Software-Defined Networking: Experimenting with the Control to Forwarding Plane Interface
Evangelos Haleplidis, Spyros Denazis, Odysseas Koufopavlou, Jamal Hadi Salim, Joel Martin Halpern
Abstract
Evangelos Haleplidis, Spyros Denazis, Odysseas Koufopavlou, Jamal Hadi Salim, Joel Martin Halpern
Abstract
Software-Defined Networking (SDN) is an emerging network architecture where the network control plane is decoupled from the forwarding plane and is programmable via an open protocol. Forwarding and Control Element Separation (Forces) first and OpenFlow later are the prevailing protocols that enable this separation. The differences between the two stem from the underlying models they are defined upon. While OpenFlow is widely used, its capability for adding new functionality of the Forwarding plane is questionable, a fact that is attributed to a restricted model. In contrast, Forces has a very dynamic model that makes its protocol quite powerful but has known little spread due to lack of industry adoption and in the academic world due to lack of open source availability for experimentation. In this paper we first investigate ways of possible confluence or convergence of Forces and OpenFlow and later we explore a real-life service use case for applying a Enabled-enabled OpenFlow switch.
OpenAlex reports 20 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
Software-Defined Networking (SDN) is an emerging network architecture where the network control plane is decoupled from the forwarding plane and is programmable via an open protocol. Forwarding and Control Element Separation (Forces) first and OpenFlow later are the prevailing protocols that enable this separation. The differences between the two stem from the underlying models they are defined upon. While OpenFlow is widely used, its capability for adding new functionality of the Forwarding plane is questionable, a fact that is attributed to a restricted model. In contrast, Forces has a very dynamic model that makes its protocol quite powerful but has known little spread due to lack of industry adoption and in the academic world due to lack of open source availability for experimentation. In this paper we first investigate ways of possible confluence or convergence of Forces and OpenFlow and later we explore a real-life service use case for applying a Enabled-enabled OpenFlow switch.
Key concepts: OpenFlow, Forwarding plane, Routing control plane, Computer science, Software-defined networking, Interface (matter), Computer network, Distributed computing