So what I'm going to try and do here is try and remove some of the hype and terms causing confusion
and kind of group visions of software defined networking into different compartments.
So the first vision and the original vision will define as open.
SD And this is based on the original work at Stanford and uses the open flow protocol.
The organization that's driving this today is the Open Networking Foundation.
It defines software defined networking as the separation of the control plane and data plane.
And later in this presentation, I'll explain what that actually means.
Implementations of software defined networking controllers include open daylight or Odl on US NOx,
Pox, Floodlight and others, including commercial controllers from the likes of HP and others.
I'm creating multiple courses to explain each of these visions or examples of software defined networking.
So have a look on the Genesis three website for more courses where I do deep dives into the details
and nitty gritty of each of these visions of MSDN.
The next vision is software defined networking via overlays, and the most famous example of this is
probably NSX from VMware.
As you can see in this video, Martin Casado works at VMware.
His company, Nazara, was purchased by VMware a few years ago for over $1,000,000,000.
And VMware now advocates a virtual network overlaid across a physical network.
We have the concept of a underlay network, which are the physical network devices, and we have a virtual
network that can automatically be deployed across the physical network.
This uses protocols like VXLAN and NV Jari.
Another example of this is Nuage Networks, which have a product for very high scale multi data center,
multi hypervisor, virtual networks.
A third vision or definition of software defined networking is what's called bright boxes or white boxes.
So white box is examples of companies that are involved here include Picker eight and Cumulus Networks
Y run proprietary operating systems tied to proprietary hardware.
Why not run an operating system that can be installed on multiple vendor devices?
So in this example, you could have a physical switch.
And today is an example.
You may want to run one operating system, but next week you may want to replace it with a different
operating system.
And that's what these vendors allow you to do.
Don't buy proprietary hardware, proprietary operating systems and proprietary features, rather, by
switches that are not tied to a specific vendor.
Another example that kind of fits in this is the Facebook Open compute switches, such as six pack and
wedge.