More From This User
Related Docuements
bgp
From ManoKhalil
Network Working Group K. LougheedRequest for Comments: 1163 cisco SystemsObsoletes: RFC 1105 Y. RekhterT.J. Watson Research Center, IBM CorpJune 1990A Border Gateway Protocol (BGP)Status of this MemoThis RFC, together with its companion RFC-1164, "Application of theBorder Gateway Protocol in the Internet", define a Proposed Standardfor an inter-autonomous system routing protocol for the Internet.This protocol, like any other at this initial stage, may undergomodifications before reaching full Internet Standard status as aresult of deployment experience. Implementers are encouraged totrack the progress of this or any protocol as it moves through thestandardization process, and to report their own experience with theprotocol.This protocol is being considered by the Interconnectivity WorkingGroup (IWG) of the Internet Engineering Task Force (IETF).Information about the progress of BGP can be monitored and/orreported on the IWG mailing list (IWG@nri.reston.va.us).Please refer to the latest edition of the "IAB Official ProtocolStandards" RFC for current information on the state and status ofstandard Internet protocols.Distribution of this memo is unlimited.Table of Contents1. Acknowledgements...................................... 22. Introduction.......................................... 23. Summary of Operation.................................. 44. Message Formats....................................... 54.1 Message Header Format................................. 54.2 OPEN Message Format................................... 64.3 UPDATE Message Format................................. 84.4 KEEPALIVE Message Format.............................. 104.5 NOTIFICATION Message Format........................... 105. Path Attributes....................................... 126. BGP Error Handling.................................... 146.1 Message Header error handling......................... 146.2 OPEN message error handling........................... 15Lougheed & Rekhter [Page 1]
RFC 1163 BGP June 19906.3 UPDATE message error handling......................... 166.4 NOTIFICATION message error handling................... 176.5 Hold Timer Expired error handling..................... 176.6 Finite State Machine error handling................... 186.7 Cease................................................. 187. BGP Version Negotiation............................... 188. BGP Finite State machine.............................. 189. UPDATE Message Handling............................... 2210. Detection of Inter-AS Policy Contradictions........... 23Appendix 1. BGP FSM State Transitions and Actions........ 25Appendix 2. Comparison with RFC 1105..................... 28Appendix 3. TCP options that may be used with BGP........ 28References................................................ 29Security Considerations................................... 29Authors' Addresses........................................ 291. AcknowledgementsWe would like to express our thanks to Guy Almes (Rice University),Len Bosack (cisco Systems), Jeffrey C. Honig (Cornell Theory Center)and all members of the Interconnectivity Working Group of theInternet Engineering Task Force, chaired by Guy Almes, for theircontributions to this document.We would also like to thank Bob Hinden, Director for Routing of theInternet Engineering Steering Group, and the team of reviewers heassembled to review earlier versions of this document. This team,consisting of Deborah Estrin, Milo Medin, John Moy, Radia Perlman,Martha Steenstrup, Mike St. Johns, and Paul Tsuchiya, acted with astrong combination of toughness, professionalism, and courtesy.2. IntroductionThe Border Gateway Protocol (BGP) is an inter-Autonomous Systemrouting protocol. It is built on experience gained with EGP asdefined in RFC 904 [1] and EGP usage in the NSFNET Backbone asdescribed in RFC 1092 [2] and RFC 1093 [3].The primary function of a BGP speaking system is to exchange networkreachability information with other BGP systems. This networkreachability information includes information on the full path ofAutonomous Systems (ASs) that traffic must transit to reach thesenetworks. This information is sufficient to construct a graph of ASconnectivity from which routing loops may be pruned and some policydecisions at the AS level may be enforced.To characterize the set of policy decisions that can be enforcedusing BGP, one must focus on the rule that an AS advertize to itsLougheed & Rekhter [Page 2]
of 00
rfc1163
90 Reads
Info and Rating
| Category: | Uncategorized. |
| Rating: | |
| Upload Date: | 02/05/2008 |
| Copyright: | Attribution Non-commercial |
| Tags: |
Leave a Comment