Software-defined networking: Difference between revisions

Revision as of 18:19, 11 June 2024

Revision as of 15:06, 9 July 2024

Line 43:

These early attempts failed to gain traction. One reason is that many in the Internet community viewed separating control from data to be risky, especially given the potential for failure in the control plane. Another reason is that vendors were concerned that creating standard application programming interfaces (APIs) between the control and data planes would result in increased competition.

The use of open-source software in these separated architectures traces its roots to the Ethane project at [[Stanford University|Stanford]]'s computer science department. Ethane's simple switch design led to the creation of OpenFlow,<ref>{{cite web

|url=http://cs.brown.edu/courses/csci2950-u/s14/papers/Casado07Ethane.pdf

|title=Ethane: Taking Control of the Enterprise

Line 173:

The ___location of the SDN data plane and agent can be used to classify SDN implementations:

* ''Hardware Switch-based SDNs:'' This approach implements the data plane processing inside a physical device. OpenFlow switches may use [[Content-addressable memory#Ternary CAMs|TCAM]] tables to route packet sequences [[Traffic flow (computer networking)|(flows)]]. These switches may use an [[Application-specific integrated circuit|ASIC]] for its implementation.

* ''Software Switch-Based SDNs:'' Some physical switches may implement SDN support using software on the device, such as [[Open vSwitch]], to populate flow tables and to act as the SDN agent when communicating with the controller. [[Hypervisor|Hypervisors]]s may likewise use software implementations to support SDN protocols in the virtual switches used to support their [[Virtualvirtual machine|virtual machines]]s.

* ''Host-Based SDNs:'' Rather than deploying the data plane and SDN agent in network infrastructure, host-based SDNs deploy the SDN agent inside the operating system of the communicating endpoints.<ref>{{cite book |last1=Taylor |first1=Curtis |last2=MacFarland |first2=Douglas |last3=Smestad |first3=Doran |last4=Shue |first4=Craig |title=IEEE INFOCOM 2016 - the 35th Annual IEEE International Conference on Computer Communications |chapter=Contextual, flow-based access control with scalable host-based SDN techniques |date=10 April 2014 |pages=1–9 |doi=10.1109/INFOCOM.2016.7524498 |isbn=978-1-4673-9953-1 |s2cid=17491115 |chapter-url=https://par.nsf.gov/servlets/purl/10055769}}</ref> Such implementations can provide additional context about the application, user, and activity associated with network flows.<ref>{{cite book |last1=Chuluundorj |first1=Zorigtbaatar |last2=Taylor |first2=Curtis |last3=Walls |first3=Robert |last4=Shue |first4=Craig |title=2021 Eighth International Conference on Software Defined Systems (SDS) |chapter=Can the User Help? Leveraging User Actions for Network Profiling |date=6 December 2021 |pages=1–8 |doi=10.1109/SDS54264.2021.9732164 |isbn=978-1-6654-5820-7 |s2cid=244036711 |chapter-url=https://ieeexplore.ieee.org/document/9732164}}</ref> To achieve the same traffic engineering capabilities of switch-based SDNs, host-based SDNs may require the use of carefully designed [[VLAN]] and [[Spanning Tree Protocol|spanning tree]] assignments.<ref>{{cite book |last1=Lei |first1=Yunsen |last2=Lanson |first2=Julian |last3=Kaldawy |first3=Remy |last4=Estrada |first4=Jeffrey |last5=Shue |first5=Craig |title=2020 11th International Conference on Network of the Future (NoF) |chapter=Can Host-Based SDNS Rival the Traffic Engineering Abilities of Switch-Based SDNS? |date=11 November 2020 |pages=91–99 |doi=10.1109/NoF50125.2020.9249110 |isbn=978-1-7281-8055-7 |s2cid=221505891 |chapter-url=https://ieeexplore.ieee.org/document/9249110}}</ref>

Line 184:

=== SDMN ===

[[Software-defined mobile network]]ing (SDMN)<ref name= MobileFlow>{{Cite journal |doi = 10.1109/MCOM.2013.6553677|title = Mobileflow: Toward software-defined mobile networks|journal = IEEE Communications Magazine|volume = 51|issue = 7|pages = 44–53|year = 2013|last1 = Pentikousis|first1 = Kostas|last2 = Wang|first2 = Yan|last3 = Hu|first3 = Weihua|s2cid = 10655582}}</ref><ref>{{Cite book|url=http://eu.wiley.com/WileyCDA/WileyTitle/productCd-1118900286.html|title=Software Defined Mobile Networks (SDMN): Beyond LTE Network Architecture|last=Liyanage|first=Madhusanka|publisher=John Wiley|year=2015|isbn=978-1-118-90028-4|___location=UK|pages=1–438}}</ref> is an approach to the design of mobile networks where all protocol-specific features are implemented in software, maximizing the use of generic and commodity hardware and software in both the [[core network]] and [[radio access network]].<ref>{{cite book|chapter=SDN and NFV Integration in Generalized Mobile Network Architecture|doi=10.1109/EuCNC.2015.7194059|title=2015 European Conference on Networks and Communications (EuCNC)|year=2015|last1=Costa-Requena|first1=Jose|last2=Liyanage|first2=Madhusanka|last3=Ylianttila|first3=Mika|last4=De Oca|first4=Edgardo Montes|last5=Santos|first5=Jesus Llorente|last6=Guasch|first6=Vicent Ferrer|last7=Ahokas|first7=Kimmo|last8=Premsankar|first8=Gopika|last9=Luukkainen|first9=Sakari|last10=Perez|first10=Oscar Lopez|last11=Itzazelaia|first11=Mikel Uriarte|last12=Ahmad|first12=Ijaz|pages=154–158|isbn=978-1-4673-7359-3|s2cid=2453962}}</ref> It is proposed as an extension of SDN paradigm to incorporate [[Cellular network|mobile network]] specific functionalities.<ref>{{cite book|chapter=Securing the Control Channel of Software-Defined Mobile Networks|doi=10.1109/WoWMoM.2014.6918981|title=Proceeding of IEEE International Symposium on a World of Wireless, Mobile and Multimedia Networks 2014|year=2014|last1=Liyanage|first1=Madhusanka|last2=Ylianttila|first2=Mika|last3=Gurtov|first3=Andrei|pages=1–6|isbn=978-1-4799-4786-7|s2cid=1378181}}</ref> Since 3GPP Rel.14, a Control User Plane Separation was introduced in the Mobile Core Network architectures with the [[PFCP]] protocol.

===SD-WAN===