Interdomain routing performs the critical function of gluing together individual pieces of the Internet topology to create a connected data delivery infrastructure. Today this critical function is performed by the Border Gateway Protocol (BGP) [rfc1771] which establishes reachability information among Autonomous Systems (ASes). However despite its importance, current measurements and analysis have not led to a basic understanding of BGP's dynamics, performance under stress, fundamental weaknesses, and potential breaking points (if any). Although a few data collection points have been set up in the last few years [ripe,routeviews], the routing data collected by these measurement points are mixed with measurement artifacts [ftntalk], thus the data do not necessarily reflect the protocol's behavior in actual operation. In order for the Internet to continue its unprecedented growth, the interdomain routing protocol must continue to evolve to meet ever increasing and sometimes contradictory requirements. There is a general belief that the current BGP routing protocol may be unable to meet its new requirements (for instance, accomodating the sharp increase in use of site multi-homing, which keeps routing tables from optimally small sizes[huston:scale:2001]). BGP is generally thought to be reaching the end of its useful lifetime, although this has not been validated by analysis or measurements [nimrod,irtfrr,huitema:ipng,huston:scale:2001]. Due to the lack of a shared understanding of the problem and lack of sufficient data and analysis, there is no consensus on where/when BGP collapses and what (if anything) should be done.
The BBGP team has identified the following fundamental technical requirements that the global routing must meet: it must scale in order to handle the growth (both in the number of users and in the richness of connectivity); security and resilience are critical issues, so it must continue to function in face of ever increasing faults and attacks; it must be able to fully utilize the rich Internet connectivity; and it must both allow network operators to apply various policy constraints and implementors to easily extend the protocol's functionality when needed. Based on the above criteria the project team proposes to tackle the challenge with the following 3 steps:
BBGP is collaboration between
BBGP is funded by NSF
under Dr. Mari Maeda's
Special Projects program.