Comments on: Some Afterthoughts on Open Network Environment, SDN and Overlay Networks http://blogs.cisco.com/datacenter/some-afterthoughts-on-open-network-environment-sdn-and-overlay-networks/ Thu, 23 May 2013 09:41:39 +0000 hourly 1 By: Gary Kinghorn http://blogs.cisco.com/datacenter/some-afterthoughts-on-open-network-environment-sdn-and-overlay-networks/#comment-611638 Gary Kinghorn Mon, 16 Jul 2012 16:40:08 +0000 http://blogs.cisco.com/?p=74388#comment-611638 You are right. Perhaps the point to clarify is that making virtual overlays PROGRAMMABLE is the killer app of SDN. Your GRE tunnels, etc. aren’t programmable. Having said that, you could also say that programmable overlays are not an app either. The app is what you program on top of the overlay. But if we said that programmable virtual overlays were really middleware for the network, even fewer people would get what we were talking about.

   0 likes

]]> By: Tim Rider http://blogs.cisco.com/datacenter/some-afterthoughts-on-open-network-environment-sdn-and-overlay-networks/#comment-610900 Tim Rider Fri, 13 Jul 2012 18:27:59 +0000 http://blogs.cisco.com/?p=74388#comment-610900 So the killer app of SDN is “virtual network overlays”? Sorry Gary, but that doesn’t make a whole lot of sense. A Network Overlay in and of itself is just another form of networking. Sure, it can enable more flexibility, extend the diameter of VM mobility. But it’s not an application itself.

Also, VNO and SDN don’t really have anything to do with one another. We have been doing network overlays (for instance, IPSec/GRE VPNs for VPLS tunnels) long before people started talking about SDN. You don’t need SDN to do Virt Network Overlays, and you certainly don’t need VNO to SDN-enable the network.

   0 likes

]]> By: Gary Kinghorn http://blogs.cisco.com/datacenter/some-afterthoughts-on-open-network-environment-sdn-and-overlay-networks/#comment-606742 Gary Kinghorn Tue, 26 Jun 2012 15:28:46 +0000 http://blogs.cisco.com/?p=74388#comment-606742 No, we are making the onePK components available for third party application developers. That is the primary intent here with this announcement. What I was trying to convey is that onePK is a developer kit which includes software libraries that can be compiled into applications (among other things). Those libraries will work only on Cisco platforms, just like when you compile Windows libraries into your application, the application will not run on a Linux box, only Windows. These libraries access internals in the platform operating systems, et al., unique to Cisco, and will not work on non-Cisco routers and switches. Sorry for the confusion.

   0 likes

]]> By: Bojian Wang http://blogs.cisco.com/datacenter/some-afterthoughts-on-open-network-environment-sdn-and-overlay-networks/#comment-606665 Bojian Wang Tue, 26 Jun 2012 10:18:33 +0000 http://blogs.cisco.com/?p=74388#comment-606665 When you are talking about that Cisco OnePK components are really only designed to Cisco platform, does it mean that we won’t provide OnePK components to 3rd party’s application ?

   0 likes

]]>