Every time I write about a simple use case that could benefit from OpenFlow, I invariably get a comment along the lines of “you can do that with NETCONF”. Repeated often enough, such comments might make an outside observer believe you don’t need OpenFlow for Software Defined Networking (SDN), which is simply not true. Here are at least three fundamental reasons why that’s the case.
Read more ...Thanks for reading my news about We need both OpenFlow and NETCONF 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 :
Unreadable IPv6 Addresses Might Be Good For Us in the Long Run- We need both OpenFlow and NETCONF
- NETCONF+YANG+NETMOD versus SMI-S
- Why is RESTful API better than SNMP?
- Dell Fabric Manager Explained
- Fallacies of GUI
- NETCONF = Expect on steroids
- The best of RIPE65
- CLI and API Myths
- Tail-f Network Control System – the First Impressions