Requirements for the Graceful Shutdown of BGP Sessions
RFC 6198, “Requirements for the Graceful Shutdown of BGP Sessions”, is an Informational document published in April 2011 by B. Decraene, P. Francois, C. Pelsser, Z. Ahmad, A.J. Elizondo Armengol, T. Takeda. The canonical text is published by the RFC Editor.
Abstract
The Border Gateway Protocol (BGP) is heavily used in Service Provider networks for both Internet and BGP/MPLS VPN services. For resiliency purposes, redundant routers and BGP sessions can be deployed to reduce the consequences of an Autonomous System Border Router (ASBR) or BGP session breakdown on customers' or peers' traffic. However, simply taking down or even bringing up a BGP session for maintenance purposes may still induce connectivity losses during the BGP convergence. This is no longer satisfactory for new applications (e.g., voice over IP, online 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. This document is not an Internet Standards Track specification; it is published for informational purposes.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6198 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6197 Location-to-Service Translation Service List Boundary Extension
- RFC 6196 Moving mailserver: URI Scheme to Historic
- RFC 6195 Domain Name System IANA Considerations
- RFC 6201 Device Reset Characterization
- RFC 6194 Security Considerations for the SHA-0 and SHA-1 Message-Digest Algorithms
- RFC 6202 Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP
- RFC 6193 Media Description for the Internet Key Exchange Protocol in the Session Description Protocol
- RFC 6203 IMAP4 Extension for Fuzzy Search