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

刘鹏 <liupengyjy@chinamobile.com> Tue, 30 March 2021 06:07 UTC

Return-Path: <liupengyjy@chinamobile.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 826D43A3E54; Mon, 29 Mar 2021 23:07:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.659
X-Spam-Level:
X-Spam-Status: No, score=-0.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HDRS_MISSP=1.939, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Fe-MZ5h-TdsN; Mon, 29 Mar 2021 23:07:16 -0700 (PDT)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with ESMTP id 6D2783A3E53; Mon, 29 Mar 2021 23:07:15 -0700 (PDT)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.19]) by rmmx-syy-dmz-app01-12001 (RichMail) with SMTP id 2ee16062c0035f3-be3d7; Tue, 30 Mar 2021 14:07:00 +0800 (CST)
X-RM-TRANSID: 2ee16062c0035f3-be3d7
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from PENG (unknown[10.2.53.59]) by rmsmtp-syy-appsvr10-12010 (RichMail) with SMTP id 2eea6062c0009cd-71147; Tue, 30 Mar 2021 14:07:00 +0800 (CST)
X-RM-TRANSID: 2eea6062c0009cd-71147
MIME-Version: 1.0
x-PcFlag: b8b5891c-d7db-49c2-9e83-f851887be823_5_48823
X-Mailer: PC_RICHMAIL 2.8.5
Date: Tue, 30 Mar 2021 14:07:00 +0800
From: 刘鹏 <liupengyjy@chinamobile.com>
To: "aldrin.ietf" <aldrin.ietf@gmail.com>
Cc: nvo3 <nvo3@ietf.org>, draft-ietf-nvo3-yang-cfg@ietf.org
Message-ID: <20210330140700707697456@chinamobile.com>
Content-Type: multipart/Alternative; boundary="----=_001_NextPart707697456_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/TJ3O23Nr-9JT040mGvLe39cgues>
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 06:07:21 -0000


Hi all,




I support the publication.




Regards,

Peng








Peng Liu | 刘鹏

China Mobile | 移动研究院

mobile phone:13810146105

email:  liupengyjy@chinamobile.com







原始邮件







发件人: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