![]() Work on OpenFlow continued at Stanford, including with the creation of testbeds to evaluate the use of the protocol in a single campus network, as well as across the WAN as a backbone for connecting multiple campuses. SDN research included emulators such as vSDNEmul, EstiNet, and Mininet. These applications became public in 2009 and have since been abandoned. Several patent applications were filed by independent researchers in 2007 describing practical applications for SDN, operating system for networks, network infrastructure compute units as a multi-core CPU and a method for virtual-network segmentation based on functionality. In that same year, NOX, an operating system for networks, was created. Ethane's simple switch design led to the creation of OpenFlow, and an API for OpenFlow was first created in 2008. The use of open-source software in split control/data plane architectures traces its roots to the Ethane project at Stanford's computer-science department. ![]() 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. 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. These early attempts failed to gain traction. ![]() Additional early standards from the IETF that pursued separating control from data include the Linux Netlink as an IP services protocol and a path computation element (PCE)-based architecture. The ForCES Working Group also proposed a companion SoftRouter architecture. The Internet Engineering Task Force (IETF) began considering various ways to decouple the control and forwarding functions in a proposed interface standard published in 2004 named Forwarding and Control Element Separation (ForCES). This provided a manner of simplifying provisioning and management years before the architecture was used in data networks. The history of SDN principles can be traced back to the separation of the control and data plane first used in public switched telephone networks. SD-WAN applies similar technology to a wide area network (WAN). These include Cisco Systems' Open Network Environment and Nicira's network virtualization platform. However, since 2012, proprietary systems have also used the term. SDN was commonly associated with the OpenFlow protocol (for remote communication with network plane elements to determine the path of network packets across network switches) since OpenFlow's emergence in 2011. However, centralization has certain drawbacks related to security, scalability and elasticity. The control plane consists of one or more controllers, which are considered the brains of the SDN network, where the whole intelligence is incorporated. ![]() SDN is meant to improve the static architecture of traditional networks and may be employed to centralize network intelligence in one network component by disassociating the forwarding process of network packets ( data plane) from the routing process ( control plane). Software-defined networking ( SDN) is an approach to network management that enables dynamic and programmatically efficient network configuration to improve network performance and monitoring in a manner more akin to cloud computing than to traditional network management. ( Learn how and when to remove this template message) Please help update this article to reflect recent events or newly available information. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |