Re: [I2nsf] IPR Statements about I2NSF documents

Roman Danyliw <rdd@cert.org> Fri, 07 June 2019 20:47 UTC

Return-Path: <rdd@cert.org>
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 634C1120161 for <i2nsf@ietfa.amsl.com>; Fri, 7 Jun 2019 13:47:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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=cert.org
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 BnDPT8wic4AU for <i2nsf@ietfa.amsl.com>; Fri, 7 Jun 2019 13:47:39 -0700 (PDT)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6684120154 for <i2nsf@ietf.org>; Fri, 7 Jun 2019 13:47:38 -0700 (PDT)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x57KlbXb047386 for <i2nsf@ietf.org>; Fri, 7 Jun 2019 16:47:37 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu x57KlbXb047386
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1559940457; bh=91uh1wExsjqyYoO8H7kC1tJ7x67YkYxDUCcki2IO/gQ=; h=From:To:Subject:Date:References:In-Reply-To:From; b=kuk2JnekUoE0FbRnvHsobN0o1i9LvCp3U2/iquNF6mt5vWhgMjIcBVwbt/EbypEgk M7spjZMwGEEDq7DIWFcHuCub+QZy/IDHRs5j0kl/HMRTgWFzN3Xl22TUPdQ3WEVD7/ hA7gM6NNSplS8ZIZZhWYOMQ5+zyvFULui1n7vOWk=
Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x57KlYXD027228 for <i2nsf@ietf.org>; Fri, 7 Jun 2019 16:47:34 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASCADE.ad.sei.cmu.edu ([10.64.28.248]) with mapi id 14.03.0439.000; Fri, 7 Jun 2019 16:47:33 -0400
From: Roman Danyliw <rdd@cert.org>
To: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: IPR Statements about I2NSF documents
Thread-Index: AQHVHI0RHudWtPBM/UW619Zl6X8otaaQpteAgAAAylA=
Date: Fri, 07 Jun 2019 20:47:33 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC01B3388F88@marathon>
References: <B10BF955-AA3E-47B6-B64C-AB7846F15399@gmail.com> <359EC4B99E040048A7131E0F4E113AFC01B3388F29@marathon>
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFC01B3388F29@marathon>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/6IJPYO9NTkVANHrGVj7aHUcmqq0>
Subject: Re: [I2nsf] IPR Statements about I2NSF documents
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 20:47:42 -0000

Hi!

> From: Yoav Nir [mailto:ynir.ietf@gmail.com]
> Sent: Thursday, June 06, 2019 1:27 PM
> To: i2nsf@ietf.org
> Cc: Roman Danyliw <rdd@cert.org>
> Subject: IPR Statements about I2NSF documents
> 
> Hi
> 
> Yesterday we got 5 IPR statements ([1], [2], [3], [4], [5]) related to the
> following drafts respectively:
> •
> • draft-ietf-i2nsf-nsf-facing-interface-dm
> • draft-ietf-i2nsf-nsf-monitoring-data-model
> • draft-ietf-i2nsf-capability-data-model
> • draft-ietf-i2nsf-registration-interface-dm
> • draft-ietf-i2nsf-consumer-facing-interface-dm
> 
> All of these are WG documents, and one of them (the capability data model
> draft) is in WGLC.  See [6] and RFC 8179 for more information about IPR
> disclosures.
> 
> All the disclosures claim that the patents or patent applications mentioned
> may be necessary for implementation of the drafts. Neither the chairs nor
> anyone else in the IETF is considered competent to evaluate such claims or
> the validity of any patents, so I suggest that in this thread we avoid bringing
> this up. What may be concerning is that the licensing policy for these
> disclosures is "Reasonable and Non-Discriminatory License to All
> Implementers with Possible Royalty/Fee”, which makes such technologies
> problematic to many implementers, especially non-commercial ones.
> 
> To quote from section 7 of RFC 8179:
>    In general, IETF working groups prefer technologies with no known IPR
>    claims or, for technologies with claims against them, an offer of
>    royalty-free licensing.  However, to solve a given technical problem,
>    IETF working groups have the discretion to adopt a technology as to
>    which IPR claims have been made if they feel that this technology is
>    superior enough to alternatives with fewer IPR claims or free
>    licensing to outweigh the potential cost of the licenses.
> 
> 
> So this message is to start a discussion about how the I2NSF working group
> would like to handle this disclosure. Continuing as before and moving to
> publication is the default outcome of this discussion, but the WG is required
> to evaluate its position about these disclosures. This is what this thread is for.

Linda/Yoav: thanks for sending this note out to the WG given these 5 IPR disclosures.  It have nothing more to add as you have precisely summarized the next steps.  I'd only reiterate that the WG needs to come to consensus on a per draft basis on whether "to adopt a technology as to which IPR claims have been made ... and this technology is superior enough to alternatives with fewer IPR claims ... to outweigh the potential cost of the licenses" per RFC8179.

Current/Future draft shepherds: (if it comes to it) Please ensure that this consensus is documented appropriate in a shepherd write-up

Thanks,
Roman

> Thanks,
> 
> 
> Linda & Yoav
> 
> [1] https://datatracker.ietf.org/ipr/3553/
> [2] https://datatracker.ietf.org/ipr/3557/
> [3] https://datatracker.ietf.org/ipr/3556/
> [4] https://datatracker.ietf.org/ipr/3555/
> [5] https://datatracker.ietf.org/ipr/3554/
> [6] https://www.ietf.org/standards/ipr/