Re: ipr-wg was Proposal to cease accepting IPR disclosures by unstructured email

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 18 July 2022 12:06 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipr-wg@ietfa.amsl.com
Delivered-To: ipr-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15E6EC14CF04 for <ipr-wg@ietfa.amsl.com>; Mon, 18 Jul 2022 05:06:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.66
X-Spam-Level:
X-Spam-Status: No, score=0.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 eZTsJUXilK4B for <ipr-wg@ietfa.amsl.com>; Mon, 18 Jul 2022 05:06:13 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 00D50C159486 for <ipr-wg@ietf.org>; Mon, 18 Jul 2022 05:06:10 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 26IC62GD057149; Mon, 18 Jul 2022 14:06:02 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id F40F72043C8; Mon, 18 Jul 2022 14:06:01 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id E6DFF2043C7; Mon, 18 Jul 2022 14:06:01 +0200 (CEST)
Received: from [10.8.32.70] (is156570.intra.cea.fr [10.8.32.70]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 26IC61j1029786; Mon, 18 Jul 2022 14:06:01 +0200
Message-ID: <fe9ce19a-f446-1382-1e57-ef7d01f1c047@gmail.com>
Date: Mon, 18 Jul 2022 14:06:01 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Subject: Re: ipr-wg was Proposal to cease accepting IPR disclosures by unstructured email
Content-Language: fr
To: Lars Eggert <lars@eggert.org>
Cc: ipr-wg@ietf.org
References: <CCFDE8BD-FC28-4E32-8861-06870AAB5AFE@ietf.org> <X+I2w3vrKZ2rLg1N@shrubbery.net> <acca1f7c-21b7-7e88-7456-5d1fbb0e7983@gmail.com> <5FE37944.3020203@btconnect.com> <235f9c45-536a-b765-c0d7-4616e7ae9db7@gmail.com> <E34E4E8C-EC51-4109-A55E-154DECF18BC7@eggert.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
In-Reply-To: <E34E4E8C-EC51-4109-A55E-154DECF18BC7@eggert.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipr-wg/JN4pLs7A3zx50dsX1iLhhIYhhog>
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipr-wg/>
List-Post: <mailto:ipr-wg@ietf.org>
List-Help: <mailto:ipr-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2022 12:06:17 -0000


Le 20/06/2022 à 08:52, Lars Eggert a écrit :
> Hi,
> 
> On 2022-6-16, at 14:11, Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
>> Ideally, I would need to have access to all private declarations of IPR _absence_, not their presence.
> 
> most contributors cannot make declarations about the absence of IPR, not even about IPR from their own organizations. (And in my understanding, most organizations can't, for various reasons, either.)
> 
>> I understand that all RFC authors are demanded during the last phases prior to RFC issuance to state what they know about IPR.
> 
> All authors are reminded during the final stages of document processing in a WG that they were under disclosure obligations all along, as are all other contributors. We do this, because in the past, there have been rare cases where authors forgot to do so, or thought their Legal department had done so but didn't. This reminder is supposed to make it easier for people to follow the rules; but the disclosure obligations start when someone begins contributing.
> 
>> In the instances of RFCs where I was an author, all replies from authors, including myself, were such declarations of absence of IPR.
> 
> The question your document shepherd is asking you as an author is:
> 
> "(7) Has each author confirmed that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed. If not, explain why." (https://github.com/ietf-tools/datatracker/blob/5a31658b7f87054237430ee5fab8a23a8b32a7e8/ietf/templates/doc/shepherd_writeup.txt#L30-L32)
> 
> In other words, you are not asked to declare the presence or absence of IPR. You are asked whether you have been following the BCP78/79 disclosure obligations as a contributor to a piece of IETF work, as you are expected to.
> 
>> These statements are however not captured on https://datatracker.ietf.org/ipr/
> 
> Correct. The result of such reaffirmations by authors end up in the document shepherd writeups in some form, which are available in the datatracker, but elsewhere.

Ah, that's right.

I remember the 'shepherd writeups' containing text such as "authors 
declared this or that about IPR".  For an RFC like RFC8691 it is there 
https://datatracker.ietf.org/doc/draft-ietf-ipwave-ipv6-over-80211ocb/shepherdwriteup/

One can see the interpretation of the shepherd of the IPR situation. 
But the original words the authors used, their manner of responding, are 
missing.

> 
>> As such, when this URL says "The IETF Datatracker maintains a list of IPR disclosures made to the IETF." - could be improved.
>>
>> Because not all IPR disclosures made to the IETF are there (e.g. the declarations of absence of IPR are not there).
> 
> That's because an "IPR disclosure" is a carefully-defined term, and your interpretation goes beyond that definition. You might want to re-read Section 5 of BCP79: https://www.rfc-editor.org/rfc/rfc8179.html#section-5

Probably my interpretation is wider.  I will read that URL.

Alex


> 
> Thanks,
> Lars
>