Requirements for the graceful shutdown of BGP sessions
draft-decraene-bgp-graceful-shutdown-requirements-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2009-03-06 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
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) | ||
https://www.ietf.org/archive/id/draft-decraene-bgp-graceful-shutdown-requirements-01.txt
Abstract
The BGP protocol is heavily used in Service Provider networks both for Internet and BGP/MPLS VPN services. For resiliency purposes, redundant routers and BGP sessions can be deployed to reduce the consequences of an AS Border Router or BGP session breakdown on customers' or peers' traffic. However simply taking down or even up a BGP session for maintenance purposes may still induce connectivity losses during the BGP convergence. This is no more satisfactory for new applications (e.g. voice over IP, on line gaming, VPN). Therefore, a solution is required for the graceful shutdown of a (set of) BGP session(s) in order to limit the amount of traffic loss during a planned shutdown. This document expresses requirements for such a solution.
Authors
Bruno Decraene
(bruno.decraene@orange-ftgroup.com)
Zubair Ahmad
(zubair.ahmad@orange-ftgroup.com)
Antonio Armengol
(ajea@tid.es)
Pierre Francois
(francois@info.ucl.ac.be)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)