Graceful BGP session shutdown
draft-ietf-grow-bgp-gshut-07

The information below is for an old version of the document
Document Type Active Internet-Draft (grow WG)
Last updated 2017-06-22
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                    Pierre Francois
Internet-Draft                                    Individual Contributor
Intended status: Informational                               B. Decraene
Expires: December 23, 2017                                        Orange
                                                              C. Pelsser
                                                   Strasbourg University
                                                                K. Patel
                                                            Arrcus, Inc.
                                                             C. Filsfils
                                                           Cisco Systems
                                                           June 21, 2017

                     Graceful BGP session shutdown
                      draft-ietf-grow-bgp-gshut-07

Abstract

   This draft describes operational procedures aimed at reducing the
   amount of traffic lost during planned maintenances of routers or
   links, involving the shutdown of BGP peering sessions.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 23, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Pierre Francois, et al. Expires December 23, 2017               [Page 1]
Internet-Draft        Graceful BGP session shutdown            June 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Packet loss upon manual eBGP session shutdown . . . . . . . .   3
   4.  Practices to avoid packet losses  . . . . . . . . . . . . . .   4
     4.1.  Improving availability of alternate paths . . . . . . . .   4
     4.2.  Make before break convergence: g-shut . . . . . . . . . .   4
   5.  Forwarding modes and transient forwarding loops during
       convergence . . . . . . . . . . . . . . . . . . . . . . . . .   7
   6.  Link Up cases . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Unreachability local to the ASBR  . . . . . . . . . . . .   7
     6.2.  iBGP convergence  . . . . . . . . . . . . . . . . . . . .   7
   7.  IANA assigned g-shut BGP community  . . . . . . . . . . . . .   8
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     11.2.  Informative References . . . . . . . . . . . . . . . . .   9
   Appendix A.  Alternative techniques with limited applicability  .  10
     A.1.  Multi Exit Discriminator tweaking . . . . . . . . . . . .  10
     A.2.  IGP distance Poisoning  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Routing changes in BGP can be caused by planned, maintenance
   operations.  This document discusses operational procedures to be
   applied in order to reduce or eliminate losses of packets during the
   maintenance.  These losses come from the transient lack of
   reachability during the BGP convergence following the shutdown of an
   eBGP peering session between two Autonomous System Border Routers
   (ASBR).

   This document presents procedures for the cases where the forwarding
   plane is impacted by the maintenance, hence when the use of Graceful
   Restart does not apply.

   The procedures described in this document can be applied to reduce or
   avoid packet loss for outbound and inbound traffic flows initially
Show full document text