[GROW] Last Call: <draft-ietf-grow-bgp-session-culling-04.txt> (Mitigating Negative Impact of Maintenance through BGP Session Culling) to Best Current Practice

The IESG <iesg-secretary@ietf.org> Mon, 11 September 2017 16:28 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
CC: grow-chairs@ietf.org, grow@ietf.org, Christopher Morrow <christopher.morrow@gmail.com>, christopher.morrow@gmail.com, draft-ietf-grow-bgp-session-culling@ietf.org, warren@kumari.net
Reply-To: ietf@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <150514733395.9749.7200491546127557512.idtracker@ietfa.amsl.com>
Date: Mon, 11 Sep 2017 09:28:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/hUcRWl9dgPZm24mvkBrQj8n6ZHw>
Subject: [GROW] Last Call: <draft-ietf-grow-bgp-session-culling-04.txt> (Mitigating Negative Impact of Maintenance through BGP Session Culling) to Best Current Practice

The IESG has received a request from the Global Routing Operations WG (grow)
to consider the following document: - 'Mitigating Negative Impact of
Maintenance through BGP Session Culling'
  <draft-ietf-grow-bgp-session-culling-04.txt> as Best Current Practice

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
ietf@ietf.org mailing lists by 2017-09-25. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   This document outlines an approach to mitigate negative impact on
   networks resulting from maintenance activities.  It includes guidance
   for both IP networks and Internet Exchange Points (IXPs).  The
   approach is to ensure BGP-4 sessions affected by the maintenance are
   forcefully torn down before the actual maintenance activities
   commence.




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

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-session-culling/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: 
    rfc4271: A Border Gateway Protocol 4 (BGP-4) (Draft Standard - IETF stream)

[GROW] Last Call: <draft-ietf-grow-bgp-session-cu… The IESG