ACM Home Page
Please provide us with feedback. Feedback
On the correctness of IBGP configuration
Full text PdfPdf (328 KB)
Source Applications, Technologies, Architectures, and Protocols for Computer Communication archive
Proceedings of the 2002 conference on Applications, technologies, architectures, and protocols for computer communications table of contents
Pittsburgh, Pennsylvania, USA
SESSION: BGP analysis table of contents
Pages: 17 - 29  
Year of Publication: 2002
ISBN:1-58113-570-X
Also published in ...
Authors
Timothy G. Griffin  AT&T Research
Gordon Wilfong  Bell Labs, Lucent Technologies
Sponsors
ACM: Association for Computing Machinery
SIGCOMM: ACM Special Interest Group on Data Communication
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 13,   Downloads (12 Months): 50,   Citation Count: 29
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/633025.633028
What is a DOI?

ABSTRACT

The Border Gateway Protocol (BGP) has two distinct modes of operation. External BGP (EBGP) exchanges reachability information between autonomous systems, while Internal BGP (IBGP) exchanges external reachability information within an autonomous system. We study several routing anomalies that are unique to IBGP because, unlike EBGP, forwarding paths and signaling paths are not always symmetric. In particular, we focus on anomalies that can cause the protocol to diverge, and those that can cause a router's chosen forwarding path to an egress point to be deflected by another router on that path. Deflections can greatly complicate the debugging of routing problems, and in the worst case multiple deflections can combine to form persistent forwarding loops. We define a correct IBGP configuration to be one that is anomaly free for every possible set of routes sent by neighboring autonomous systems. We show that determination of IBGP configuration correctness is NP-hard. However, we give simple sufficient conditions on network configurations that guarantee correctness.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
T. Bates, R. Chandra, and E. Chen. BGP route reflection: An alternative to full mesh IBGP. RFC 2796, 2000.
 
3
Marc Blanchet, Florent Parent, and Bill St-Arnaud. Optical BGP (OBGP): InterAS lightpath provisioning. Internet Draft draft-parent-obgp-01.txt. Work in progress.
 
4
Cisco. Endless BGP Convergence Problem in Cisco IOS Software Releases. Field Note, October 10 2001, http://www.cisco.com/warp/public/770/fn12942.html.
5
6
 
7
L. Gao, T. G. Grin, and J. Rexford. Inherently safe backup routing with BGP. In Proceedings of the 20th IEEE Conference on Computer Communications (Infocom 2001), Anchorage, Alaska, April 2001.
8
 
9
 
10
T. G. Griffin and G. Wilfong. A safe path vector protocol. In Proceedings of the 19th Annual IEEE Conference on Computer Communications (Infocom 2000), Tel Aviv, Israel, March 2000.
 
11
 
12
13
 
14
Timothy G. Griffin and Gordon Wilfong. Analysis of the MED oscillation problem in BGP. unpublished manuscript, 2002.
 
15
 
16
17
 
18
D. McPherson, V. Gill, D. Walton, and A. Retana. BGP persistent route oscillation condition. Internet Draft draft-ietf-idr-route-oscillation-01.txt , Work In Progress, 2002.
 
19
Y. Rekhter and T. Li. A Border Gateway Protocol. RFC 1771 (BGP version 4), March 1995.
 
20
Jonathan Rosenberg, Hussein Salma, and Matt Squire. Telephony routing over IP (TRIP). RFC 3219. January 2002.
 
21
P. Traina, D. McPherson, and J. Scudder. Autonomous system confederations for BGP. RFC 3056, 2001.
 
22
Kanan Varadhan, Ramesh Govindan, and Deborah Estrin. Persistent route oscillations in inter-domain routing. Computer Networks, 32:1--16, 2000.

CITED BY  29

Collaborative Colleagues:
Timothy G. Griffin: colleagues
Gordon Wilfong: colleagues