Subject: Re: [Idr] New Version Notification for draft-francois-idr-rs-addpaths-01.txt

From: Camilo Cardona <[email-masked]>
Date: Tue, 12 Aug 2014 12:18:15 +0200

Hello everyone,

We just submitted a new version of draft-francois-idr-rs-addpaths. We modified the first document based on variuos comments, notably from Andy Davidson and Thomas Mangin. 

We welcome further feedback or suggestions of changes that can improve the document.

Thanks,

Camilo Cardona

On 12 Aug 2014, at 12:06, [email-masked] wrote:

> 
> A new version of I-D, draft-francois-idr-rs-addpaths-01.txt
> has been successfully submitted by Camilo Cardona and posted to the
> IETF repository.
> 
> Name:		draft-francois-idr-rs-addpaths
> Revision:	01
> Title:		ADD-PATH for Route Servers
> Document date:	2014-08-12
> Group:		Individual Submission
> Pages:		6
> URL:            http://www.ietf.org/internet-drafts/draft-francois-idr-rs-addpaths-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-francois-idr-rs-addpaths/
> Htmlized:       http://tools.ietf.org/html/draft-francois-idr-rs-addpaths-01
> Diff:           http://www.ietf.org/rfcdiff?url2=draft-francois-idr-rs-addpaths-01
> 
> 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.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>