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

"Zafar Ali (zali)" <zali@cisco.com> Fri, 25 May 2018 15:23 UTC

Return-Path: <zali@cisco.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 92D3212EB1A; Fri, 25 May 2018 08:23:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 GO8C6TipnK2x; Fri, 25 May 2018 08:23:49 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A04012EB2B; Fri, 25 May 2018 08:23:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16256; q=dns/txt; s=iport; t=1527261829; x=1528471429; h=from:to:cc:subject:date:message-id:mime-version; bh=kuYD6ldtHzO974q0qJ3uiWv2W8/xQ6mXSBqjGMnoOpg=; b=JLSyJ14i5XYvJaePMe6Fk9sfsRmFZ4lxg4dVJJNXdP2EedvEq3dYg9kh xK80mwjOGIO3riy9ISxuOdIabnGmH/rj8ZDtfJ63qgR6jfqzCnJmhJznb WGGTZsTqk2J4LTTaO78b9gwKPQKRi/NZfPxoPa7qHpqD5zh8cFvmakCWU w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DOAADsKQhb/4cNJK1cGQEBAQEBAQEBAQEBAQcBAQEBAYJOdmJ9KAqDbYgEjGyBeYEPjkOEdhSBZAslhEcCF4F4ITQYAQIBAQEBAQECbBwMhSgBAwMdBlYSAQgRAwECKwIEMB0KBAENBYMiAoEbZA8DqCyCHIhAgXcFiDaBVD+BDySCaYMRAQEDgSUFARIBP4JgMIIkAocrgQSIcYc/CQKFaohxCoExg2+CX4R9iWiGdAIREwGBJB04YXFwFTsqAYIYCYsHhT5vjDuBH4EZAQE
X-IronPort-AV: E=Sophos;i="5.49,440,1520899200"; d="scan'208,217";a="119460140"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 May 2018 15:23:48 +0000
Received: from XCH-RTP-017.cisco.com (xch-rtp-017.cisco.com [64.101.220.157]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w4PFNlbF006815 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 25 May 2018 15:23:48 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-017.cisco.com (64.101.220.157) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 25 May 2018 11:23:46 -0400
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1320.000; Fri, 25 May 2018 11:23:46 -0400
From: "Zafar Ali (zali)" <zali@cisco.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, SPRING WG List <spring@ietf.org>
CC: "draft-ietf-spring-segment-routing-mpls@ietf.org" <draft-ietf-spring-segment-routing-mpls@ietf.org>
Thread-Topic: [spring] WG Last Call for draft-ietf-spring-segment-routing-mpls-13
Thread-Index: AQHT9DxfKwPIKnTMSDy4d61puK5luw==
Date: Fri, 25 May 2018 15:23:46 +0000
Message-ID: <E6DDD89E-D6D6-425E-A9FB-BE1C99E3B5D1@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.9.0.180116
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.180.203]
Content-Type: multipart/alternative; boundary="_000_E6DDD89ED6D6425EA9FBBE1C99E3B5D1ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/qUKf88_evcaandfVNanPtRJgtHM>
Subject: Re: [spring] WG Last Call for draft-ietf-spring-segment-routing-mpls-13
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 25 May 2018 15:23:59 -0000

Dear Martin, Chairs and the WG,

I have read the document and believe it is ready for the publication.

Thanks

Regards … Zafar

From: spring <spring-bounces@ietf.org> on behalf of "bruno.decraene@orange.com" <bruno.decraene@orange.com>
Date: Thursday, May 24, 2018 at 1:18 PM
To: SPRING WG List <spring@ietf.org>
Cc: "draft-ietf-spring-segment-routing-mpls@ietf.org" <draft-ietf-spring-segment-routing-mpls@ietf.org>
Subject: [spring] 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.