xBGP: When you can’t wait for the IETF and vendors
Abstract
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.
People
BibTex
@inproceedings{wirtgen2020vendors,
author = {Wirtgen, Thomas and Coninck, Quentin De and Bush, Randy and Vanbever, Laurent and Bonaventure, Olivier},
title = {{xBGP: When you can't wait for the IETF and vendors}},
booktitle = {Proceedings of the 19th ACM Workshop on Hot Topics in Networks},
address = {Chicago, IL, USA},
year = 2020,
month = nov,
publisher = {Association for Computing Machinery},
doi = {10.1145/3422604.3425952},
url = {https://doi.org/10.1145/3422604.3425952}
}Research Collection: 20.500.11850/452272
