BGP Persistent Route Oscillation Solutions
draft-walton-bgp-route-oscillation-stop-08
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Daniel Walton , Alvaro Retana , Enke Chen , John Scudder | ||
| Last updated | 2014-04-19 (Latest revision 2013-10-16) | ||
| Replaced by | draft-ietf-idr-route-oscillation-stop, RFC 7964 | ||
| RFC stream | (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
In this document we present two sets of paths for an address prefix that can be advertised by a BGP route reflector or confederation ASBR to eliminate the MED-induced route oscillations in a network. The first set involves all the available paths, and would achieve the same routing consistency as the full IBGP mesh. The second set, which is a subset of the first one, involves the neighbor-AS based Group Best Paths, and would be sufficient to eliminate the MED- induced route oscillations (subject to certain commonly adopted topological constrains).
Authors
Daniel Walton
Alvaro Retana
Enke Chen
John Scudder
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)