The Case for Pluginized Routing Protocols

Wirtgen, Thomas; Denos, Cyril; Coninck, Quentin De; Jadin, Mathieu; Bonaventure, Olivier

doi:10.1109/icnp.2019.8888065

Cited by 4 publications

(4 citation statements)

References 49 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…FRR, as a control plane, and VPP + DPDK, as a data plane, are located in user space. However, the Network Interface Card (NIC) is completely in control of DPDK, therefore, the kernel will not be able to see or manipulate it [14,55]. The main details of this architecture should be mentioned, including Zebra and Router plugins.…”

Section: Overall Design Architecturementioning

confidence: 99%

“…So far, VPLS is vendor-specific, which means that in order to support VPLS on a vendor's device, the service provider should purchase VPLS modules that are only compatible with its own product, and also in this situation, it is unclear if the VPLS module is inter-operable with that of the device of other vendors located somewhere else. This gives us the inspiration to implement a vendor-agnostic VPLS on high-speed and commodity routers [4,12,14]. The development of new VPLS applications necessitates the incorporation of new operational needs, such as improved security, streamlined service provisioning, better network resource use, improved scalability, and autonomous network management support [15,16].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Developing a Novel Hierarchical VPLS Architecture Using Q-in-Q Tunneling in Router and Switch Design

Biabani,

Yazdani,

Fotouhi

2023

Computers

View full text Add to dashboard Cite

Virtual Private LAN Services (VPLS) is an ethernet-based Virtual Private Network (VPN) service that provides multipoint-to-multipoint Layer 2 VPN service, where each site is geographically dispersed across a Wide Area Network (WAN). The adaptability and scalability of VPLS are limited despite the fact that they provide a flexible solution for connecting geographically dispersed sites. Furthermore, the construction of tunnels connecting customer locations that are separated by great distances adds a substantial amount of latency to the user traffic transportation. To address these issues, a novel Hierarchical VPLS (H-VPLS) architecture has been developed using 802.1Q tunneling (also known as Q-in-Q) on high-speed and commodity routers to satisfy the additional requirements of new VPLS applications. The Vector Packet Processing (VPP) performs as the router’s data plane, and FRRouting (FRR), an open-source network routing software suite, acts as the router’s control plane. The router is designed to seamlessly forward VPLS packets using the Request For Comments (RFCs) 4762, 4446, 4447, 4448, and 4385 from The Internet Engineering Task Force (IETF) integrated with VPP. In addition, the Label Distribution Protocol (LDP) is used for Multi-Protocol Label Switching (MPLS) Pseudo-Wire (PW) signaling in FRR. The proposed mechanism has been implemented on a software-based router in the Linux environment and tested for its functionality, signaling, and control plane processes. The router is also implemented on commodity hardware for testing the functionality of VPLS in the real world. Finally, the analysis of the results verifies the efficiency of the proposed mechanism in terms of throughput, latency, and packet loss ratio.

show abstract

Section: Overall Design Architecturementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Developing a Novel Hierarchical VPLS Architecture Using Q-in-Q Tunneling in Router and Switch Design

Biabani,

Yazdani,

Fotouhi

2023

Computers

View full text Add to dashboard Cite

show abstract

“…Extending Network Functionality Using eBPF to program the Linux kernel network stack, multiple works propose extension systems for IPv6 [27,56], OSPF [55], TCP [8,27,49], Multipath TCP [22], BGP [55], and QUIC [16]. All these approaches, however, rely on the C language with its downsides.…”

Section: Related Workmentioning

confidence: 99%

ReactiFi: Reactive Programming of Wi-Fi Firmware on Mobile Devices

Sterz¹,

Eichholz²,

Mogk³

et al. 2020

Programming

View full text Add to dashboard Cite

Network programmability will be required to handle future increased network traffic and constantly changing application needs. However, there is currently no way of using a high-level, easy to use programming language to program Wi-Fi firmware. This impedes rapid prototyping and deployment of novel network services/applications and hinders continuous performance optimization in Wi-Fi networks, since expert knowledge is required for both the used hardware platforms and the Wi-Fi domain. In this paper, we present ReactiFi, a high-level reactive programming language to program Wi-Fi chips on mobile consumer devices. ReactiFi enables programmers to implement extensions of PHY, MAC, and IP layer mechanisms without requiring expert knowledge of Wi-Fi chips, allowing for novel applications and network protocols. ReactiFi programs are executed directly on the Wi-Fi chip, improving performance and power consumption compared to execution on the main CPU. ReactiFi is conceptually similar to functional reactive languages, but is dedicated to the domain-specific needs of Wi-Fi firmware. First, it handles low-level platform-specific details without interfering with the core functionality of Wi-Fi chips. Second, it supports static reasoning about memory usage of applications, which is important for typically memory-constrained Wi-Fi chips. Third, it limits dynamic changes of dependencies between computations to dynamic branching, in order to enable static reasoning about the order of computations. We evaluate ReactiFi empirically in two real-world case studies. Our results show that throughput, latency, and power consumption are significantly improved when executing applications on the Wi-Fi chip rather than in the operating system kernel or in user space. Moreover, we show that the high-level programming abstractions of ReactiFi have no performance overhead compared to manually written C code. ACM CCS 2012Software and its engineering → Domain specific languages;

show abstract

“…Related Works The architecture of routing protocol implementations such as XORP was designed with extensibility in mind [19], but it does not expose a vendor-neutral API. We previously added eBPF to the FRRouting implementation [40], but the proposed eBPF programs could only be used inside this implementation. Transport protocols researchers have proposed using extension codes to dynamically extend transport protocols like STP [31] or QUIC [10].…”

Section: Xbgp Meets Actual Bgp Implementationsmentioning

confidence: 99%

xBGP

Wirtgen

Coninck

Bush

et al. 2020

Proceedings of the 19th ACM Workshop on Hot Topics in Networks

Self Cite

View full text Add to dashboard Cite

Thanks to the standardization of routing protocols such as BGP, OSPF or IS-IS, Internet Service Providers (ISP) and enterprise networks can deploy routers from various vendors. This prevents them from vendor-lockin problems. Unfortunately, this also slows innovation since any new feature must be standardized and implemented by all vendors before being deployed. We propose a paradigm shift that enables network operators to program the routing protocols used in their networks. We demonstrate the feasibility of this approach with xBGP. xBGP is a vendor neutral API that exposes the key data structures and functions of any BGP implementation. Each xBGP compliant implementation includes an eBPF virtual machine that executes the operator supplied programs. We extend FRRouting and BIRD to support this new paradigm and demonstrate the flexibility of xBGP with four different use cases. Finally, we discuss how xBGP could affect future research on future routing protocols. CCS CONCEPTS • Networks → Network protocol design; Routing protocols; Programming interfaces; Programmable networks.

show abstract

The Case for Pluginized Routing Protocols

Cited by 4 publications

References 49 publications

Developing a Novel Hierarchical VPLS Architecture Using Q-in-Q Tunneling in Router and Switch Design

Developing a Novel Hierarchical VPLS Architecture Using Q-in-Q Tunneling in Router and Switch Design

ReactiFi: Reactive Programming of Wi-Fi Firmware on Mobile Devices

xBGP

Contact Info

Product

Resources

About