Re: [Idr] I-D Action: draft-ietf-idr-add-paths-10.txt

["Susan Hares" <[e-mail]>]

Betrand:

 

IMHO+E (in my humble opinion and experience) quick passage of an IDR draft through IESG requires that the IDR chair collects the implementation information.  Implementation drafts are just one way to present the summarized data, and do not become RFCs. 

 

Would a short online-survey (5 minutes) be quicker for you? 

 

Sue 

 

From: Idr [mailto:[e-mail]] On Behalf Of Bertrand Duvivier (bduvivie)
Sent: Friday, October 24, 2014 12:15 PM
To: Robert Raszuk
Cc: [e-mail]
Subject: Re: [Idr] I-D Action: draft-ietf-idr-add-paths-10.txt

 

Robert,

 

Add-Path has been deployed by many SP’s  with mix vendor environment since years and does works fine... 

 

Thus we may need to ask, what is the added value of such document (outside of following processes). 

 

For Cisco, my BGP team is ready to provide full support if someone start this exercise/ implementation draft but  I’m not ready to take the lead and fund this works, this is not our priority.

 

BTW:  my personal opinion (Not Cisco): I’m in favor to ask SP’s who deployed Add-Path to speak up and provide feedback and bypass the implementation draft if we believe we got enough return from experience.

 

Best Regards Bertrand Duvivier

IP routing Product Manager

 

 

From: [e-mail] [mailto:[e-mail]] On Behalf Of Robert Raszuk
Sent: vendredi 24 octobre 2014 18:00
To: Bertrand Duvivier (bduvivie)
Cc: Acee Lindem (acee); Jeffrey Haas; [e-mail]
Subject: Re: [Idr] I-D Action: draft-ietf-idr-add-paths-10.txt

 

 

Shouldn't we have an implementation report draft documenting those details before WG last call on the main draft ? 

 

r.

 

On Fri, Oct 24, 2014 at 5:56 PM, Bertrand Duvivier (bduvivie) <[e-mail]> wrote:

Acee, Jeff,

To be more precise for Cisco we already support it in our 3 OS's
- IOS XE and IOS classic (CPE and Access routing platform OS)
- IOS XR (hig-end routing platform OS)
- NXOS (switching platform OS)
And interoperability have been tested between Cisco OS's, with Juniper JUNOS, and few others

Best Regards Bertrand Duvivier
IP routing Product Manager



-----Original Message-----

From: Idr [mailto:[e-mail]] On Behalf Of Bertrand Duvivier (bduvivie)
Sent: vendredi 24 octobre 2014 17:49
To: Acee Lindem (acee); Jeffrey Haas; [e-mail]
Subject: Re: [Idr] I-D Action: draft-ietf-idr-add-paths-10.txt

Agree, has been implemented in many OS's already

Best Regards Bertrand Duvivier
IP routing Product Manager



-----Original Message-----
From: Idr [mailto:[e-mail]] On Behalf Of Acee Lindem (acee)
Sent: vendredi 24 octobre 2014 17:02
To: Jeffrey Haas; [e-mail]
Subject: Re: [Idr] I-D Action: draft-ietf-idr-add-paths-10.txt

I just reread it for the first time in a couple years and would agree that it is ready for WG last call.
Thanks,
Acee

On 10/24/14, 10:18 AM, "Jeffrey Haas" <[e-mail]> wrote:

>The update below addressed the major open issue that remained for the
>feature, as deployed, to match the spec: The behavior for ebgp has been
>moved out of operation and into deployment considerations.
>
>I'm not an author, but I believe this draft is finally read for a
>hopefully short Working Group Last Call.
>
>-- Jeff
>
>On Fri, Oct 24, 2014 at 06:57:42AM -0700, [e-mail] wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts
>>directories.
>>  This draft is a work item of the Inter-Domain Routing Working Group
>>of the IETF.
>>
>>         Title           : Advertisement of Multiple Paths in BGP
>>         Authors         : Daniel Walton
>>                           Alvaro Retana
>>                           Enke Chen
>>                           John Scudder
>>      Filename        : draft-ietf-idr-add-paths-10.txt
>>      Pages           : 8
>>      Date            : 2014-10-24
>>
>> Abstract:
>>    In this document we propose 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.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-idr-add-paths/
>
>_______________________________________________
>Idr mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/idr

_______________________________________________
Idr mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/idr

_______________________________________________
Idr mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/idr

_______________________________________________
Idr mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/idr