Allow me to wax poetic about software-defined wide area networking (SD-WAN):Ode to an SD-WAN
I love your complexityAnd lack of deterministic behaviorI need your connectivityBut not new network layersOnly I can comprehendYour brittleness and insecurityAnd in the bitter endLike ATM fade in obscurityWhile SD-WANs are a hot topic currently, in reality, I believe that WANs will ultimately wane and give way to “wide area inter-networks." SD-WANs are already multi-network use cases (e.g. connecting branch networks to the corporate network). Right now, they are simple overlays, but over time, performance and functionality demands will require them to interact with the underlay network (and other layers). To read this article in full or to leave a comment, please click here
Allow me to wax poetic about software-defined wide area networking (SD-WAN):Ode to an SD-WAN
I love your complexityAnd lack of deterministic behaviorI need your connectivityBut not new network layersOnly I can comprehendYour brittleness and insecurityAnd in the bitter endLike ATM fade in obscurityWhile SD-WANs are a hot topic currently, in reality, I believe that WANs will ultimately wane and give way to “wide area inter-networks." SD-WANs are already multi-network use cases (e.g. connecting branch networks to the corporate network). Right now, they are simple overlays, but over time, performance and functionality demands will require them to interact with the underlay network (and other layers). To read this article in full or to leave a comment, please click here
It is probably safe to assume that private networking has been an afterthought. In fact, the Internet Engineering Task Force (IETF) document (RFC 1918) that created private network addresses that are “un-routable” was released years after BGP-4 and IPV6 were codified into standards.In order to join private networks to each other, wide area networks (WANs) emerged. Initially, the benefits obtained by WANs were just pure connectivity. Subsequent benefits accrued, including the belief that private networks were secure because addresses of servers and clients in the private address could not be reached from the public network unless a “translation” or rule was established. This, however, may no longer be the case.To read this article in full or to leave a comment, please click here
It is probably safe to assume that private networking has been an afterthought. In fact, the Internet Engineering Task Force (IETF) document (RFC 1918) that created private network addresses that are “un-routable” was released years after BGP-4 and IPV6 were codified into standards.In order to join private networks to each other, wide area networks (WANs) emerged. Initially, the benefits obtained by WANs were just pure connectivity. Subsequent benefits accrued, including the belief that private networks were secure because addresses of servers and clients in the private address could not be reached from the public network unless a “translation” or rule was established. This, however, may no longer be the case.To read this article in full or to leave a comment, please click here
It is probably safe to assume that private networking has been an afterthought. In fact, the Internet Engineering Task Force (IETF) document (RFC 1918) that created private network addresses that are “un-routable” was released years after BGP-4 and IPV6 were codified into standards.In order to join private networks to each other, wide area networks (WANs) emerged. Initially, the benefits obtained by WANs were just pure connectivity. Subsequent benefits accrued, including the belief that private networks were secure because addresses of servers and clients in the private address could not be reached from the public network unless a “translation” or rule was established. This, however, may no longer be the case.To read this article in full or to leave a comment, please click here