SMALL REGION | Secure Vector Routing (SVR) – Part 1
post-template-default,single,single-post,postid-16488,single-format-standard,qode-quick-links-1.0,ajax_fade,page_not_loaded,,overlapping_content,qode-theme-ver-11.1,qode-theme-bridge,bridge,wpb-js-composer js-comp-ver-5.1.1,vc_responsive

Secure Vector Routing (SVR) – Part 1

Secure Vector Routing (SVR) – Part 1

What’s the similarity of human communication vs. IP networking communication, if not to the extent of IOT/IOE? Plenty of similarity, just to prove they are in nature. The importance of persistence in communication, and the importance to improve the network in supporting the persistence, if not to fix it, is what this particular blog all about.

How do we feel when mobile broadband is congested and we can’t check our social media or chat with our contacts? Typically, if we are normal, the feeling of being isolated is building up, then it gets to frustrating level. Then we start dropping the idea, some ideas lost. Important topics get delayed. Then we narrow them down to only really crucial ones, finding alternative ways to communicate. Switching to WiFi if we were in mobile broadband, or even switched to 2.5G if 3G/4G doesn’t work in our mobile still.

We are not alone here. The impacted network elements, machines, too. They try to buffer the communication packets, but to the limit that they can only manage. Buffering, holding as much as of information. But when they got saturated with the delay and time-out, they start dropping the information. Reload is then needed. The F5 key on our notebook, remember still, anyone? Or the refresh circle is more familiar these days in our mobile apps?

Those impacted machines actually try to find alternative connectivity, as we human do. In a way, not directly. They keep on retrying it. Then the network continuously try to re-route during the congestion, and it happens at the lower TCP/IP (or OSI) layer. Hence if specific service is impacted while the network has no congestion nor failure, then either the machines for the service is impacted, or the network path used by the service is having problems. If the machines are working fine – which we can almost assume so with cloud redundancy and geographical load-sharing, then likely the network fails to find the alternate route it needs to connect the machines to other part of the network.

Things we don’t realize, and often take it from granted is, when network communication is running fine and we have no issue from using the service i.e Facebook, Google, etc., there are lots of works underneath it. It doesn’t mean the network is working fine too, it just that it managed to get around the network issues to make it seamless to us, the user of the service. It sounds complicated? It is indeed. And I am glad network technology introduction such Secure Vector Routing (SVR) is here to make it better.

Network congestion affect performance. With the Internet today is full of overlays that introduces high overhead such as VPN tunneling using IPSec or even MPLS, it also lacking of the ability to route based on certain QoS (Quality of Service) such as latency, packet-loss, and jitter. The SVR addresses all these constraints in a very smart way, lighter network processing, and much lesser packet overhead without degrading the network capabilities. Does 30% bandwidth efficiency sound good to the network? The answer is, yes, of course. And the best of all, not only it does it natively without intensive network resources for encryption and encapsulation, but it adds security, session and application aware, just to name a few benefit which is part of its native capability.

If you have question such as how SVR does it, then you are on the right blog. Stay tuned. Will elaborate more in SVR – Part 2 following this soon.


Moh. Omar

Co-Founder & CEO
SMALL Region

No Comments

Post A Comment