User:JUehV/sandbox
TODO add this to npv site
Network Protocol Virtualization or Network Protocol Stack Virtualization is a concept of providing network connections as a service, without concerning application developer to decide the exact communication stack composition.
Concept
[edit]
Network Protocol Virtualization (NPV) was firstly proposed by Heuschkel et. al. in 2015 as a rough sketch as part of a transition concept for network protocol stacks[1]. The concept evolved and was published in a deployable state in 2018[2].
The key idea is to decouple applications from their communication stacks. Today the socket API requires application developer to compose the communication stack by hand by choosing between IPv4/IPv6 and UDP/TCP. NPV proposes the network protocol stack should be tailored to the observed network environment (e.g. link layer technology, or current network performance). Thus, the network stack should not be composed at development time, but at runtime and needs the possibility to be adapted if needed.
Additionally the decoupling relaxes the chains of the ISO OSI network layer model, and thus enables alternative concepts of communication stacks. Heuschkel et. al. proposes the concept of Application layer middleboxes as example to add additional layers to the communication stack to enrich the communication with useful services (e.g. HTTP optimizations[3])
The Figure illustrates the dataflow. Applications interface to the NPV software through some kind of API. Heuschkel et. al. proposed socket API equivalent replacements but envision more sophisticated interfaces for future applications. The application payload is assigned by a scheduler to one (of potentially many) communication stack to get processed to network packets, that get sent using networking hardware. A management component decide how communication stacks get composed and how the scheduling scheme should be. To support decisions a management interface is provided to integrate the management system in software-defined networking contexts.
Implementations
[edit]Currently there is just one academic implementation available to demonstrate the concept. Heuschkel et. al. published this implementation as demonstrator in 2016[4]. The last iteration of this code is available under AGPLv3 on Github.
See also
[edit]References
[edit]- ^ Heuschkel, Jens; Schweizer, Immanuel; Zimmermann, Thorsten; Wehrle, Klaus; Mühlhäuser, Max (2015). "Protocol Virtualization through Dynamic Network Stacks". Proceedings of 1st Workshop on Software-Defined Networking and Network Function Virtualization for Flexible Network Management (SDNFlex).
- ^ Heuschkel, Jens; Wang, Lin; Fleckstein, Erik; Ofenloch, Michael; Blöcher, Marcel; Crowcroft, Jon; Mühlhäuser, Max (2015). "VirtualStack: Flexible Cross-layer Optimization via Network Protocol Virtualization". Proceedings of 43rd Local Computer Networks (LCN) IEEE.
- ^ Heuschkel, Jens; Forstmann, Jens; Wang, Lin; Mühlhäuser, Max (2018). "Identifying the Performance Impairment of HTTP". Proceedings of 42rd Local Computer Networks (LCN) IEEE.
- ^ Heuschkel, Jens; Stein, Michael; Mühlhäuser, Max (2016). "VirtualStack: SDN-controlled Transparent Protocol Transitions At the Edge". Proceedings of 41rd Local Computer Networks (LCN) IEEE.