You’ve probably seen SD-WAN solutions in the last few years touting themselves as the best thing since Betty White. You gain all of the VPN overlays you want with consumer priced circuits and application visibility. But are those all the things that really make up SD-WAN? Are they even requirements to be considered an SD-WAN solution?
Daniel Dib has done a lot of thinking on the situation and he’s come up with a great list of things that he thinks need to be included to consider a solution SD-WAN. Note that this list isn’t definitive or all-inclusive. But as you go down the bullet points you’ll quickly realize that Daniel is a lot closer to a real SD-WAN definition than your average marketing department:
We’ve been using things like IP SLA and PfR to provide application-aware routing, that is, the ability to send traffic on different paths depending on how a transport is performing, in regards to the amount of packet loss, latency, and jitter. This provides the ability to protect against brownouts and not only blackouts.
Read more here: When Is Something SD-WAN?
- Framing Data Fortresses with Fortanix - April 2, 2020
- Drilling Down with XM Cyber - March 26, 2020
- Community Construction Isn’t Just Numbers - March 19, 2020
- Itential – The Network Glue You Need - March 17, 2020
- Building Secondary Security for IoT - March 10, 2020
- Confidence in The Cloud with NetApp - March 3, 2020
- The Power of Communities – An Interview with David Penaloza Seijas - March 2, 2020
- Moving Past The Edge with Aruba SD-Branch - February 26, 2020
- Does SPB Mean “Secure Path Bridging”? - February 12, 2020
- Cloud Isn’t Your Key To Compliance - February 10, 2020