[Before you start reading, I need to give a big thanks to Christian Esteve Rothenberg, Research Scientist at CPqD. I asked if he wouldn't mind reading through this post prior to posting to ensure I didn't botch up anything on RouteFlow, and sure enough he immediately helped out and provided great feedback. Christian also provided us with the picture you'll eventually see below and many of the RouteFlow links as well. There was much more information he provided that I'll hope to get out soon too. Thanks again, Christian.]
So...let's get to it.
Understanding “flow based protocols” and RouteFlow can change the way you think about networking and the protocols we use on daily basis. I’m referring to control plane protocols such as Spanning Tree, OSPF, EIGRP, and BGP. Based on the traction from this blog, I can see many people are searching for answers on what SDN means for the industry and what the future will be for a network engineer, etc. If you are one of those people, first, ready my last post. It’s a quick synopsis of a presentation at ONS that covers some interesting automated tools already available for controller based networks. And second, keep reading here.
So...let's get to it.
Understanding “flow based protocols” and RouteFlow can change the way you think about networking and the protocols we use on daily basis. I’m referring to control plane protocols such as Spanning Tree, OSPF, EIGRP, and BGP. Based on the traction from this blog, I can see many people are searching for answers on what SDN means for the industry and what the future will be for a network engineer, etc. If you are one of those people, first, ready my last post. It’s a quick synopsis of a presentation at ONS that covers some interesting automated tools already available for controller based networks. And second, keep reading here.
RSS Feed
