RFC 4456 - BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)
Network Working Group T. Bates - Cisco Systems E. Chen - Cisco Systems R. Chandra - Sonoa Systems April 2006
Category: Standards Track Obsoletes: RFC 2796, RFC 1966
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
The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for TCP/IP internets. Typically, all BGP speakers within a single AS must be fully meshed so that any external routing information must be re-distributed to all other routers within that Autonomous System (AS). This represents a serious scaling problem that has been well documented with several alternatives proposed.
This document describes the use and design of a method known as "route reflection" to alleviate the need for "full mesh" Internal BGP (IBGP).
This document obsoletes RFC 2796 and RFC 1966.
Table of Contents
- 1. Introduction
- 2. Specification of Requirements
- 3. Design Criteria
- 4. Route Reflection
- 5. Terminology and Concepts
- 6. Operation
- 7. Redundant RRs
- 8. Avoiding Routing Information Loops
- 9. Impact on Route Selection
- 10. Implementation Considerations
- 11. Configuration and Deployment Considerations
- 12. Security Considerations
- 13. Acknowledgements
- 14. References
- Appendix A: Comparison with RFC 2796
- Appendix B: Comparison with RFC 1966