Re: [nvo3] WG Last call and IPR Poll for draft-ietf-nvo3-yang-cfg-04

chen.ran@zte.com.cn Tue, 30 March 2021 02:24 UTC

Return-Path: <chen.ran@zte.com.cn>
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 0DEFD3A29F3; Mon, 29 Mar 2021 19:24:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level:
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 QSdAoRA6DDE1; Mon, 29 Mar 2021 19:24:25 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 C0B253A29EE; Mon, 29 Mar 2021 19:23:45 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.164.217]) by Forcepoint Email with ESMTPS id 7E0774F8DE18717F9C99; Tue, 30 Mar 2021 10:23:42 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id 285CC52DB03EB437D197; Tue, 30 Mar 2021 10:23:42 +0800 (CST)
Received: from njxapp01.zte.com.cn ([10.41.132.200]) by mse-fl2.zte.com.cn with SMTP id 12U2NRcx082037; Tue, 30 Mar 2021 10:23:27 +0800 (GMT-8) (envelope-from chen.ran@zte.com.cn)
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid203; Tue, 30 Mar 2021 10:23:26 +0800 (CST)
Date: Tue, 30 Mar 2021 10:23:26 +0800
X-Zmail-TransId: 2afb60628b9e42ea89e9
X-Mailer: Zmail v1.0
Message-ID: <202103301023269808253@zte.com.cn>
In-Reply-To: <CA+C0YO2HsW_LMHwYtm3GUPZdVcZ998RxRG8UgdYgCSM6BtCfWA@mail.gmail.com>
References: CA+C0YO2HsW_LMHwYtm3GUPZdVcZ998RxRG8UgdYgCSM6BtCfWA@mail.gmail.com
Mime-Version: 1.0
From: chen.ran@zte.com.cn
To: aldrin.ietf@gmail.com
Cc: nvo3@ietf.org, draft-ietf-nvo3-yang-cfg@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 12U2NRcx082037
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/35Zva2cfJU3KA04PeU8_Lmn-FgU>
Subject: Re: [nvo3] WG Last call and IPR Poll for draft-ietf-nvo3-yang-cfg-04
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Mar 2021 02:24:30 -0000

Hi Sam, Matthew and WG


I am not aware of any IPR applicable to this draft that should be disclosed in accordance with IETF IPR rules, and I support the last call adoption of the document as co-author. 






Best Regards,


Ran







原始邮件



发件人:SamAldrin
收件人:NVO3;draft-ietf-nvo3-yang-cfg@ietf.org;
日 期 :2021年03月29日 14:54
主 题 :[nvo3] WG Last call and IPR Poll for draft-ietf-nvo3-yang-cfg-04


_______________________________________________
nvo3 mailing list
nvo3@ietf.org
https://www.ietf.org/mailman/listinfo/nvo3



This email begins a two-week working group last call for draft-ietf-nvo3-yang-cfg-04.


 


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 a standards track 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 in order 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 12th April 2021.


 


Regards


 


Sam and Matthew