Mitigating the Negative Impact of Maintenance through BGP Session Culling
RFC 8327

Document Type RFC - Best Current Practice (March 2018; Errata)
Also known as BCP 214
Last updated 2018-03-07
Replaces draft-iops-grow-bgp-session-culling
Stream IETF
Formats plain text pdf html bibtex
Reviews SECDIR will not review this version
Stream WG state Submitted to IESG for Publication
Document shepherd Christopher Morrow
Shepherd write-up Show (last changed 2017-09-06)
IESG IESG state RFC 8327 (Best Current Practice)
Consensus Boilerplate Yes
Telechat date
Responsible AD Warren Kumari
Send notices to Christopher Morrow <christopher.morrow@gmail.com>
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IANA Actions
Internet Engineering Task Force (IETF)                       W. Hargrave
Request for Comments: 8327                                         LONAP
BCP: 214                                                     M. Griswold
Category: Best Current Practice                                      20C
ISSN: 2070-1721                                              J. Snijders
                                                                     NTT
                                                             N. Hilliard
                                                                    INEX
                                                              March 2018

         Mitigating the Negative Impact of Maintenance through
                          BGP Session Culling

Abstract

   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.

Status of This Memo

   This memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   BCPs is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8327.

Hargrave, et al.          Best Current Practice                 [Page 1]
RFC 8327                   BGP Session Culling                March 2018

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  BGP Session Culling . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Voluntary BGP Session Teardown Recommendations  . . . . .   4
       3.1.1.  Maintenance Considerations  . . . . . . . . . . . . .   4
     3.2.  Involuntary BGP Session Teardown Recommendations  . . . .   4
       3.2.1.  Packet-Filter Considerations  . . . . . . . . . . . .   5
       3.2.2.  Hardware Considerations . . . . . . . . . . . . . . .   5
     3.3.  Procedural Considerations . . . . . . . . . . . . . . . .   6
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Appendix A.  Example Packet Filters . . . . . . . . . . . . . . .   8
     A.1.  Example Configuration for Cisco IOS, IOS XR, and Arista
           EOS . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
     A.2.  Example Configuration for Nokia SR OS . . . . . . . . . .   9
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

Hargrave, et al.          Best Current Practice                 [Page 2]
RFC 8327                   BGP Session Culling                March 2018

1.  Introduction

   BGP Session Culling is the practice of ensuring BGP sessions are
   forcefully torn down before maintenance activities on a lower-layer
   network commence -- activities that otherwise would affect the flow
   of data between the BGP speakers.  BGP Session Culling is the
   practice of ensuring BGP sessions are forcefully torn down before
   commencing maintenance activities (that otherwise would affect the
   flow of data between the BGP speakers) on a lower-layer network.

   BGP Session Culling minimizes the amount of disruption that lower-
   layer network maintenance activities cause, by making BGP speakers
   preemptively converge onto alternative paths while the lower-layer
   network's forwarding plane remains fully operational.
Show full document text