BGP Path Marking
draft-bgp-path-marking-00

Document Type Expired Internet-Draft (individual)
Authors Camilo Cardona  , Pierre Francois  , Saikat Ray  , Keyur Patel  , Paolo Lucente  , Prodosh Mohapatra 
Last updated 2014-01-11 (latest revision 2013-07-10)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-bgp-path-marking-00.txt

Abstract

The potential advertisement of non-best paths by a BGP speaker supporting the add-path or the best-external extensions makes it difficult for other BGP speakers to identify the paths that have been selected as best by those who advertise them. This information is required for proper operation of some applications. Towards that end, this document proposes marking the paths using extended communities that encode the path type.

Authors

Camilo Cardona (juancamilo.cardona@imdea.org)
Pierre Francois (pierre.francois@imdea.org)
Saikat Ray (sairay@cisco.com)
Keyur Patel (keyupate@cisco.com)
Paolo Lucente (plucente@cisco.com)
Prodosh Mohapatra (pmohapat@cumulusnetworks.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)