1. Open Flow
Oded Rotter
oded1233@gmail.com
Based On:
http://en.wikipedia.org/wiki/Openflow_Switching_Protocol
http://www.networkworld.com/community/blog/openflow-inventor-discusses-
software-defined-networking?page=0%2C0&source=NWWNLE_nlt_cisco_2011-09-09
http://www.nicira.com/
http://www.bigswitch.com/

2. Wikepedia
OpenFlow is a communications protocol that gives access to
the forwarding plane of a network switch or router over the
network.[1] In simpler terms, OpenFlow allows the path-of-
network-packets-through-the-network-of-switches to be
determined by software running on a separate server. This
separation of the control from the forwarding allows for
more sophisticated traffic management than feasible using
access control lists (ACL)s and routing protocols. Its inventors
consider OpenFlow an enabler of "Software Defined
Networking".[2]

3. OpenFlow has been implemented by a number of network
switch and router vendors including Arista Networks, Extreme
Networks, IBM, Juniper Networks, Hewlett-Packard, and
NEC.[3] Some network control plane implementations use the
protocol to manage the network forwarding elements.[4]
OpenFlow is mainly used between the switch and controller
on secure channel.
Version 1.1.0 of the OpenFlow protocol was released on
February 28, 2011 and is still maintained at openflow.org, but
new development of the standard was managed by the Open
Networking Foundation.[5]
Indiana University in May 2011 launched the SDN
Interoperability Lab in conjunction with the Open Networking
Foundation to test how well different vendors' Software-
Defined Networking and OpenFlow products work together.