Software-defined networking: Difference between revisions

Revision as of 02:56, 7 July 2025

Revision as of 01:06, 9 July 2025

Line 68:

|title=GENI. Campus OpenFlow topology

|date=2011

}}</ref> In academic settings, there were several research and production networks based on OpenFlow switches from [[NEC]] and [[Hewlett-Packard]], as well as those based on [[Quanta Computer]] whiteboxeswhite-boxes starting in about 2009.<ref>{{cite web

|url=https://www.internet2.edu/presentations/fall11/20111003-wang-openflow.pdf

|archive-url=https://web.archive.org/web/20180103133512/https://www.internet2.edu/presentations/fall11/20111003-wang-openflow.pdf

Line 115:

==Concept==

SDN architectures decouple network control ([[control plane]]) and forwarding ([[data plane]]) functions, enabling the network control to become directly programmable and the underlying infrastructure to be abstracted from applications and network services.<ref>{{cite web|url=http://www.opennetworking.org/sdn-resources/sdn-definition|title=Software-Defined Networking (SDN) Definition|website=Opennetworking.org|access-date=26 October 2014}}</ref> The OpenFlow protocol is one of the protocols used in SDN technologies.

The OpenFlow protocol can be used in SDN technologies. The SDN architecture is:

* Directly programmable: Network control is directly programmable because it is decoupled from forwarding functions.

* Agile: Abstracting control from forwarding lets administrators dynamically adjust network-wide [[Traffic flow (computer networking)|traffic flow]] to meet changing needs.