Re: [nvo3] WG Last Call for draft-ietf-nvo3-encap-08

Zhuangshunwan <zhuangshunwan@huawei.com> Fri, 10 June 2022 13:09 UTC

Return-Path: <zhuangshunwan@huawei.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A771EC1A7F0B; Fri, 10 Jun 2022 06:09:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HTgrqIxnO7Bx; Fri, 10 Jun 2022 06:09:30 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3DBEC15AE21; Fri, 10 Jun 2022 06:09:30 -0700 (PDT)
Received: from fraeml734-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4LKLmv4H6Yz6823d; Fri, 10 Jun 2022 21:05:51 +0800 (CST)
Received: from kwepemi500002.china.huawei.com (7.221.188.171) by fraeml734-chm.china.huawei.com (10.206.15.215) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Fri, 10 Jun 2022 15:09:26 +0200
Received: from kwepemi500002.china.huawei.com (7.221.188.171) by kwepemi500002.china.huawei.com (7.221.188.171) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Fri, 10 Jun 2022 21:09:24 +0800
Received: from kwepemi500002.china.huawei.com ([7.221.188.171]) by kwepemi500002.china.huawei.com ([7.221.188.171]) with mapi id 15.01.2375.024; Fri, 10 Jun 2022 21:09:24 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>, NVO3 <nvo3@ietf.org>
CC: "nvo3-chairs@ietf.org" <nvo3-chairs@ietf.org>, "ilango.s.ganga@intel.com" <ilango.s.ganga@intel.com>, "prankajg@microsoft.com" <prankajg@microsoft.com>, Rajeev Manur <rajeev.manur@broadcom.com>, "talmi@marvell.com" <talmi@marvell.com>, "mosesster@gmail.com" <mosesster@gmail.com>, "nordmark@sonic.net" <nordmark@sonic.net>, "Michael Smith (michsmit)" <michsmit@cisco.com>, Sam Aldrin <aldrin.ietf@gmail.com>, Ignas Bagdonas <ibagdona.ietf@gmail.com>, "draft-ietf-nvo3-encap@ietf.org" <draft-ietf-nvo3-encap@ietf.org>
Thread-Topic: WG Last Call for draft-ietf-nvo3-encap-08
Thread-Index: AQHYbopvxZ0lTsEaYE+BKCmPaMLpiK1IuTcw
Date: Fri, 10 Jun 2022 13:09:24 +0000
Message-ID: <f2086c5d6b284441a74fefbb83139d38@huawei.com>
References: <VI1PR0701MB6991AF12239635F6D72F87D4EBD49@VI1PR0701MB6991.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR0701MB6991AF12239635F6D72F87D4EBD49@VI1PR0701MB6991.eurprd07.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.202.95]
Content-Type: multipart/alternative; boundary="_000_f2086c5d6b284441a74fefbb83139d38huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/wsJCn3iR3ZhJMUpt-4X0UAiuT5A>
Subject: Re: [nvo3] WG Last Call for draft-ietf-nvo3-encap-08
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2022 13:09:34 -0000

I support the publication of this document.

Best Regards,
Shunwan


From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB)
Sent: Monday, May 23, 2022 5:58 PM
To: NVO3 <nvo3@ietf.org>
Cc: nvo3-chairs@ietf.org; ilango.s.ganga@intel.com; prankajg@microsoft.com; Rajeev Manur <rajeev.manur@broadcom.com>; talmi@marvell.com; mosesster@gmail.com; nordmark@sonic.net; Michael Smith (michsmit) <michsmit@cisco.com>; Sam Aldrin <aldrin.ietf@gmail.com>; Ignas Bagdonas <ibagdona.ietf@gmail.com>; draft-ietf-nvo3-encap@ietf.org
Subject: [nvo3] WG Last Call for draft-ietf-nvo3-encap-08

This email begins a two-week working group last call for draft-ietf-nvo3-encap-08 (draft-ietf-nvo3-encap-08 - Network Virtualization Overlays (NVO3) Encapsulation Considerations<https://datatracker.ietf.org/doc/draft-ietf-nvo3-encap/>).

We are running a new WG last call as there were a few updates made during the RTG DIR review discussions. We are also missing a few IPR declarations from contributors, which need to be made against the WG LC version of the document. I have copied the contributors directly.

Please review the draft and post any comments to the NVO3 working group list. If you have read the latest version of the draft but have no comments and believe it is ready for publication as an informational RFC, please also indicate so to the WG email list.

We are also polling for knowledge of any undisclosed IPR that applies to this document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).
If you are listed as an Author or a Contributor of this document, please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors.

Currently there are no IPR disclosures against this document.

If you are not listed as an Author or a Contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules.

As a reminder, we are pursuing publication of this document to permanently document the experience of one working group in choosing between multiple proposed standards track encapsulation drafts. The idea was that this would provide helpful guidance to others in the community going forward.

This poll will run until Monday 6th June 2022.

Regards

Matthew and Sam