IBGP Auto Mesh

Document Type Expired Internet-Draft (individual)
Author Robert Raszuk 
Last updated 2003-06-24
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The distribution of BGP routing information within an autonomous system requires all border routers to be fully meshed. This constitutes a significant operational problem in terms of configuration management. This has led to the wide-spread adoption of route reflection [RFC2796], primarily in order to reduce the number systems which configuration must be modified in order to introduce or remove a new internal BGP speaker. Route reflection, however, implies with it information reduction which is not always desired. This document defines a discovery mechanism that is designed to address the problem of introducing (or removing) a BGP speaker into an iBGP mesh without implying any other behavior change when compared to manual configuration.


Robert Raszuk (raszuk@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)