From benoit.claise@huawei.com Mon Oct 16 00:14:20 2023 Return-Path: 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 F32F7C151547 for ; Mon, 16 Oct 2023 00:14:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.994 X-Spam-Level: X-Spam-Status: No, score=-1.994 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.091, RCVD_IN_MSPIKE_H5=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_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 LMUwrqLquEz2 for ; Mon, 16 Oct 2023 00:14:18 -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 9AC64C15152D for ; Mon, 16 Oct 2023 00:13:34 -0700 (PDT) Received: from frapeml500001.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4S87Y06ZHSz67Ph9; Mon, 16 Oct 2023 15:10:12 +0800 (CST) Received: from [10.45.156.166] (10.45.156.166) by frapeml500001.china.huawei.com (7.182.85.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Mon, 16 Oct 2023 09:13:24 +0200 Content-Type: multipart/alternative; boundary="------------rW86Ik8vvJbX6yuyK1nPmiQm" Message-ID: Date: Mon, 16 Oct 2023 09:13:19 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Content-Language: en-GB To: Kent Watsen , Jean Quilbeuf , Benoit Claise , Thomas Graf , Diego Lopez , Sun Qiong CC: "netconf@ietf.org" References: <0100018b33d7238d-d0ccba02-7474-4aa3-86de-08f0007db5f0-000000@email.amazonses.com> From: Benoit Claise In-Reply-To: <0100018b33d7238d-d0ccba02-7474-4aa3-86de-08f0007db5f0-000000@email.amazonses.com> X-Originating-IP: [10.45.156.166] X-ClientProxiedBy: dggems703-chm.china.huawei.com (10.3.19.180) To frapeml500001.china.huawei.com (7.182.85.94) X-CFilter-Loop: Reflected 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: Mon, 16 Oct 2023 07:14:20 -0000 --------------rW86Ik8vvJbX6yuyK1nPmiQm Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit Dear all, draft-quilbeuf-netconf-configuration-tracing-00 is a replacement for draft-quilbeuf-opsawg-configuration-tracing-02 Note: I am trying to get the "replaced-by" field updated in the datatracker. And there was an IPR on the old draft-quilbeuf-opsawg-configuration-tracing, which should be transferred to the new draft. Note: I am also working on that front. Regards, Benoit On 10/15/2023 4:56 PM, Kent Watsen 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-configuration-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” > 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” > 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=draft&id=draft-quilbeuf-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). > > Thanks. > Kent (as co-chair) > > > _______________________________________________ > netconf mailing list > netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf --------------rW86Ik8vvJbX6yuyK1nPmiQm Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 8bit Dear all,

draft-quilbeuf-netconf-configuration-tracing-00 is a replacement for draft-quilbeuf-opsawg-configuration-tracing-02
Note: I am trying to get the "replaced-by" field updated in the datatracker.
And there was an IPR on the old draft-quilbeuf-opsawg-configuration-tracing, which should be transferred to the new draft.
Note: I am also working on that front.

Regards, Benoit

On 10/15/2023 4:56 PM, Kent Watsen 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-configuration-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”
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”
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=draft&id=draft-quilbeuf-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).

Thanks.
Kent (as co-chair)


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

--------------rW86Ik8vvJbX6yuyK1nPmiQm--