BGP Route Reflection - An Alternative to Full Mesh IBGP

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 11
Abstract: 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]
Publication Date: 2000-04-01
Status Note: Proposed Standard
DOI: 10.17487/RFC2796
Link: https://doi.org/10.17487/RFC2796
Author(s): Tony J. Bates
Ravi Chandra
Enke Chen
Keyword(s): BGP

Latest version of IETF RFC 2796

Document Versions — IETF RFC 2796

▶ IETF RFC 2796 (2000-04-01)

THIS DOC [SUPERSEDED] [LATEST VERSION]

Superseded by:

RFC4456 NOT IN REGISTRY

Bibliographic Reference(s)

IETF RFC 1771 [Superseded*]
RFC1863 — 2 EXTERNAL
IETF RFC 1965 [Superseded*]
IETF RFC 1966 [Superseded*]
IETF RFC 2385 [Superseded*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC2796.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 2796, BGP Route Reflection - An Alternative to Full Mesh IBGP. Available at https://doi.org/10.17487/RFC2796

Snippet:

IETF RFC 2796, BGP Route Reflection - An Alternative to Full Mesh IBGP. Available at https://doi.org/10.17487/RFC2796

HTML (ISO 690 compliant)

Preview:

IETF RFC 2796, BGP Route Reflection - An Alternative to Full Mesh IBGP. Available at https://doi.org/10.17487/RFC2796

Snippet:

<span class="citation"><cite>IETF RFC 2796</cite>, BGP Route Reflection - An Alternative to Full Mesh IBGP. Available at <a href="https://doi.org/10.17487/RFC2796" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2796</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 2796, BGP Route Reflection - An Alternative to Full Mesh IBGP
doi: 10.17487/RFC2796
url: https://doi.org/10.17487/RFC2796

Snippet:

<li>
<cite id="bib-rfc2796">IETF RFC 2796</cite>, BGP Route Reflection - An Alternative to Full Mesh IBGP
<span class="doi">10.17487/RFC2796</span>
</li>

Referenced By

IETF RFC 3065 [Superseded*]
IETF RFC 4271 [Active*]
IETF RFC 4364 [Active*]
IETF RFC 4664 [Active*]