Virtual data planes for easy creation and operation of end-to-end virtual networks

Naoki, Oguchi; Sekiya, Motoyoshi

doi:10.23919/softcom.2017.8115595

Cited by 2 publications

(2 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…• the design should be conceived as a stateful from the beginning, • a precise semantic of the forwarding table layering is needed, • physical layer protocols need to be separated from the data plane, • all operations should be modeled as actions (e.g., tunneling as encapsulation and decapsulation), • forwarding should be kept simple, • commodity NIC hardware is not ideal for the SDN. Virtual data planes, as described in [174], can be realized as software objects called virtual network objects (VNO), to which multiple network infrastructures can be mapped. The network slice can be created as needed by configuring the logical network via VNO, which liberates users from the need for expert knowledge in the field of virtual networks.…”

Section: G Network and Network Functions Virtualizationmentioning

confidence: 99%

“…• commodity NIC hardware is not ideal for the SDN. Virtual data planes, as described in [174], can be realized as software objects called virtual network objects (VNO), to which multiple network infrastructures can be mapped. The network slice can be created as needed by configuring the logical network via VNO, which liberates users from the need for expert knowledge in the field of virtual networks.…”

Section: G Network and Network Functions Virtualizationmentioning

confidence: 99%

See 1 more Smart Citation

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

Section: G Network and Network Functions Virtualizationmentioning

confidence: 99%

Section: G Network and Network Functions Virtualizationmentioning

confidence: 99%