From 0100018c2096c533-0ffb5b02-9325-498a-87a0-ee1d30e8abcf-000000@amazonses.watsen.net Thu Nov 30 06:16:47 2023 Return-Path: <0100018c2096c533-0ffb5b02-9325-498a-87a0-ee1d30e8abcf-000000@amazonses.watsen.net> X-Original-To: netconf@ietfa.amsl.com Delivered-To: netconf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8121C151984 for ; Thu, 30 Nov 2023 06:16:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.904 X-Spam-Level: X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com 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 JXnw6rTcPMQg for ; Thu, 30 Nov 2023 06:16:44 -0800 (PST) Received: from a48-94.smtp-out.amazonses.com (a48-94.smtp-out.amazonses.com [54.240.48.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53B0BC1516F8 for ; Thu, 30 Nov 2023 06:16:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1701353801; h=From:Content-Type:Mime-Version:Subject:Date:References:To:In-Reply-To:Message-Id:Feedback-ID; bh=E860+CELDtIKu9fCmChMnBNjYSAHK4YnROcmVrNXziw=; b=L33ygvYzgYWVM9rgMXQFZiUk0EVUWEyx0t1V6sP4Xmwwam/s4BdY/eN4Js4OzLTL 2x11Dwsqdmoxk/NIjanQZSA/34k+sbzpGd68GcazTH/j1L+Ynceiiy8eaF1UqKMRUAO Eele8CpSbm+OCrX2CzF3vIldtt/9UAV4hHipAzXs= From: Kent Watsen Content-Type: multipart/alternative; boundary="Apple-Mail=_7F574FDC-6011-42E7-ADAE-2419F976A0FE" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\)) Date: Thu, 30 Nov 2023 14:16:41 +0000 References: <0100018b33d7238d-d0ccba02-7474-4aa3-86de-08f0007db5f0-000000@email.amazonses.com> To: "netconf@ietf.org" In-Reply-To: <0100018b33d7238d-d0ccba02-7474-4aa3-86de-08f0007db5f0-000000@email.amazonses.com> Message-ID: <0100018c2096c533-0ffb5b02-9325-498a-87a0-ee1d30e8abcf-000000@email.amazonses.com> X-Mailer: Apple Mail (2.3731.600.7) Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES X-SES-Outgoing: 2023.11.30-54.240.48.94 Archived-At: Subject: Re: [netconf] IPR call for draft-quilbeuf-netconf-configuration-tracing-00 X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: NETCONF WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2023 14:16:48 -0000 --Apple-Mail=_7F574FDC-6011-42E7-ADAE-2419F976A0FE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 All listed authors and contributors have responded not being aware of = any IPR other than that filed for the draft here: = https://datatracker.ietf.org/ipr/5995. Please be aware the Licensing text of the IPR states: =3D=3D=3D=3D START =3D=3D=3D=3D Conditional Non-Assertion Statement: Subject to the Defensive Assertion = Condition stated below, if any patent claim contained in the patent(s) = or patent application(s) disclosed would necessarily be infringed by = implementing [sections 4 and 5] of the specification contained in the = IETF document or other contribution referenced above that is = incorporated into an Internet Standard or an Proposed Standard adopted = by IETF, Huawei on behalf of itself and its Affiliates hereby covenant = not to assert any such claim against any party where an infringement = assertion is based upon a product or portion of a product which = implements the [sections 4 and 5] of the specification; however, Huawei = retains the right to assert any patents or claims, including the above = disclosed patents and claims, against any party where an infringement = assertion is based upon a product or portion of a product that is not = necessarily infringed by implementing [sections 4 and 5] of the = specification incorporated into the Internet standard or the Proposed = Standard. Nothing in this disclosure should be interpreted to limit in = any way Huawei=E2=80=99s right to assert any claim of any patent that is = not expressly identified above in this disclosure. =20 Defensive Assertion Condition: Notwithstanding the Conditional = Non-Assertion Statement, Huawei shall retain the right to assert the = above disclosed patent(s) or patent application(s) (including claiming = past royalties) against any party that asserts directly or indirectly a = patent it owns or controls against Huawei and/or its Affiliates, or = against any products of Huawei or its Affiliates either alone or in = combination with other products, regardless of whether such patent = assertion is related to IETF standards or not. =20 FRAND License Available for Additional Use: In the event that any party = seeks the right to use the patent(s) disclosed above in ways that exceed = the scope of the above stated commitment by Huawei, Huawei is willing to = offer FRAND royalty-bearing licenses for such activities. =3D=3D=3D=3D STOP =3D=3D=3D=3D Kent // co-chair > On Oct 15, 2023, at 10:56 AM, Kent Watsen = wrote: >=20 > Authors, Contributors, WG, >=20 > As a prerequisite for the adoption on this document: >=20 > External Trace ID for Configuration Tracing > = https://datatracker.ietf.org/doc/draft-quilbeuf-netconf-configuration-trac= ing-00 >=20 > Are you aware of any IPR that applies to draft identified above? >=20 > Please state either: >=20 > "No, I'm not aware of any IPR that applies to this draft=E2=80=9D > or > "Yes, I'm aware of IPR that applies to this draft" >=20 > If so, has this IPR been disclosed in compliance with IETF IPR rules > (see RFCs 3669, 5378 and 8179 for more details)? >=20 > If yes to the above, please state either: >=20 > "Yes, the IPR has been disclosed in compliance with IETF IPR = rules=E2=80=9D > or > "No, the IPR has not been disclosed" >=20 > If you answer no, please provide any additional details you think > appropriate. >=20 > If you are listed as a document author or contributor please answer = the > above by responding to this email regardless of whether or not you are > aware of any relevant IPR. This document will not advance to the next > stage until a response has been received from each author. >=20 > Also please send the response to the list above, and not unicast it. >=20 > FWIW, currently, no IPR is filed for this draft: = https://datatracker.ietf.org/ipr/search/?submit=3Ddraft&id=3Ddraft-quilbeu= f-netconf-configuration-tracing. That said, it is noted that the = previous version of this draft (in OPSAWG) had IPR filed for it here: = https://datatracker.ietf.org/ipr/5995. I have requested the IETF = Secretariat to move that IPR disclosure to this draft (in NETCONF). >=20 > Thanks. > Kent (as co-chair) >=20 > _______________________________________________ > netconf mailing list > netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf --Apple-Mail=_7F574FDC-6011-42E7-ADAE-2419F976A0FE Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
All = listed authors and contributors have responded not being aware of any = IPR other than that filed for the draft here: https://datatracker.ietf.or= g/ipr/5995.

