Browse Prior Art Database

Enhanced Route Refresh Capability for BGP-4 (RFC7313)

IP.com Disclosure Number: IPCOM000237963D
Publication Date: 2014-Jul-23
Document File: 16 page(s) / 15K

Publishing Venue

The IP.com Prior Art Database

Related People

K. Patel: AUTHOR [+3]

Abstract

It is sometimes necessary to perform routing consistency validations such as checking for possible missing route withdrawals between BGP speakers [RFC4271]. Currently, such validations typically involve offline, manual operations that can be tedious and time-consuming.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 18% of the total text.

Internet Engineering Task Force (IETF)                          K. Patel Request for Comments: 7313                                       E. Chen Updates: 2918                                              Cisco Systems Category: Standards Track                           B. Venkatachalapathy ISSN: 2070-1721                                                July 2014

               Enhanced Route Refresh Capability for BGP-4

Abstract

   In this document, we enhance the existing BGP route refresh    mechanisms to provide for the demarcation of the beginning and the    ending of a route refresh.  The enhancement can be used to facilitate    correction of BGP Routing Information Base (RIB) inconsistencies in a    non-disruptive manner.  This document updates RFC 2918.

Status of This Memo

   This is an Internet Standards Track document.

   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    Internet Standards is available in Section 2 of RFC 5741.

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

Copyright Notice

   Copyright (c) 2014 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    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.

 Patel, et al.                Standards Track                    [Page 1]
 RFC 7313       Enhanced Route Refresh Capability for BGP-4     July 2014

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2    2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2    3.  Protocol Extensions . . . . . . . . . . . . . . . . . . . . .   2      3.1.  Enhanced Route Refresh Capability . . . . . . . . . . . .   3      3.2.  Subtypes for ROUTE-REFRESH Message  . . . . . . . . . . .   3    4.  Operation . . . . . . . . . . . . . . . . . . . . . . . ....