Need for software defined networking

Enter the characters you see below Sorry, we just need to make sure you’re not a robot. Enter the need for software defined networking you see below Sorry, we just need to make sure you’re not a robot. Please help improve it or discuss these issues on the talk page. This article has been nominated to be checked for its neutrality.

Discussion of this nomination can be found on the talk page. This article needs additional citations for verification. This section may need to be rewritten entirely to comply with Wikipedia’s quality standards, as it seems to deviate from the SDN development history as described in this source. This section’s factual accuracy is disputed. Relevant discussion may be found on Talk:Software-defined networking. The history of SDN principles can be traced back to the separation of the control and data plane first used in the public switched telephone network as a way to simplify provisioning and management well before this architecture began to be used in data networks.

These early attempts failed to gain traction for two reasons. One is that many in the Internet community viewed separating control from data to be risky, especially owing to the potential for a failure in the control plane. Ethane project at Stanford’s computer sciences department. That same year witnessed the creation of NOX—an operating system for networks. Beyond academia, the first deployments were by Nicira in 2010 to control OVS from Onix, co-developed with NTT and Google. A notable deployment was Google’s B4 deployment in 2012.

Did not find what they wanted? Try here

SDN architectures decouple network control and forwarding functions, enabling network control to become directly programmable and the underlying infrastructure to be abstracted from applications and network services. 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 to meet changing needs. SDN controllers that maintain a global view of the network, which appears to applications and policy engines as a single, logical switch. Programmatically configured: SDN lets network managers configure, manage, secure, and optimize network resources very quickly via dynamic, automated SDN programs, which they can write themselves because the programs do not depend on proprietary software.

Open standards-based and vendor-neutral: When implemented through open standards, SDN simplifies network design and operation because instructions are provided by SDN controllers instead of multiple, vendor-specific devices and protocols. Many conventional networks are hierarchical, built with tiers of Ethernet switches arranged in a tree structure. Changing traffic patterns Within the enterprise data center, traffic patterns have changed significantly. In addition they may consume an abstracted view of the network for their internal decision-making purposes. An SDN Application consists of one SDN Application Logic and one or more NBI Drivers. Centralized – Hierarchical – Distributed The implementation of the SDN control plane can follow a centralized, hierarchical, or decentralized design.

Initial SDN control plane proposals focused on a centralized solution, where a single control entity has a global view of the network. While this simplifies the implementation of the control logic, it has scalability limitations as the size and dynamics of the network increase. Controller Placement A key issue when designing a distributed SDN control plane is to decide on the number and placement of control entities. An important parameter to consider while doing so is the propagation delay between the controllers and the network devices, especially in the context of large networks. SDN architecture may enable, facilitate or enhance network-related security applications due to the controller’s central view of the network, and its capacity to reprogram the data plane at any time.

Several research works on SDN have already investigated security applications built upon the SDN controller, with different aims in mind. MTD algorithms are typically used to make any attack on a given system or network more difficult than usual by periodically hiding or changing key properties of that system or network. The former tries to use a single hardware forwarding plane sharing multiple separated logical networks. SDN controller applications are mostly deployed in large-scale scenarios, which requires comprehensive checks of possible programming errors. A system to do this called NICE was described in 2012.