Graceful Shutdown of BGP Sessions
draft-dubois-bgp-planned-maintenance-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Nicolas Dubois | ||
| Last updated | 2004-06-30 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-dubois-bgp-planned-maintenance-00.txt
Abstract
To ease the maintenance of BGP-4 sessions and limit the amount of traffic that is lost during planned maintenance on routers, a specific mechanism is proposed in order to gracefully shutdown a router or a session. It's proposed that a router first withdraw its route to its peer to initiate their convergence. After a timer the router can proceed with the closing of the BGP sessions and consequently remove its peers'routes from it's RIB (Routing Information Base).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)