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

<bruno.decraene@orange.com> Mon, 15 October 2018 16:12 UTC

Return-Path: <bruno.decraene@orange.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D9AE130E9D; Mon, 15 Oct 2018 09:12:09 -0700 (PDT)
X-Quarantine-ID: <4tiEgcDqroCe>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): References: ...@OPEXCLILM21.corporate.adroot.infra.ftgroup>\n
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4tiEgcDqroCe; Mon, 15 Oct 2018 09:12:05 -0700 (PDT)
Received: from orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21B71130EC0; Mon, 15 Oct 2018 09:12:03 -0700 (PDT)
Received: from opfedar03.francetelecom.fr (unknown [xx.xx.xx.5]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id 42Yk3P55yfz2y3d; Mon, 15 Oct 2018 18:12:01 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.43]) by opfedar03.francetelecom.fr (ESMTP service) with ESMTP id 42Yk3P453wzCqkS; Mon, 15 Oct 2018 18:12:01 +0200 (CEST)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM5F.corporate.adroot.infra.ftgroup ([fe80::e172:f13e:8be6:71cc%18]) with mapi id 14.03.0415.000; Mon, 15 Oct 2018 18:12:01 +0200
From: bruno.decraene@orange.com
To: "draft-ietf-spring-segment-routing-mpls@ietf.org" <draft-ietf-spring-segment-routing-mpls@ietf.org>, "abashandy.ietf@gmail.com" <abashandy.ietf@gmail.com>
CC: SPRING WG List <spring@ietf.org>
Thread-Topic: WG Last Call for draft-ietf-spring-segment-routing-mpls-13
Thread-Index: AdPzgj45KwPIKnTMSDy4d61puK5luwK+2i5gGYgd9HA=
Date: Mon, 15 Oct 2018 16:12:01 +0000
Message-ID: <6143_1539619921_5BC4BC51_6143_164_1_53C29892C857584299CBF5D05346208A47B69553@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <28960_1527182067_5B06F2F3_28960_194_1_53C29892C857584299CBF5D05346208A47A53592@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.2]
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A47B69553OPEXCLILM21corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/qgdxW_PzpT3JyZKzq9slGopBpbI>
Subject: Re: [spring] WG Last Call for draft-ietf-spring-segment-routing-mpls-13
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2018 16:12:09 -0000

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: draft-ietf-spring-segment-routing-mpls@ietf.org
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: bruno.decraene@orange.com [mailto:bruno.decraene@orange.com]
Sent: Thursday, May 24, 2018 7:14 PM
To: SPRING WG List
Cc: draft-ietf-spring-segment-routing-mpls@ietf.org
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.