Re: [netconf] Regarding IPR on draft-ietf-netconf-https-notif-06

Kent Watsen <kent+ietf@watsen.net> Tue, 15 December 2020 19:40 UTC

Return-Path: <0100017667eade5b-5276e200-ffc8-4236-9771-4ff0abc621fa-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 405CA3A16EA; Tue, 15 Dec 2020 11:40:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3JQYRIRJqwbk; Tue, 15 Dec 2020 11:40:15 -0800 (PST)
Received: from a8-33.smtp-out.amazonses.com (a8-33.smtp-out.amazonses.com [54.240.8.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A0033A16E9; Tue, 15 Dec 2020 11:40:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1608061214; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=9/qV1R8BdDnZAPQIeWXoT0IEH2HXeaRRuz8BvaHfmMQ=; b=iMcC/NiKHI73Xba0XtScKsQnUDxlxMAPhCBfptGj/wgyoWmA3QJZadJOCNcSCozE 3ZcnjbNb4/20IpwxkFyWEsODu/Q4WLrDpTzKDiS9aZiSHpfT0d4Yhn/HJnqi5Ukp/71 LGAn1s2nd60eq863QqFus+Y1Uvg5iMGdMJytiKY8=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100017667eade5b-5276e200-ffc8-4236-9771-4ff0abc621fa-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C08203F7-7AD3-476D-BA1F-6840C1643A3A"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Tue, 15 Dec 2020 19:40:14 +0000
In-Reply-To: <MN2PR11MB4366D0F2866589647C725535B5C60@MN2PR11MB4366.namprd11.prod.outlook.com>
Cc: Mahesh Jethanandani <mjethanandani@gmail.com>, "draft-ietf-netconf-https-notif@ietf.org" <draft-ietf-netconf-https-notif@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>
References: <MN2PR11MB4366D0F2866589647C725535B5C60@MN2PR11MB4366.namprd11.prod.outlook.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-SES-Outgoing: 2020.12.15-54.240.8.33
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/1HuKfDOPbvUL9LqsQHKYkd5pHoU>
Subject: Re: [netconf] Regarding IPR on draft-ietf-netconf-https-notif-06
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Dec 2020 19:40:17 -0000

No, I am not not aware of any IPR that applies to this draft.

Kent (as co-author)


> On Dec 15, 2020, at 12:43 PM, Rob Wilton (rwilton) <rwilton@cisco.com> wrote:
> 
> Authors, Contributors, WG,
> 
> As part of preparation for WG LC (which is planned for after the holidays):
> 
> Are you aware of any IPR that applies to the 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.
> 
> NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.
> 
> If you are on the WG email list or attend WG meetings but are not listed
> as an author or contributor, we remind you of your obligations under
> the IETF IPR rules which encourages you to notify the IETF if you are
> aware of IPR of others on an IETF contribution, or to refrain from
> participating in any contribution or discussion related to your
> undisclosed IPR. For more information, please see the RFCs listed above
> and
> http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.
> 
> Please note, the reason that I am making this request rather than the
> WG chairs is because both chairs are listed as authors on this document.
> 
> Thank you,
> Rob (OPS AD)
> 
> PS Please include all listed in the headers of this message in your
> response.