RFC 7911: Advertisement of Multiple Paths in BGP
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7911
- Published
- July 2016
- Authors
- D. Walton; A. Retana; E. Chen; J. Scudder
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7313Enhanced Route Refresh Capability for BGP-4Current
July 2014
- RFC 8654Extended Message Support for BGPCurrent
October 2019
- RFC 7153IANA Registries for BGP Extended CommunitiesUpdated
March 2014
- RFC 6793BGP Support for Four-Octet Autonomous System (AS) Number SpaceCurrent
December 2012
- RFC 5701IPv6 Address Specific BGP Extended Community AttributeUpdated
November 2009
- RFC 56684-Octet AS Specific BGP Extended CommunityCurrent
October 2009
- RFC 5492Capabilities Advertisement with BGP-4Updated
February 2009
- RFC 5292Address-Prefix-Based Outbound Route Filter for BGP-4Current
August 2008
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?