Re: [nvo3] Poll on progressing draft-ietf-nvo3-encap with missing IPR declaration

xiao.min2@zte.com.cn Fri, 15 July 2022 00:53 UTC

Return-Path: <xiao.min2@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 01D1FC15A72E; Thu, 14 Jul 2022 17:53:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.907
X-Spam-Level:
X-Spam-Status: No, score=-0.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 tLI9bWMoVbXg; Thu, 14 Jul 2022 17:53:29 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13C88C14F741; Thu, 14 Jul 2022 17:53:28 -0700 (PDT)
Received: from mse-fl1.zte.com.cn (unknown [10.5.228.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4LkXsf5tZPz5BNS0; Fri, 15 Jul 2022 08:53:26 +0800 (CST)
Received: from njxapp01.zte.com.cn ([10.41.132.200]) by mse-fl1.zte.com.cn with SMTP id 26F0rJ4Q035747; Fri, 15 Jul 2022 08:53:19 +0800 (GMT-8) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njxapp02[null]) by mapi (Zmail) with MAPI id mid201; Fri, 15 Jul 2022 08:53:19 +0800 (CST)
Date: Fri, 15 Jul 2022 08:53:19 +0800
X-Zmail-TransId: 2afa62d0ba7f503d3b29
X-Mailer: Zmail v1.0
Message-ID: <202207150853198536916@zte.com.cn>
In-Reply-To: <VI1PR0701MB69913D5721DACB7976DA2837EB829@VI1PR0701MB6991.eurprd07.prod.outlook.com>
References: VI1PR0701MB69913D5721DACB7976DA2837EB829@VI1PR0701MB6991.eurprd07.prod.outlook.com
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: matthew.bocci@nokia.com
Cc: nvo3@ietf.org, draft-ietf-nvo3-encap@ietf.org, andrew-ietf@liquid.tech
Content-Type: text/plain; charset="UTF-8"
X-MAIL: mse-fl1.zte.com.cn 26F0rJ4Q035747
X-Fangmail-Gw-Spam-Type: 0
X-FangMail-Miltered: at cgslv5.04-192.168.250.138.novalocal with ID 62D0BA86.000 by FangMail milter!
X-FangMail-Envelope: 1657846406/4LkXsf5tZPz5BNS0/62D0BA86.000/10.5.228.81/[10.5.228.81]/mse-fl1.zte.com.cn/<xiao.min2@zte.com.cn>
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 62D0BA86.000/4LkXsf5tZPz5BNS0
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/uZZRY5toxUpR9lL5HiPKhlufMIA>
Subject: Re: [nvo3] Poll on progressing draft-ietf-nvo3-encap with missing IPR declaration
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, 15 Jul 2022 00:53:33 -0000

Hi Matthew,

I support option (1).

Cheers,
Xiao Min
------------------Original------------------
From: Bocci,Matthew(Nokia-GB) <matthew.bocci@nokia.com>
To: NVO3 <nvo3@ietf.org>;draft-ietf-nvo3-encap@ietf.org <draft-ietf-nvo3-encap@ietf.org>;
Cc: Andrew Alston - IETF <andrew-ietf@liquid.tech>;
Date: 2022年07月08日 20:52
Subject: [nvo3] Poll on progressing draft-ietf-nvo3-encap with missing IPR declaration
_______________________________________________
nvo3 mailing list
nvo3@ietf.org
https://www.ietf.org/mailman/listinfo/nvo3

NVo3 WG,
The chairs believe there is consensus to publish draft-ietf-nvo3-encap as an informational RFC. However, we are missing an IPR declaration from one of the co-authors listed in the Contributors  section.
Despite repeated attempts to contact them over several weeks through multiple channels, we have not received an IPR declaration. It is incumbent upon us to ask every author and contributor  to declare whether they are aware of any IPR that may be applicable to the draft. However, since we have not been unable to contact this one co-author, we would like the working group’s input on how to proceed by responding to this poll.
These are the potential options:
Remove the individual’s name from the list of contributors, moving it to the acknowledgements section, and then request publication of the draft.
Proceed with publication of the draft regardless, with no changes to the contributors list.
Do not publish the draft until we receive a response form the individual (which may be never).
Please respond to this poll by Friday 22nd July stating whether you support option (1), option (2) or option (3).
Best regards,
Matthew and Sam.