[GROW] BCP 214, RFC 8327 on Mitigating the Negative Impact of Maintenance through BGP Session Culling

rfc-editor@rfc-editor.org Tue, 06 March 2018 22:49 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54D8C12DA3E; Tue, 6 Mar 2018 14:49:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cllFKAkozJ_K; Tue, 6 Mar 2018 14:49:36 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A5DD12D877; Tue, 6 Mar 2018 14:49:36 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 02AFBB80E53; Tue, 6 Mar 2018 14:49:20 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, grow@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180306224920.02AFBB80E53@rfc-editor.org>
Date: Tue, 06 Mar 2018 14:49:20 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/LBBb4KDD5OsbRC-f6TfEoflFV0I>
Subject: [GROW] BCP 214, RFC 8327 on Mitigating the Negative Impact of Maintenance through BGP Session Culling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2018 22:49:44 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 214        
        RFC 8327

        Title:      Mitigating the Negative Impact of 
                    Maintenance through BGP Session Culling 
        Author:     W. Hargrave,
                    M. Griswold,
                    J. Snijders,
                    N. Hilliard
        Status:     Best Current Practice
        Stream:     IETF
        Date:       March 2018
        Mailbox:    will@lonap.net, 
                    grizz@20c.com, 
                    job@ntt.net,
                    nick@inex.ie
        Pages:      10
        Characters: 18087
        See Also:   BCP 214

        I-D Tag:    draft-ietf-grow-bgp-session-culling-05.txt

        URL:        https://www.rfc-editor.org/info/rfc8327

        DOI:        10.17487/RFC8327

This document outlines an approach to mitigate the 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 that will be affected by
maintenance are forcefully torn down before the actual maintenance
activities commence.

This document is a product of the Global Routing Operations Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC