Requirements for the Graceful Shutdown of BGP Sessions

Thu, 04/21/2011 - 23:47 by Olivier Bonaventure

Abstract

The Border Gateway Protocol (BGP) is heavily used in Service Provider
networks for both Internet and BGP/MPLS VPN services. For resiliency
purposes, redundant routers and BGP sessions can be deployed to reduce
the consequences of an Autonomous System Border Router (ASBR) or BGP
session breakdown on customers' or peers' traffic. However, simply
taking down or even bringing up a BGP session for maintenance purposes
may still induce connectivity losses during the BGP convergence. This
is no longer satisfactory for new applications (e.g., voice over IP,
online gaming, VPN). Therefore, a solution is required for the
graceful shutdown of a (set of) BGP session(s) in order to limit the
amount of traffic loss during a planned shutdown. This document
expresses requirements for such a solution. This document is not
an Internet Standards Track specification; it is
published for informational purposes.

Authors
B. Decraene, Pierre Francois, Cristel Pelsser, Z. Ahmad, A.J. Elizondo Armengol and T. Takeda
Source
Internet Engineering Task Force (IETF) Request for Comments (RFC),(6198), April 2011.
Full text
pdf    (28.78 KB)
Cite it
BibTex
Copyright
See here

IEEE Copyright Notice: This material is presented to ensure timely dissemination of scholarly and technical work. Copyright and all rights therein are retained by authors or by other copyright holders. All persons copying this information are expected to adhere to the terms and constraints invoked by each author's copyright. In most cases, these works may not be reposted without the explicit permission of the copyright holder.

ACM Copyright Notice: Copyright 1999 by the Association for Computing Machinery, Inc. Permission to make digital or hard copies of part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page or intial screen of the document. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, to republish, to post on servers, or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from Publications Dept., ACM Inc., fax +1 (212) 869-0481, or permissions@acm.org.

Springer-Verlag LNCS Copyright Notice: The copyright of these contributions has been transferred to Springer-Verlag Berlin Heidelberg New York. The copyright transfer covers the exclusive right to reproduce and distribute the contribution, including reprints, translations, photographic reproductions, microform, electronic form (offline, online), or any other reproductions of similar nature. Online available from Springer-Verlag LNCS series.