Route Reflection Considered Harmful
draft-dube-route-reflection-harmful-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | John Scudder , Rohit Dube | ||
| Last updated | 1998-11-04 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Route reflection as defined by [2] is a popular way of reducing the full-mesh IBGP peering required by routers running the Border Gateway Protocol [1]. There are cases where a topology built using route reflectors produces persistent loops or does not produce the same results as what one would expect with a full IBGP mesh. This document describes these problems.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)