答复: [spring] Request to close the LC and move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming

"Chenxia (D)" <jescia.chenxia@huawei.com> Wed, 26 February 2020 12:39 UTC

Return-Path: <jescia.chenxia@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABACB3A0977; Wed, 26 Feb 2020 04:39:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-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 vceBmgWUHb4b; Wed, 26 Feb 2020 04:39:56 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9FBC3A0978; Wed, 26 Feb 2020 04:39:55 -0800 (PST)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 621D3E424B5D48642292; Wed, 26 Feb 2020 12:39:54 +0000 (GMT)
Received: from lhreml702-chm.china.huawei.com (10.201.108.51) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 26 Feb 2020 12:39:53 +0000
Received: from lhreml702-chm.china.huawei.com (10.201.108.51) by lhreml702-chm.china.huawei.com (10.201.108.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Wed, 26 Feb 2020 12:39:53 +0000
Received: from DGGEMM405-HUB.china.huawei.com (10.3.20.213) by lhreml702-chm.china.huawei.com (10.201.108.51) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Wed, 26 Feb 2020 12:39:53 +0000
Received: from DGGEMM529-MBX.china.huawei.com ([169.254.13.117]) by DGGEMM405-HUB.china.huawei.com ([10.3.20.213]) with mapi id 14.03.0439.000; Wed, 26 Feb 2020 20:39:41 +0800
From: "Chenxia (D)" <jescia.chenxia@huawei.com>
To: "Chengli (Cheng Li)" <chengli13@huawei.com>, 'SPRING WG List' <spring@ietf.org>
CC: "6man@ietf.org" <6man@ietf.org>, draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>
Subject: =?utf-8?b?562U5aSNOg==?= [spring] Request to close the LC and move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming
Thread-Topic: [spring] Request to close the LC and move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming
Thread-Index: AQHV7KDFAeDTM9mJU0uRoKMc2iK/NagtaiLm
Date: Wed, 26 Feb 2020 12:39:41 +0000
Message-ID: <346809D6D8BB1849AF0886D035619F9C2B07128A@DGGEMM529-MBX.china.huawei.com>
References: <5A5B4DE12C0DAC44AF501CD9A2B01A8D9364A1C2@DGGEMM532-MBX.china.huawei.com> <7f4c1d0a6f674e7eb3d51163e7b7954f@huawei.com>, <C7C2E1C43D652C4E9E49FE7517C236CB0292D0E1@dggeml529-mbx.china.huawei.com>
In-Reply-To: <C7C2E1C43D652C4E9E49FE7517C236CB0292D0E1@dggeml529-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.181.174]
Content-Type: multipart/alternative; boundary="_000_346809D6D8BB1849AF0886D035619F9C2B07128ADGGEMM529MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/tTwxZOCxx4E2zEwiZJ0ZaQ0zLVc>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2020 12:39:58 -0000

+1

Xia
________________________________
发件人: Chengli (Cheng Li) [chengli13@huawei.com]
发送时间: 2020年2月26日 20:22
收件人: 'SPRING WG List'
抄送: 6man@ietf.org; draft-ietf-spring-srv6-network-programming
主题: Re: [spring] Request to close the LC and move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming

+1

Cheng

From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Gengxuesong (Geng Xuesong)
Sent: Wednesday, February 26, 2020 8:19 PM
To: Lizhenbin <lizhenbin@huawei.com>om>; bruno.decraene@orange.com; 'SPRING WG List' <spring@ietf.org>
Cc: 6man@ietf.org; draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>
Subject: RE: Request to close the LC and move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming

+1


Best Regards
Xuesong
From: spring [mailto:spring-bounces@ietf.org] On Behalf Of Lizhenbin
Sent: Wednesday, February 26, 2020 7:55 PM
To: bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>; 'SPRING WG List' <spring@ietf.org<mailto:spring@ietf.org>>
Cc: 6man@ietf.org<mailto:6man@ietf.org>; draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org<mailto:draft-ietf-spring-srv6-network-programming@ietf.org>>
Subject: [spring] Request to close the LC and move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming

Hi Bruno and WG,
The LC has lasted for almost 3 months which greatly exceeds the expected 2 week. In the process all the comments have been resolved while some issues is raised again and again with little value.
On the other hand, there have been multiple commercial implementation and inter-op test and almost 20 deployments for SRv6 which justify the solution proposed by the draft in practice.

We sincerely request to close the LC of the draft and move forward.



Best Regards,
Zhenbin (Robin)


From: bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> [mailto:bruno.decraene@orange.com]
Sent: Friday, December 06, 2019 1:15 AM
To: 'SPRING WG List' <spring@ietf.org<mailto:spring@ietf.org>>
Cc: 6man@ietf.org<mailto:6man@ietf.org>; draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org<mailto:draft-ietf-spring-srv6-network-programming@ietf.org>>
Subject: WGLC - draft-ietf-spring-srv6-network-programming


Hello SPRING,



This email starts a two weeks Working Group Last Call on draft-ietf-spring-srv6-network-programming [1].



Please read this document if you haven't read the most recent version, and send your comments to the SPRING WG list, no later than December 20.



You may copy the 6MAN WG for IPv6 related comment, but consider not duplicating emails on the 6MAN mailing list for the comments which are only spring specifics.



If you are raising a point which you expect will be specifically debated on the mailing list, consider using a specific email/thread for this point.

This may help avoiding that the thread become specific to this point and that other points get forgotten (or that the thread get converted into parallel independent discussions)



Thank you,

Bruno



[1] https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-05




_________________________________________________________________________________________________________________________



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.