Software-defined networking

Software-defined networking
Name	Software-defined networking
Introduced	2000s
Inventor	Multiple
Influenced	Network virtualization, Cloud computing

Software-defined networking Software-defined networking (SDN) is an approach to network management that separates the control plane from the data plane to enable programmable, centralized control of network behavior. SDN emerged alongside developments in Google (company), Stanford University, OpenFlow research and has influenced technologies used by Amazon Web Services, Microsoft Azure, Facebook, IBM, and Cisco Systems. SDN interacts with virtualization projects such as VMware, Xen (software), and orchestration platforms like Kubernetes and OpenStack, and has been subject to standardization efforts at organizations including the Internet Engineering Task Force and the Open Networking Foundation.

Overview

SDN redefines how networks built by vendors such as Cisco Systems, Juniper Networks, Arista Networks and Huawei are managed by decoupling control instantiated in controllers like ONOS (software) and OpenDaylight from forwarding implemented on switches such as those by Intel, Broadcom Inc., and Mellanox Technologies. The paradigm enables programmability used by cloud providers including Google (company), Amazon Web Services, and Microsoft Azure to support services pioneered by projects at Stanford University, UC Berkeley, and research labs at IBM. SDN has intersections with concepts advanced by VMware, Nicira, Cumulus Networks and influenced follow-on architectures in Network Functions Virtualization and Service Orchestration initiatives.

Architecture and Components

SDN architecture typically comprises three layers: an application layer populated by orchestration tools like Kubernetes, OpenStack, and Ansible (software), a control layer featuring controllers including OpenDaylight and ONOS (software), and an infrastructure layer of switches and routers produced by Cisco Systems, Juniper Networks, and Arista Networks. Key components include southbound interfaces such as OpenFlow and NetConf; northbound APIs used by OpenStack, CloudStack, and proprietary controllers; and management systems from HP Enterprise and Dell Technologies. SDN controllers may integrate modules from projects like Open Networking Foundation, ETSI working groups, and academic prototypes developed at Stanford University and Princeton University.

Implementation and Protocols

Implementations use protocols and standards including OpenFlow, Border Gateway Protocol, NETCONF, BGP (Border Gateway Protocol), and P4 (language), and leverage platforms like Linux, Open vSwitch, and hardware from Broadcom Inc. and Intel. Controller software such as OpenDaylight, ONOS (software), and commercial offerings from Cisco Systems and Huawei expose northbound APIs used by orchestration stacks like OpenStack and Kubernetes. Research prototypes from Stanford University, UC Berkeley, and companies like Nicira informed protocol evolution and spurred industry projects at Google (company) and Facebook that integrate custom control-plane logic with protocols including BGP (Border Gateway Protocol) and extensions to OpenFlow.

Use Cases and Applications

SDN is applied in data center networks operated by Google (company), Amazon Web Services, and Facebook to enable traffic engineering, microsegmentation, and workload mobility managed by tools like Kubernetes and OpenStack. Service providers such as AT&T and Verizon Communications use SDN for metro and wide-area optimization, virtual private network services, and dynamic bandwidth allocation alongside initiatives from ETSI and Open Networking Foundation. Enterprises including Goldman Sachs and cloud providers deploy SDN for security policies integrated with Palo Alto Networks appliances, and telecommunications vendors such as Nokia and Ericsson use SDN alongside Network Functions Virtualization for 5G infrastructure.

Advantages and Limitations

Advantages cited by adopters including Google (company), Amazon Web Services, and Facebook include centralized management, faster innovation cycles inspired by DevOps practices, and improved resource utilization demonstrated in research at Stanford University and UC Berkeley. Limitations include interoperability hurdles among vendors such as Cisco Systems, Juniper Networks, and Huawei; performance constraints on high-throughput platforms from Broadcom Inc.; and operational complexity discussed in industry reports by Gartner and Forrester Research. Transition challenges mirror concerns in migrations documented by VMware case studies and regulatory considerations referenced by Federal Communications Commission filings.

Security and Reliability

Security concerns involve controller vulnerabilities, supply-chain issues tied to vendors including Huawei and ZTE, and attack surfaces in southbound protocols originally designed in research at Stanford University and UC Berkeley. Mitigations employ redundancy patterns used by AT&T and Verizon Communications, authentication and authorization frameworks aligned with IETF recommendations, and secure telemetry integrations with systems from Splunk and Elastic NV. Reliability strategies parallel distributed-system designs from Google (company) and Apache Software Foundation projects, using controller clustering, failover mechanisms, and formal verification methods explored at MIT and Carnegie Mellon University.

History and Standardization

Early SDN concepts were advanced by academics at Stanford University and UC Berkeley and commercialized by startups such as Nicira before acquisitions by VMware. Standardization efforts have been led by the Open Networking Foundation, contributions to protocol work at the Internet Engineering Task Force, and initiatives within ETSI and the IEEE Standards Association. Industry adoption accelerated after deployments by Google (company), open-source projects like OpenDaylight and Open vSwitch, and acquisitions and product launches from Cisco Systems, Juniper Networks, and VMware.

Category:Computer networking