RFC 4456: BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC4456
- Published
- April 2006
- Authors
- T. Bates; E. Chen; R. Chandra
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
- Updated by:
- RFC 7606
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1966 (1996)
- RFC 2796 (2000)
- RFC 4456 (2006)
Read the full history of BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent
January 1998
- RFC 1364BGP OSPF InteractionObsoleted
September 1992
- RFC 4364BGP/MPLS IP Virtual Private Networks (VPNs)Updated
February 2006
- RFC 4223Reclassification of RFC 1863 to HistoricCurrent
October 2005
- RFC 2858Multiprotocol Extensions for BGP-4Obsoleted
June 2000
- RFC 2842Capabilities Advertisement with BGP-4Obsoleted
May 2000
- RFC 2519A Framework for Inter-Domain Route AggregationCurrent
February 1999
- RFC 2283Multiprotocol Extensions for BGP-4Obsoleted
February 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?