Programmable Abstraction of Datapath

Belter, Bartosz; Binczewski, Artur; Dombek, Krzysztof; Juszczyk, Artur; Ogrodowczyk, Łukasz; Parniewicz, Damian; Stroiński, Maciej; Olszewski, Iwo

doi:10.1109/ewsdn.2014.10

Cited by 13 publications

(10 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Recent research experiments with HAL have demonstrated the viability of SDN control in access networks such as Gigabit Ethernet passive optical networks (GEPONs) [160] and cable networks (DOCSIS) [161]. A similar effort to HAL is the Programmable Abstraction of Datapath (PAD) [159], a proposal that goes a bit further by also working as a southbound API by itself. More importantly, PAD allows a more generic programming of forwarding devices by enabling the control of datapath behavior using generic byte operations, defining protocol headers and providing function definitions.…”

Section: B Layer Ii: Southbound Interfacesmentioning

confidence: 99%

“…There are other API proposals such as ForCES [30], OVSDB [153], POF [31], [120], OpFlex [154], OpenState [155], Revised OpenFlow Library (ROFL) [156], Hardware Abstraction Layer (HAL) [157], [158], and Programmable Abstraction of Datapath (PAD) [159]. ForCES proposes a more flexible approach to traditional network management without changing the current architecture of the network, i.e., without the need of a logically-centralized external controller.…”

Section: B Layer Ii: Southbound Interfacesmentioning

confidence: 99%

“…Some of these efforts include new architectures for a smooth migration from the current mobile core infrastructure to SDN [222], and techno-economic models for virtualization of these networks [549], [550]; carrier-grade OpenFlow virtualization schemes [551], [112], including virtualized broadband access infrastructures [552], techniques that are allowing the offer of network-as-a-service [553]; programmable GE-PON and DWDM ROADM [157], [158], [159], [160]; largescale inter-autonomous systems (ASs) SDN-enabled deployments [554]; flexible control of network resources [555], including offering MPLS services using an SDN approach [556]; and the investigation of novel network architectures, from proposals to separate the network edge from the core [557], [558], with the latter forming the fabric that transports packets as defined by an intelligent edge, to software-defined Internet exchange points [559], [526].…”

Section: H Meeting Carrier-grade and Cloud Requirementsmentioning

confidence: 99%

See 2 more Smart Citations

Software-Defined Networking: A Comprehensive Survey

et al. 2015

View full text Add to dashboard Cite

Abstract-The Internet has led to the creation of a digital society, where (almost) everything is connected and is accessible from anywhere. However, despite their widespread adoption, traditional IP networks are complex and very hard to manage. It is both difficult to configure the network according to predefined policies, and to reconfigure it to respond to faults, load and changes. To make matters even more difficult, current networks are also vertically integrated: the control and data planes are bundled together. Software-Defined Networking (SDN) is an emerging paradigm that promises to change this state of affairs, by breaking vertical integration, separating the network's control logic from the underlying routers and switches, promoting (logical) centralization of network control, and introducing the ability to program the network. The separation of concerns introduced between the definition of network policies, their implementation in switching hardware, and the forwarding of traffic, is key to the desired flexibility: by breaking the network control problem into tractable pieces, SDN makes it easier to create and introduce new abstractions in networking, simplifying network management and facilitating network evolution.In this paper we present a comprehensive survey on SDN. We start by introducing the motivation for SDN, explain its main concepts and how it differs from traditional networking, its roots, and the standardization activities regarding this novel paradigm. Next, we present the key building blocks of an SDN infrastructure using a bottom-up, layered approach. We provide an in-depth analysis of the hardware infrastructure, southbound and northbound APIs, network virtualization layers, network operating systems (SDN controllers), network programming languages, and network applications. We also look at cross-layer problems such as debugging and troubleshooting. In an effort to anticipate the future evolution of this new paradigm, we discuss the main ongoing research efforts and challenges of SDN. In particular, we address the design of switches and control platforms -with a focus on aspects such as resiliency, scalability, performance, security and dependability -as well as new opportunities for carrier transport networks and cloud providers. Last but not least, we analyze the position of SDN as a key enabler of a software-defined environment.

show abstract

Section: B Layer Ii: Southbound Interfacesmentioning

confidence: 99%

Section: B Layer Ii: Southbound Interfacesmentioning

confidence: 99%

Section: H Meeting Carrier-grade and Cloud Requirementsmentioning

confidence: 99%

See 1 more Smart Citation

Software-Defined Networking: A Comprehensive Survey

et al. 2015

View full text Add to dashboard Cite

show abstract

“…In Programming Abstraction Datapath (PAD) [66] authors exposes switch capabilities for programmability and provides a southbound API for other types of devices such as Optical Switches. It provides generic programming of forwarding devices by using byte operations which define protocol headers and functions.…”

Section: B Openflow Dependent Sbi Proposalsmentioning

confidence: 99%

A comprehensive survey of interface protocols for software defined networks

Latif

Sharif

et al. 2020

Journal of Network and Computer Applications

108

View full text Add to dashboard Cite

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.

show abstract

“…New hardware abstraction, called Programmable Abstraction of Datapath (PAD), for various network devices such as access devices, network processors, and optical devices, is proposed in [220]. PAD enabled data plane behavior programming through protocol and function header definitions, and by using generic byte-oriented operations.…”

Section: ) Data Plane Abstractionsmentioning

confidence: 99%

A Survey on Data Plane Flexibility and Programmability in Software-Defined Networking

et al. 2019

View full text Add to dashboard Cite

Software-defined networking (SDN) attracts the attention of the research community in recent years, as evidenced by a large number of survey and review papers. The architecture of SDN clearly recognizes three planes: application, control, and data plane. The application plane executes network applications; control plane regulates the rules for the entire network based on the requests generated by network applications; and based on the set rules, the controller configures the switches in the data plane. The role of the switch in the data plane is to simply forward packets based on the instructions given by the controller. By analyzing SDN-related research papers, it is observed that research, from the very beginning, is insufficiently focused on the data plane. Therefore, this paper gives a comprehensive overview of the data plane survey with particular emphasis on the problem of programmability and flexibility. The first part of the survey is dedicated to the evaluation of actual data plane architectures through several definitions and aspects of data plane flexibility and programmability. Then, an overview of SDN-related research was presented with the aim of identifying key factors influencing the gradual deviation from the original data plane architectures given with ForCES and OpenFlow specifications, which we called the data plane evolution. By establishing a correlation between the treated problem and the problem-solving approaches, the limitations of ForCES and OpenFlow data plane architectures were identified. Based on identified limitations, a generalization of approaches to addressing the problem of data plane flexibility and programmability is made. By examining generalized approaches, open issues have been identified, establishing the grounds for future research directions proposal.

show abstract

Programmable Abstraction of Datapath

Cited by 13 publications

References 3 publications

Software-Defined Networking: A Comprehensive Survey

Software-Defined Networking: A Comprehensive Survey

A comprehensive survey of interface protocols for software defined networks

A Survey on Data Plane Flexibility and Programmability in Software-Defined Networking

Contact Info

Product

Resources

About