Two days ago I described how you can use tunneling or labeling to reduce the forwarding state in the network core (which you have to do if you want to have reasonably fast convergence with currently-available OpenFlow-enabled switches). Now let’s see what you can do in the very limited world of OpenFlow 1.0 (if any shipping physical switch supports OpenFlow 1.1 beyond OpenFlow 1.0 functionality, please write a comment)
Read more ...Thanks for reading my news about Virtual Circuits in OpenFlow 1.0 World at my blog Bros Droid if you want too share this article, please put the resource, and if you think this article is very usefully dont forget to bookmark this site with CTRL + D on your keyboard to web browser.
More Articles :
Edge and Core OpenFlow (and why MPLS is not NAT)- Could MPLS-over-IP replace VXLAN or NVGRE?
- Secondary MPLS-TE Tunnels and Fast Reroute
- Can BGP Route Reflectors Really Generate Forwarding Loops?
- Virtual Circuits in OpenFlow 1.0 World
- Exception Routing with BGP: SDN Done Right
- Forwarding State Abstraction with Tunneling and Labeling
- OpenFlow and Ipsilon: Nothing New Under the Sun
- Could you run an MPLS-TE-only MPLS/VPN network without LDP?
- Edge Protocol Independence: Another Benefit of Edge-and-Core Layering