Re: [spring] WG Last Call for draft-ietf-spring-segment-routing-mpls-13

[Ahmed Bashandy <[e-mail]>]

I uploaded version 15 to address the comments below since today is the 
deadline before the upcoming IETF

I will explaining how version 15 addresses each of the comments before 
the start of the IETF next week

Thanks a lot for all the help and the feedback

Ahmed



On 10/15/18 9:12 AM, [e-mail] wrote:
>
> Authors, Ahmed,
>
> Could you progress on this document?
>
> Thread is: 
> https://mailarchive.ietf.org/arch/browse/spring/?q=subject%3Adraft-ietf-spring-segment-routing-mpls
>
> Comments still to be addressed/resolved are the following:
>
> https://mailarchive.ietf.org/arch/msg/spring/xx-t5v5IW2P_8rZykeJrvl9qDIE 
> (from myself since 2018-05-24)
>
> https://mailarchive.ietf.org/arch/msg/spring/CRi96MnH4Bsu-tqlz5u26Man9xw 
> (from Chris Bowers since 2018-06-08)
>
> https://mailarchive.ietf.org/arch/msg/spring/yIwUvKddrcR-gxPQZSMjbynTX74 
> (from PK since 2018-06-09)
>
> https://mailarchive.ietf.org/arch/msg/spring/5PHhLlMIxLgoFdoRC1Wqz6xCBnI 
> (from PK since 2018-06-09)
>
> https://mailarchive.ietf.org/arch/msg/spring/w0ZmOAcDf_TUUWLkeFk_E6jzQm4 
> (from Ruediger 2018-06-13)
>
> https://mailarchive.ietf.org/arch/msg/spring/gKA5sqkuk3SnOMAz4nSSCxFQHtQ 
> (from Shraddha 2018-07-20 & +1 from Sasha)
>
> https://mailarchive.ietf.org/arch/msg/spring/c7Pb8paTt1UibOw_O0yfPW4fgOk 
> (from Sasha & Stéphane discussion 2018-08-06)
>
> Authors, Ahmed,
>
> Thank you for engaging the authors of those comments and update the draft.
>
> Thank you,
>
> --Bruno
>
> *From:*DECRAENE Bruno IMT/OLN
> *Sent:* Thursday, June 07, 2018 6:52 PM
> *To:* SPRING WG List
> *Cc:* [e-mail]
> *Subject:* RE: WG Last Call for draft-ietf-spring-segment-routing-mpls-13
>
> Hi all,
>
> A quick update on the status of this WGLC:
>
> - All the authors have responded about IPR (thank you!). Still missing 
> replies from some contributors (Wim, Edward, Igor, Saku). I’ve sent 
> them a reminder this Monday.
>
> - Two people (Zafar, Adrian) have responded supporting publication.
>
> - No opposition.
>
> - Two persons have sent comments (Adrian, myself). Thanks Adrian.
>
> - Authors have not replied to any comment so far.
>
> - The WGLC period was scheduled to end tomorrow.
>
> I wish we had more support, reviews, and authors’ involvement to reply 
> to reviews.
>
> The WGLC is extended by a week. Please review the document and send 
> your comments to the list, no later than **June 15**
>
> Thank you,
>
> --Bruno
>
> *From:*[e-mail] [mailto:[e-mail]]
> *Sent:* Thursday, May 24, 2018 7:14 PM
> *To:* SPRING WG List
> *Cc:* [e-mail]
> *Subject:* WG Last Call for draft-ietf-spring-segment-routing-mpls-13
>
> Hello Working Group,
> This email starts a Working Group Last Call on 
> draft-ietf-spring-segment-routing-mpls-13 [1] which is considered 
> mature and ready for a final working group review.
> Please read this document if you haven't read the most recent version 
> yet, and send your comments to the list, no later than *June 08*.
> As a reminder, this document had already passed a WGLC more than a 
> year ago on version -06 [2], had been sent to the AD but then returned 
> to the WG.
> Since then, the document has significantly changed, so please read it 
> again. In particular, it now includes the resolution in case of 
> incoming label collision. Hence it killed 
> draft-ietf-spring-conflict-resolution.
> Both co-chairs co-author this document, hence:
> - Shraddha has agreed to be the document shepherd. Thank you Shraddha.
> - Martin, our AD, has agreed to evaluate the WG consensus.
> Thank you,
> Bruno, Rob
> [1] https://tools.ietf.org/html/draft-ietf-spring-segment-routing-mpls-13
> [2] 
> https://mailarchive.ietf.org/arch/msg/spring/STiYsQJWuVXA1C9hK4BiUnyMu7Y
> _________________________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.