Last Call: <draft-ietf-grow-bgp-gshut-13.txt> (Graceful BGP session shutdown) to Proposed Standard

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Last Call: <draft-ietf-grow-bgp-gshut-13.txt> (Graceful BGP session shutdown) to Proposed Standard

The IESG-3

The IESG has received a request from the Global Routing Operations WG (grow)
to consider the following document: - 'Graceful BGP session shutdown'
  <draft-ietf-grow-bgp-gshut-13.txt> as Proposed Standard

This is a second IETF Last Call. The document had an initial LC as an Informational
document, but the IESG felt it was more appropriate to be Standards Track. As the
Last Call time will run into the end of the year holiday period, we are requesting
a 4-week Last Call.

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
[hidden email] mailing lists by 2018-01-11. Exceptionally, comments may be
sent to [hidden email] instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   This draft standardizes a new well-known BGP community
   GRACEFUL_SHUTDOWN to signal the graceful shutdown of paths.  This
   draft also describes operational procedures which use this community
   to reduce the amount of traffic lost when BGP peering sessions are
   about to be shut down deliberately, e.g. for planned maintenance.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-gshut/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-gshut/ballot/


No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information:
    rfc6198: Requirements for the Graceful Shutdown of BGP Sessions (Informational - IETF stream)