RFC 4456

BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP), April 2006

Canonical URL:
https://www.rfc-editor.org/rfc/rfc4456.txt
File formats:
Plain TextPDF
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

DOI:  10.17487/RFC4456

Discuss this RFC: Send questions or comments to idr@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF


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. [STANDARDS-TRACK]


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader



Search RFCs
Advanced Search
×