A comprehensive survey of interface protocols for software defined networks

Abstract

Software Defined Networks has seen tremendous growth and deployment in different types of networks. Compared to traditional networks it decouples the control logic from network layer devices, and centralizes it for efficient traffic forwarding and flow management across the domain. This multilayered architecture has data forwarding devices at the bottom in data plane, which are programmed by controllers in the control plane. The high level application or management plane interacts with control layer to program the whole network and enforce different policies. The interaction among these layers is done through interfaces which work as communication/programming protocols. In this survey, we present a comprehensive study of such interfaces available for southbound, northbound, and east/westbound communication. We have classified each type into different categories based on their properties and capabilities. Virtualization of networks devices is a common practice in Software Defined Networks. This paper also analyzes interface solution which work with different virtualization schemes. In addition, the paper highlights a number of short term and long term research challenges and open issues related to SDN interfaces.

A Review of Industry 4.0 Manufacturing Process Security Risks

“…The concept of a software-defined network (SDN) presents a unique and very promising solution to this complex networking problem. Where network control and data-forwarding functionalities are typically embedded within the same device for a conventional network, the concept of an SDN enables the possibility of decoupling network functionality from actual network infrastructure [6,48,49]. The main aspect of this network decoupling process is the abstraction of the underlying network infrastructure that interconnects network devices.…”

“…An SDN network can be divided into three main entities, namely the management plane, control plane and data plane [49]. This also introduces the concept of network function virtualization (NFV), where networking functions such as firewalls, switching and routing are separated from the rest of the network infrastructure [6,49]. The separation of a network into these three entities makes it possible to optimize the underlying functionalities of each of these entities.…”

“…The separation of a network into these three entities makes it possible to optimize the underlying functionalities of each of these entities. The entities make use of dedicated interfaces called the northbound, southbound, eastbound and westbound interfaces [49]. Figure 8 illustrates this network separation into the three main entities, and summarizes the architectural layout of an SDN: enables the possibility of decoupling network functionality from actual network infrastructure [6,48,49].…”

“…The entities make use of dedicated interfaces called the northbound, southbound, eastbound and westbound interfaces [49]. Figure 8 illustrates this network separation into the three main entities, and summarizes the architectural layout of an SDN: enables the possibility of decoupling network functionality from actual network infrastructure [6,48,49]. The main aspect of this network decoupling process is the abstraction of the underlying network infrastructure that interconnects network devices.…”

“…The OpenFlow protocol was the first standardized communications interface that allowed the direct control and manipulation of network devices and networking services within an SDN [48]. Currently, it is also the most commonly used protocol for SDNs in both the research and commercial sectors [49]. One great advantage that the OpenFlow protocol offers is its ability to be deployed within existing networks, both of a physical and virtual nature.…”