RFC 4271 - A Border Gateway Protocol 4 (BGP-4)
Network Working Group
Y. Rekhter, Ed. - Cisco Systems
T. Li, Ed. - Cisco Systems
S. Hares, Ed. - NextHop Technologies
January 2006
Category: Standards Track
Obsoletes: RFC 1771
Status of This Memo
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This document discusses the Border Gateway Protocol (BGP), which is an inter-Autonomous System routing protocol.
The primary function of a BGP speaking system is to exchange network reachability information with other BGP systems. This network reachability information includes information on the list of Autonomous Systems (ASes) that reachability information traverses. This information is sufficient for constructing a graph of AS connectivity for this reachability from which routing loops may be pruned, and, at the AS level, some policy decisions may be enforced.
BGP-4 provides a set of mechanisms for supporting Classless Inter-Domain Routing (CIDR). These mechanisms include support for advertising a set of destinations as an IP prefix, and eliminating the concept of network "class" within BGP. BGP-4 also introduces mechanisms that allow aggregation of routes, including aggregation of AS paths.
This document obsoletes RFC 1771.
Table of Contents
- 1. Introduction
- 2. Acknowledgements
- 3. Summary of Operation
- 4. Message Formats
- 5. Path Attributes
- 6. BGP Error Handling
- 7. BGP Version Negotiation
- 8. BGP Finite State Machine (FSM)
- 9. UPDATE Message Handling
- 10. BGP Timers
- Appendix A. Comparison with RFC 1771
- Appendix B. Comparison with RFC 1267
- Appendix C. Comparison with RFC 1163
- Appendix D. Comparison with RFC 1105
- Appendix E. TCP Options that May Be Used with BGP
- Appendix F. Implementation Recommendations
- Security Considerations
- IANA Considerations
- References