Re: [hrpc] Patents in draft-tenoever-hrpc-research-05

Niels ten Oever <niels@article19.org> Mon, 19 September 2016 07:46 UTC

Return-Path: <niels@article19.org>
X-Original-To: hrpc@ietfa.amsl.com
Delivered-To: hrpc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 239E512B0BF for <hrpc@ietfa.amsl.com>; Mon, 19 Sep 2016 00:46:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level:
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] 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 kDMXBFuNm_eE for <hrpc@ietfa.amsl.com>; Mon, 19 Sep 2016 00:46:47 -0700 (PDT)
Received: from mail.article19.io (vps784.greenhost.nl [213.108.108.114]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BE7012B08C for <hrpc@irtf.org>; Mon, 19 Sep 2016 00:46:47 -0700 (PDT)
Received: from mail.article19.io (localhost [127.0.0.1]) by mail.article19.io (Postfix) with ESMTPS id AA4951C8730 for <hrpc@irtf.org>; Mon, 19 Sep 2016 07:46:45 +0000 (UTC)
Received: from mail.article19.io (localhost [127.0.0.1]) by mail.article19.io (Postfix) with ESMTPS id 9BE9A1A11CF for <hrpc@irtf.org>; Mon, 19 Sep 2016 07:46:45 +0000 (UTC)
Received: from [192.168.1.71] (sd5112335.adsl.online.nl [213.17.35.53]) by mail.article19.io (Postfix) with ESMTPSA id 9125F18858B for <hrpc@irtf.org>; Mon, 19 Sep 2016 07:46:45 +0000 (UTC)
To: hrpc@irtf.org
References: <20160918193829.GA27308@sources.org> <3112c805-66db-ed18-9f0f-42137938db80@article19.org> <20160919072116.GB756@mx2.yitter.info>
From: Niels ten Oever <niels@article19.org>
Message-ID: <5064cd05-a545-92a7-11db-9dedc31ea73b@article19.org>
Date: Mon, 19 Sep 2016 09:46:44 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160919072116.GB756@mx2.yitter.info>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="Bds957AWKE2VWLR7FaiAhnx0rn3UfpapG"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/WHBx4nVLl1aIzQx2noB8jsUQF5s>
Subject: Re: [hrpc] Patents in draft-tenoever-hrpc-research-05
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "niels@article19.org" <hrpc.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hrpc>, <mailto:hrpc-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hrpc/>
List-Post: <mailto:hrpc@irtf.org>
List-Help: <mailto:hrpc-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hrpc>, <mailto:hrpc-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Sep 2016 07:46:49 -0000

Hi Andrew,


On 09/19/2016 09:21 AM, Andrew Sullivan wrote:
> On Mon, Sep 19, 2016 at 05:13:56PM +1200, Niels ten Oever wrote:
>> The question does not say one should not implement because of patents
>> but asks whether the patent 'would prevent your standard from being
>> fully implemented'. So it asks whether the limits the use (which is not
>> necessarily the case).
> 
> I think the question goes sort of to the heart of who we think the
> audience is.  If the goal is for individuals to consider these
> considerations (which is I think formally what the document says) then
> I don't (speaking personally) have a concern about this question.
> 

This is exactly what it aims to do.

> If the practical goal, however, is actually to influence the way the
> IETF or WGs or something make decisions about these matters, then I
> think Stephane's point is that IPR generally is an issue the IETF has
> wrestled with, and it has come out on the side of not taking a
> position on these matters.  The question above militates against
> taking that non-position, and that might be reason to worry a little
> about this discussion.
> 

Would you have a language suggestion which would help people interpret
this question? I thought the references to RFC3979 RFC6701 would help
reiterate the former reading.

Best,

Niels

> Best regards,
> 
> A
>