Advertisement of Multiple Paths in BGP (RFC7911)
Original Publication Date: 2016-Jul-01
Included in the Prior Art Database: 2016-Jul-12
Internet Society Requests For Comment (RFCs)
D. Walton: AUTHOR [+4]
The BGP specification [RFC4271] defines an Update-Send Process to advertise the routes chosen by the Decision Process to other BGP speakers. No provisions are made to allow the advertisement of multiple paths for the same address prefix or Network Layer Reachability Information (NLRI). In fact, a route with the same NLRI as a previously advertised route implicitly replaces the previous advertisement.
Internet Engineering Task Force (IETF) D. Walton Request for Comments: 7911 Cumulus Networks Category: Standards Track A. Retana ISSN: 2070-1721 E. Chen Cisco Systems, Inc. J. Scudder Juniper Networks July 2016
Advertisement of Multiple Paths in BGP
This document defines a BGP extension that allows the advertisement of multiple paths for the same address prefix without the new paths implicitly replacing any previous ones. The essence of the extension is that each path is identified by a Path Identifier in addition to the address prefix.
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 7841.
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/rfc7911.
Copyright (c) 2016 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.
al. Standards Track [Page 1]
RFC 7911 ADD-PATH July 2016
Table of Contents
1. Introduction . . . . . . . . . . . . . . ....