Skip to main content

Distribution of Diverse BGP Paths
RFC 6774

Revision differences

Document history

Date By Action
2023-06-03
(System) Received changes through RFC Editor sync (removed Errata tag)
2023-05-30
(System) Received changes through RFC Editor sync (added Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'The BGP4 protocol specifies the selection and propagation of a single best path for each prefix. …
Received changes through RFC Editor sync (changed abstract to 'The BGP4 protocol specifies the selection and propagation of a single best path for each prefix. As defined and widely deployed today, BGP has no mechanisms to distribute alternate paths that are not considered best path between its speakers. This behavior results in a number of disadvantages for new applications and services.

The main objective of this document is to observe that by simply adding a new session between a route reflector and its client, the Nth best path can be distributed. This document also compares existing solutions and proposed ideas that enable distribution of more paths than just the best path.

This proposal does not specify any changes to the BGP protocol definition. It does not require a software upgrade of provider edge (PE) routers acting as route reflector clients. This document is not an Internet Standards Track specification; it is published for informational purposes.')
2016-11-30
(System) Closed request for Last Call review by GENART with state 'Unknown'
2015-10-14
(System) Notify list changed from grow-chairs@ietf.org, draft-ietf-grow-diverse-bgp-path-dist@ietf.org to (None)
2012-11-07
(System) RFC published