External failure propagation
draft-raszuk-ext-failure-propagation-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Robert Raszuk | ||
| Last updated | 2005-07-05 | ||
| 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
The current BGP specification calls for sending prefix based routing information when a BGP peer fails to all other peers so that they could converge using the new information. Certain network events could be communicated to BGP speakers in an aggregated fashion. This not only minimizes control plane traffic but more importantly reduces the time to react to these events by the The current BGP specification calls for sending prefix based routing information when a BGP peer fails to all other peers so that they could converge using the new information. Certain network events could be communicated to BGP speakers in an aggregated fashion. This not only minimizes control plane traffic but more importantly reduces the time to react to these events by the
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)