oBGP: an overlay for a scalable iBGP control plane

  • Authors:
  • Iuniana Oprescu;Mickaël Meulle;Steve Uhlig;Cristel Pelsser;Olaf Maennel;Philippe Owezarski

  • Affiliations:
  • Orange Labs, Issy-les-Moulineaux Cedex, France and CNRS, LAAS, Toulouse Cedex, France and Université de Toulouse, UPS, INSA, INP, ISAE, UT1, UTM, LAAS, Toulouse Cedex, France;Orange Labs, Issy-les-Moulineaux Cedex, France;Deutsche Telekom Laboratories & Technische Universität Berlin, Berlin, Germany;Internet Initiative Japan, Tokyo, Japan;University of Loughborough, Department of Computer Science, Loughborough, United Kingdom;CNRS, LAAS, Toulouse Cedex, France and Université de Toulouse, UPS, INSA, INP, ISAE, UT1, UTM, LAAS, Toulouse Cedex, France

  • Venue:
  • NETWORKING'11 Proceedings of the 10th international IFIP TC 6 conference on Networking - Volume Part I
  • Year:
  • 2011

Quantified Score

Hi-index 0.01

Visualization

Abstract

The Internet is organized as a collection of networks called Autonomous Systems (ASes). The Border Gateway Protocol (BGP) is the glue that connects these administrative domains. Communication is thus possible between users worldwide and each network is responsible of sharing reachability information to peers through BGP. Protocol extensions are periodically added because the intended use and design of BGP no longer fit the current demands. Scalability concerns make the required internal BGP (iBGP) full mesh difficult to achieve in today's large networks and therefore network operators resort to confederations or Route Reflectors (RRs) to achieve full connectivity. These two options come with a set of flaws of their own such as persistent routing oscillations, deflections, forwarding loops etc. In this paper we present oBGP, a new architecture for the redistribution of external routes inside an AS. Instead of relying on the usual statically configured set of iBGP sessions, we propose to use an overlay of routing instances that are collectively responsible for (i) the exchange of routes with other ASes, (ii) the storage of internal and external routes, (iii) the storage of the entire routing policy configuration of the AS and (iv) the computation and redistribution of the best routes towards Internet destinations to each router of the AS.