Re: ipr-wg was Proposal to cease accepting IPR disclosures by unstructured email
Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 16 June 2022 11:12 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 ABB33C13C2D7 for <ipr-wg@ietfa.amsl.com>; Thu, 16 Jun 2022 04:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.213
X-Spam-Level:
X-Spam-Status: No, score=-1.213 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=-1.876, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, 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 MurSewYIj3sg for <ipr-wg@ietfa.amsl.com>; Thu, 16 Jun 2022 04:12:13 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 DC16FC14CF05 for <ipr-wg@ietf.org>; Thu, 16 Jun 2022 04:11:08 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 25GBB7RP022048 for <ipr-wg@ietf.org>; Thu, 16 Jun 2022 13:11:07 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 53EC4206230 for <ipr-wg@ietf.org>; Thu, 16 Jun 2022 13:11:07 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 49FE820619B for <ipr-wg@ietf.org>; Thu, 16 Jun 2022 13:11:07 +0200 (CEST)
Received: from [10.8.32.70] (is156570.intra.cea.fr [10.8.32.70]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 25GBB7ND064573 for <ipr-wg@ietf.org>; Thu, 16 Jun 2022 13:11:07 +0200
Message-ID: <235f9c45-536a-b765-c0d7-4616e7ae9db7@gmail.com>
Date: Thu, 16 Jun 2022 13:11:07 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Subject: Re: ipr-wg was Proposal to cease accepting IPR disclosures by unstructured email
Content-Language: fr
To: 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>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
In-Reply-To: <5FE37944.3020203@btconnect.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipr-wg/o9uCcobMODfxDldssLzIPAHcqIA>
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: Thu, 16 Jun 2022 11:12:17 -0000
Ideally, I would need to have access to all private declarations of IPR _absence_, not their presence. I understand that all RFC authors are demanded during the last phases prior to RFC issuance to state what they know about IPR. In the instances of RFCs where I was an author, all replies from authors, including myself, were such declarations of absence of IPR. These statements are however not captured on https://datatracker.ietf.org/ipr/ 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). Alex Le 23/12/2020 à 18:07, tom petch a écrit : > > > On 22/12/2020 19:44, Brian E Carpenter wrote: >> John, >> >> IMHO your point is clearly out of scope for the admin list since it >> raises an IETF process issue. So I've have bcc'ed the admin list and, >> since we don't have an ipr-discuss list, added the IETF list. You said: > > > We used to, the ipr-wg, and the website tells you how to subscribe to > the mailng list although as the last archive entry is 2014 there would > likely not be much traffic but if like me you never get reminders and > never get around to unsubscribing there could still be interested > parties on it. > > Tom Petch > >>> If IPR arises after adoption, the draft should >>> automatically return to an adoption call - but much better to simply not >>> allow it. >> >> Firstly, an adoption call is not a formal or required part of the IETF >> process, it is simply a pragmatic step that some WGs use (see >> RFC7221). So we can't have a requirement to repeat a step that isn't >> required in the first place. >> >> Secondly, we have no power to "disallow" late IPR disclosures. >> Sometimes people only discover patents late, and do us a favour by >> notifying them. That particularly applies to third party disclosures, >> or patents elsewhere in a large company**. Sometimes people are >> legally or contractually unable to make disclosures until their >> employer decides to publish an application. I'm sure there are other >> cases too, such as when an IETF Last Call triggers a disclosure by >> somebody who has been unaware of the draft until then. We may not like >> it, but there will always be late disclosures. >> >> Therefore we just have to deal with them when they arrive. >> >> Regards >> Brian Carpenter >> >> ** Note that our rules do not require a patent search. From RFC8179: >> >>>> m. "Reasonably and personally known": something an individual knows >>>> personally or, because of the job the individual holds, would >>>> reasonably be expected to know. This wording is used to >>>> indicate >>>> that an organization cannot purposely keep an individual in the >>>> dark about patents or patent applications just to avoid the >>>> disclosure requirement. But this requirement should not be >>>> interpreted as requiring the IETF Contributor or Participant (or >>>> his or her represented organization, if any) to perform a patent >>>> search to find applicable IPR. >> >> On 23-Dec-20 07:11, john heasley wrote: >>> Fri, Dec 18, 2020 at 09:27:11AM +1300, IETF Executive Director: >>>> The IETF Administration LLC is proposing to cease accepting IPR >>>> disclosures by unstructured email and making the existing mechanism >>>> of a structured form the sole mechanism for submitting IPR >>>> disclosures. We are now seeking feedback on this proposal. >>>> >>>> IPR disclosures can currently be submitted by one of three >>>> Datatracker forms [1] [2] [3] or by email. The forms are highly >>>> structured and the IPR disclosures are stored in a database that can >>>> be both browsed [4] and searched [5] using this structure, >>>> >>>> Email submissions, provided for historical compatibility, often >>>> require significant backend processing and judgement calls from the >>>> Secretariat on what data should be extracted from the email for each >>>> field in the database. The volumes are small, generally only one or >>>> two a month, but on occasion they are tens of pages long with >>>> multiple disclosures extracted. Notwithstanding the low volumes, it >>>> is our view that it is inappropriate to ask the Secretariat to >>>> decide what content to include/exclude and how to represent it, for >>>> such a legally sensitive area and that we should not be processing >>>> of IPR disclosures in this way. Consequently, we propose to cease >>>> accepting IPR disclosure by email. >>>> >>>> If you have any feedback on this proposal, please send it directly >>>> to me or to the admin-discuss list before Friday 8th January 2021. >>> >>> I think this is a good idea. I do not have negative comment on this >>> proposal, but on IPR in general. I am of the opinion that IPR should be >>> required BEFORE a draft can be considered for adoption and allowed at no >>> time afterward. If IPR arises after adoption, the draft should >>> automatically return to an adoption call - but much better to simply not >>> allow it. >>> >>> I think that WGs should have the opportunity to consider restrictions >>> of IPR before they spend any time on a draft. I have no interest in >>> improving a work that has unclear or restrictive IPR - not knowing about >>> IPR until after adoption or even later amounts to free consulting. It >>> is not unreasonable to require a company to figure-out their IPR >>> beforehand. >>> >>> I have seen a few IPR that are open, but whose current and/or future >>> restrictions are unclear. >>> >>>> Any IPR disclosures received by email from now on will not be >>>> processed until a final decision is made on this proposal. >>>> Submitters will be notified of that so that they can submit by a >>>> form if they choose. >>>> >>>> [1] https://datatracker.ietf.org/ipr/new-specific/ >>>> [2] https://datatracker.ietf.org/ipr/new-generic/ >>>> [3] https://datatracker.ietf.org/ipr/new-third-party/ >>>> [4] https://datatracker.ietf.org/ipr/ >>>> [5] https://datatracker.ietf.org/ipr/search/ >>>> >>>> -- >>>> Jay Daley >>>> IETF Executive Director >>>> exec-director@ietf.org >>>> >>>> >>>> >>>> _______________________________________________ >>>> IETF-Announce mailing list >>>> IETF-Announce@ietf.org >>>> https://www.ietf.org/mailman/listinfo/ietf-announce >>> >> >> . >> > > _______________________________________________ > Ipr-wg mailing list > Ipr-wg@ietf.org > https://www.ietf.org/mailman/listinfo/ipr-wg
- ipr-wg was Proposal to cease accepting IPR disclo… tom petch
- Re: ipr-wg was Proposal to cease accepting IPR di… Stephan Wenger
- Re: ipr-wg was Proposal to cease accepting IPR di… Alexandre Petrescu
- Re: ipr-wg was Proposal to cease accepting IPR di… Lars Eggert
- Re: ipr-wg was Proposal to cease accepting IPR di… Brian Carpenter
- Re: ipr-wg was Proposal to cease accepting IPR di… Alexandre Petrescu
- Re: ipr-wg was Proposal to cease accepting IPR di… Alexandre Petrescu
- Re: ipr-wg was Proposal to cease accepting IPR di… Alan Clark
- Re: ipr-wg was Proposal to cease accepting IPR di… Bradner, Scott
- Re: ipr-wg was Proposal to cease accepting IPR di… John C Klensin
- Re: ipr-wg was Proposal to cease accepting IPR di… Bradner, Scott
- Re: ipr-wg was Proposal to cease accepting IPR di… John C Klensin
- Re: ipr-wg was Proposal to cease accepting IPR di… Bradner, Scott
- Re: ipr-wg was Proposal to cease accepting IPR di… Brian E Carpenter
- Re: ipr-wg was Proposal to cease accepting IPR di… John C Klensin
- Re: ipr-wg was Proposal to cease accepting IPR di… Martin J. Dürst
- Re: ipr-wg was Proposal to cease accepting IPR di… Carsten Bormann
- Re: ipr-wg was Proposal to cease accepting IPR di… Bradner, Scott
- Re: ipr-wg was Proposal to cease accepting IPR di… Scott Bradner
- Re: ipr-wg was Proposal to cease accepting IPR di… Carsten Bormann
- Re: ipr-wg was Proposal to cease accepting IPR di… Scott Bradner
- Subject discipline (was Re: ipr-wg was Proposal t… Robert Sparks
- Re: unstructured email and IPR Alexandre Petrescu