@misc{rfc6198,
    series =    {Request for Comments},
    number =    6198,
    howpublished =  {RFC 6198},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC6198},
    url =       {https://www.rfc-editor.org/info/rfc6198},
    author =    {Cristel Pelsser and Antonio Jose Elizond Armengol and Bruno Decraene and Zubair Ahmad and Tomonori Takeda and Pierre Francois},
    title =     {{Requirements for the Graceful Shutdown of BGP Sessions}},
    pagetotal = 20,
    year =      2011,
    month =     apr,
    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.},
}