<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.decraene-bgp-graceful-shutdown-requirements" target="https://datatracker.ietf.org/doc/html/draft-decraene-bgp-graceful-shutdown-requirements-01">
   <front>
      <title>Requirements for the graceful shutdown of BGP sessions</title>
      <author initials="B." surname="Decraene" fullname="Bruno Decraene">
         <organization>France Telecom</organization>
      </author>
      <author initials="Z." surname="Ahmad" fullname="Zubair Ahmad">
         <organization>Orange Business Services</organization>
      </author>
      <author initials="A. J. E." surname="Armengol" fullname="Antonio Jose Elizond Armengol">
         </author>
      <author initials="P." surname="Francois" fullname="Pierre Francois">
         <organization>UCL</organization>
      </author>
      <date month="March" day="6" year="2009" />
      <abstract>
	 <t>   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&#x27; or peers&#x27; 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. 
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-decraene-bgp-graceful-shutdown-requirements-01" />
   
</reference>
