RFC 1966: BGP Route Reflection An alternative to full mesh IBGP
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4456.
Current document in this lineage: RFC 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)
In plain English — editorial summary, not part of the RFC
This document describes the use and design of a method known as "Route Reflection" to alleviate the the need for "full mesh" IBGP. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC1966
- Published
- June 1996
- Authors
- T. Bates; R. Chandra
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 7
- Also known as
- —
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
2 later RFCs formally update or obsolete 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 1965Autonomous System Confederations for BGPObsoleted
June 1996
- RFC 1997BGP Communities AttributeUpdated
August 1996
- RFC 1998An Application of the BGP Community Attribute in Multi-home RoutingCurrent
August 1996
- RFC 1930Guidelines for creation, selection, and registration of an Autonomous System (AS)Updated
March 1996
- RFC 1863A BGP/IDRP Route Server alternative to a full mesh routingObsoleted
October 1995
- RFC 1773Experience with the BGP-4 protocolCurrent
March 1995
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?