Re: Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to 10/21/2019]

I support the adoption of both drafts.


Rgds
Shraddha

From: Idr <[email protected]> On Behalf Of Susan Hares
Sent: Monday, October 14, 2019 11:43 PM
To: 'idr wg' <[email protected]>; 'SPRING WG List' <[email protected]>
Subject: Re: [Idr] Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to 10/21/2019]

Greetings IDR and Spring WG

The WG Adoption for the two IDR drafts related to IDR received a level support below the threshold to accept this draft into the IDR WG.  There were no objection, but there was simply a low level of response.

This 1 week extension to the Adoption call is to let the members of both the IDR and SPRING WG comment on whether these drafts have matured enough to be IDR WG drafts.  On 10/21/2019, the IDR chairs will make a determination of whether either of these two drafts have enough support to be accepted.

Thank you,  Susan  Hares
IDR co-chair

From: Idr [mailto:[email protected]] On Behalf Of Susan Hares
Sent: Tuesday, September 17, 2019 12:35 PM
To: 'idr wg'
Subject: [Idr] Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt [9/17 to 10/1/2019]

This begins a 2 week WG Adoption call two related drafts [9/17 to 10/1/2019]

  *   draft-li-bgp-ls-sr-policy-path-segment-03.txt and
  *   draft-li-idr-sr-policy-path-segment-01.txt.

You can access these two drafts at the following location:

https://datatracker.ietf.org/doc/draft-li-idr-bgp-ls-sr-policy-path-segment/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-li-idr-bgp-ls-sr-policy-path-segment/__;!8WoA6RjC81c!Wz7b25P3MjEHNnuIJlISWoZ6ixJ439lDVO5kS5HFr5fxrtGr07gJ6yZJJvkoqyV8$>

https://datatracker.ietf.org/doc/draft-li-idr-sr-policy-path-segment/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-li-idr-sr-policy-path-segment/__;!8WoA6RjC81c!Wz7b25P3MjEHNnuIJlISWoZ6ixJ439lDVO5kS5HFr5fxrtGr07gJ6yZJJhIezQzQ$>

The authors have pointed out that the adoption of this
draft since the following  SR-MPLS Path Segment draft has been adopted:

https://tools.ietf.org/html/draft-ietf-spring-mpls-path-segment-00<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-ietf-spring-mpls-path-segment-00__;!8WoA6RjC81c!Wz7b25P3MjEHNnuIJlISWoZ6ixJ439lDVO5kS5HFr5fxrtGr07gJ6yZJJrFqQvFw$>

Please consider the following questions in your responses?


  1.  Should this SR Policy technology be included in BGP for SR-MPLS



Spring has adopted the draft, but IDR can provide feedback

to spring about putting this technology in BGP.


  1.  Is this technology a good way to implement the required

Features in BGP?



  1.  Is this technology ready for adoption?



  1.  Do you have any concerns about adopting this technology?



Cheers, Susan Hares

_______________________________________________
Idr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/idr