Please be aware the Licensing = text of the IPR states:

=3D=3D=3D=3D START = =3D=3D=3D=3D
Conditional Non-Assertion Statement: Subject to the = Defensive Assertion Condition stated below, if any patent claim = contained in the patent(s) or patent application(s) disclosed would = necessarily be infringed by implementing [sections 4 and 5] of the = specification contained in the IETF document or other contribution = referenced above that is incorporated into an Internet Standard or an = Proposed Standard adopted by IETF, Huawei on behalf of itself and its = Affiliates hereby covenant not to assert any such claim against any = party where an infringement assertion is based upon a product or portion = of a product which implements the [sections 4 and 5] of the = specification; however, Huawei retains the right to assert any patents = or claims, including the above disclosed patents and claims, against any = party where an infringement assertion is based upon a product or portion = of a product that is not necessarily infringed by implementing [sections = 4 and 5] of the specification incorporated into the Internet standard or = the Proposed Standard. Nothing in this disclosure should be interpreted = to limit in any way Huawei=E2=80=99s right to assert any claim of any = patent that is not expressly identified above in this = disclosure.  

Defensive = Assertion Condition: Notwithstanding the Conditional Non-Assertion = Statement, Huawei shall retain the right to assert the above disclosed = patent(s) or patent application(s) (including claiming past royalties) = against any party that asserts directly or indirectly a patent it owns = or controls against Huawei and/or its Affiliates, or against any = products of Huawei or its Affiliates either alone or in combination with = other products, regardless of whether such patent assertion is related = to IETF standards or not.  

FRAND License Available for Additional Use: In the event that any = party seeks the right to use the patent(s) disclosed above in ways that = exceed the scope of the above stated commitment by Huawei, Huawei is = willing to offer FRAND royalty-bearing licenses for such = activities.
=3D=3D=3D=3D STOP = =3D=3D=3D=3D


Kent // = co-chair


On = Oct 15, 2023, at 10:56 AM, Kent Watsen <kent+ietf@watsen.net> = wrote:

Authors, Contributors, WG,

As a prerequisite for the adoption = on this document:

= External Trace ID for = Configuration Tracing
= https://datatracker.ietf.org/doc/draft-quilbeuf-netconf-co= nfiguration-tracing-00

Are you aware of any IPR that = applies to draft identified above?

Please state either:

"No, I'm not aware of any IPR that applies to this = draft=E2=80=9D
or
"Yes, I'm aware of IPR that applies to this draft"

If so, has this IPR been = disclosed in compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, = please state either:

"Yes, the IPR has been disclosed in = compliance with IETF IPR rules=E2=80=9D
or
"No, the IPR has not been disclosed"

If you answer no, please provide = any additional details you think
appropriate.

If you are listed as a document author or contributor please = answer the
above by responding to this email = regardless of whether or not you are
aware of any = relevant IPR. This document will not advance to the next
stage until a response has been received from each = author.

Also please send the response to the list above, and not unicast = it.

FWIW, = currently, no IPR = is filed for this draft: https://datatracker.ietf.org/= ipr/search/?submit=3Ddraft&id=3Ddraft-quilbeuf-netconf-configuration-t= racing.  That said, = it is noted that the previous version of this draft (in OPSAWG) had IPR = filed for it here: https://datatracker.ietf.or= g/ipr/5995.  I have = requested the IETF Secretariat to move that IPR disclosure to this = draft (in NETCONF).

Thanks.
Kent (as co-chair)

__________________________________________= _____
netconf mailing = list
netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf<= br>

= --Apple-Mail=_7F574FDC-6011-42E7-ADAE-2419F976A0FE--