Graceful Restart Mechanism for BGP
draft-chen-idr-rfc4724bis-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Srihari R. Sangli , Enke Chen , Rex Fernando , John Scudder , Yakov Rekhter | ||
| Last updated | 2012-03-26 (Latest revision 2011-08-29) | ||
| 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
This document describes a mechanism for BGP that would help minimize the negative effects on routing caused by BGP restart. An End-of-RIB marker is specified and can be used to convey routing convergence information. A new BGP capability, termed "Graceful Restart Capability", is defined that would allow a BGP speaker to express its ability to preserve its forwarding state during BGP restart, as well as to convey its intention of generating the End-of-RIB marker upon the completion of its initial routing update. Finally, procedures are outlined for temporarily retaining routing information across a TCP session termination/re-establishment. The mechanisms described in this document are applicable to all routers, both those with the ability to preserve the forwarding state during BGP restart and those without (although the latter need to implement only a subset of the mechanisms described in this document).
Authors
Srihari R. Sangli
Enke Chen
Rex Fernando
John Scudder
Yakov Rekhter
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)