Re: [I2nsf] WGLC and IPR poll for draft-ietf-i2nsf-capability-data-model

"Susan Hares" <shares@ndzh.com> Fri, 07 June 2019 21:51 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69463120154 for <i2nsf@ietfa.amsl.com>; Fri, 7 Jun 2019 14:51:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.949
X-Spam-Level:
X-Spam-Status: No, score=0.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 KNokK--5WBP7 for <i2nsf@ietfa.amsl.com>; Fri, 7 Jun 2019 14:51:17 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 637E6120135 for <i2nsf@ietf.org>; Fri, 7 Jun 2019 14:51:17 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=166.177.57.113;
From: Susan Hares <shares@ndzh.com>
To: 'Linda Dunbar' <dunbar.ll@gmail.com>, i2nsf@ietf.org
References: <CAP_bo1Yt+Wms9GDCJqTRiffPfbQk6uG-v4pDCuxoJavg+ZvBnA@mail.gmail.com>
In-Reply-To: <CAP_bo1Yt+Wms9GDCJqTRiffPfbQk6uG-v4pDCuxoJavg+ZvBnA@mail.gmail.com>
Date: Fri, 07 Jun 2019 17:51:14 -0400
Message-ID: <061701d51d7b$218a6ac0$649f4040$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0618_01D51D59.9A7B3BC0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGQZLSjCKpbMVM5TSPB3R7feCh4W6caKrZA
Content-Language: en-us
X-Antivirus: AVG (VPS 190607-4, 06/07/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/9_5AdIbC412K8UY2WEowfTJer88>
Subject: Re: [I2nsf] WGLC and IPR poll for draft-ietf-i2nsf-capability-data-model
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" <i2nsf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2nsf/>
List-Post: <mailto:i2nsf@ietf.org>
List-Help: <mailto:i2nsf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 21:51:19 -0000

As a co-author, I know of no other IPR other than IPR already disclosed. 

  

None of my inputs to the capability data model draft had any IPR attached to it.   

 

As to IPR on this draft, I would expect a more licensing statement such as included in the following IPR. 

https://datatracker.ietf.org/ipr/2611/

 

The IPR terms rather than its existence is a challenge to me as I2NSF member and co-author. 

 

Sue Hares 

 

From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of Linda Dunbar
Sent: Wednesday, June 5, 2019 5:07 PM
To: i2nsf@ietf.org
Subject: [I2nsf] WGLC and IPR poll for draft-ietf-i2nsf-capability-data-model

 

Hello Working Group, 

 

This email starts a three weeks Working Group Last Call on   <https://tools.ietf.org/html/draft-ietf-i2nsf-capability-data-model-04> draft-ietf-i2nsf-capability-data-model-04  . 

This poll runs until June 26, 2019. 

    <https://tools.ietf.org/html/draft-ietf-i2nsf-capability-data-model-04> https://tools.ietf.org/html/draft-ietf-i2nsf-capability-data-model-04

 

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.

 

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.

 

 

Thank you. 

Linda & Yoav