metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

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

Document record

Document ID
RFC2796
Published
April 2000
Authors
T. Bates; R. Chandra; E. Chen
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
11
Also known as
—
Obsoleted by:
RFC 4456
Updates:
RFC 1966

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 1966 (1996)
  2. RFC 2796 (2000)
  3. 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.

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?

canonical URL: /rfc/2796-bgp-route-reflection-an-alternative-to-full-mesh-ibgp