ADD-PATH for Route Servers
draft-francois-idr-rs-addpaths-01

Document Type Expired Internet-Draft (individual)
Last updated 2015-02-13 (latest revision 2014-08-12)
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-francois-idr-rs-addpaths-01.txt

Abstract

BGP speakers at Internet Exchange Points typically exchange routes with a large number of peers. To reduce the burden of maintaining many sessions, IXPs implement and administrate BGP route servers. Route servers announce to their clients the paths of multiple peers by using a single eBGP session. Route servers, however, are restricted to propagating a single path per NLRI per eBGP session. This constraint affects the diversity of paths received by clients. To overcome this limitation, we propose the extension of ADD-PATH to eBGP peers. ADD-PATH allows a BGP speaker to send multiple paths for the same NLRI, typically through different nexthops, over a single session with a peer. By supporting ADD-PATH, a route server hence allows a client to potentially select among all the available paths for that NLRI, instead of the one arbitrarily chosen by the Route Server.

Authors

Pierre Francois (pierre.francois@imdea.org)
Camilo Cardona (juancamilo.cardona@imdea.org)
Adam Simpson (adam.simpson@alcatel-lucent.com)
Jeffrey Haas (jhaas@juniper.net)

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