Requirements for planned maintenance of BGP sessions
draft-dubois-bgp-pm-reqs-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2005-07-20 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-dubois-bgp-pm-reqs-02.txt
https://www.ietf.org/archive/id/draft-dubois-bgp-pm-reqs-02.txt
Abstract
To ease the maintenance of BGP [BGP] sessions and limit the amount of traffic that is lost during planned maintenance operations on routers, a solution is required in order to gracefully shutdown a router or a session.
Authors
Nicolas Dubois (nicolas.dubois@francetelecom.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)