BGP Protocol Analysis (RFC1265)
Original Publication Date: 1991-Oct-01
Included in the Prior Art Database: 2019-Feb-11
Internet Society Requests For Comment (RFCs)
This report summarizes the key feature of BGP, and analyzes the protocol with respect to scaling and performance. This memo provides information for the Internet community. It does not specify an Internet standard.
Network Working Group Y. Rekhter, Editor Request for Comments: 1265 T.J. Watson Research Center, IBM Corp. October 1991
BGP Protocol Analysis
1. Status of this Memo.
This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited.
The purpose of this report is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by the Border Gateway Protocol (BGP). This report summarizes the key feature of BGP, and analyzes the protocol with respect to scaling and performance. This is the first of two reports on the BGP protocol.
BGP is an inter-autonomous system routing protocol designed for the TCP/IP internets. Version 1 of the BGP protocol was published in RFC 1105. Since then BGP versions 2 and 3 have been developed. Version 2 was documented in RFC 1163. Version 3 is documented in . The changes between versions 1, 2 and 3 are explained in Appendix 3 of .
Possible applications of BGP in the Internet are documented in .
Please send comments to firstname.lastname@example.org.
The BGP protocol has been developed by the IWG/BGP Working Group of the Internet Engineering Task Force. We would like to express our deepest thanks to Guy Almes (Rice University) who was the previous chairman of the IWG Working Group. We also like to explicitly thank Bob Braden (ISI) and Bob Hinden (BBN) for the review of this document as well as their constructive and valuable comments.
4. Key features and algorithms of the BGP protocol.
This section summarizes the key features and algorithms of the BGP protocol. BGP is an inter-autonomous system routing protocol; it is designed to be used between multiple autonomous systems. BGP assumes that routing within an autonomous system is done by an intra- autonomous system routing protocol. BGP does not make any assumptions
BGP Working Group [Page 1]
RFC 1265 BGP Protocol Analysis October 1991
about intra-autonomous system routing protocols employed by the various autonomous systems. Specifically, BGP does not require all autonomous systems to run the same intra-autonomous system routing protocol.
BGP is a real inter-autonomous system routing protocol. It imposes no constraints on the underlying Internet topology. The information exchanged via BGP is sufficient to construct a graph of autonomous systems connectivity from which routing loops may be pruned and some routing policy decisions at the autonomous system level may be enforced.
The key feature of the protocol is the notion of Path Attributes. This feature provides BGP with flexibility and expandability. Path attributes are partitioned into well-known and optional. The provision for optional attributes allows experimentation that may involve a group of BGP routers without affecting the rest of the Internet. New optional attributes can be added to the protocol in much the same fashion as new options are added to the Telnet protocol...