Search RFCs
RFC 4456
BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP),April 2006
- File formats:
- Status:
- DRAFT STANDARD
- Obsoletes:
- RFC 2796,RFC 1966
- Updated by:
- RFC 7606
- Authors:
- T. Bates
E. Chen
R. Chandra - Stream:
- IETF
- Source:
- idr (rtg)
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC4456
Discuss this RFC: Send questions or comments to the mailing listidr@ietf.org
Other actions:View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 4456
Abstract
The Border Gateway Protocol (BGP) is an inter-autonomous systemrouting protocol designed for TCP/IP internets. Typically, all BGPspeakers within a single AS must be fully meshed so that any externalrouting information must be re-distributed to all other routerswithin that Autonomous System (AS). This represents a serious scalingproblem 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" InternalBGP (IBGP).
This document obsoletes RFC 2796 and RFC 1966. [STANDARDS-TRACK]
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.