Re: [admin-discuss] Proposal to cease accepting IPR disclosures by unstructured email

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 22 December 2020 19:44 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: admin-discuss@ietfa.amsl.com
Delivered-To: admin-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7E103A1254; Tue, 22 Dec 2020 11:44:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, 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 (2048-bit key) header.d=gmail.com
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 chxXxWtUojq7; Tue, 22 Dec 2020 11:44:35 -0800 (PST)
Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) (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 D60043A113F; Tue, 22 Dec 2020 11:44:34 -0800 (PST)
Received: by mail-pl1-x62c.google.com with SMTP id t6so7962212plq.1; Tue, 22 Dec 2020 11:44:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=JfmDzvOdziMXvJPGjGFWFfPjteAgRal78GmL4YKiUqc=; b=E7n2AIvboOp39jUkeLrjGN0hSMObDsRGwnZpkT+KBYu/m0dZboveto5UJtjII9ZIPY 1Elq37mD+1FyrjhBok9xMt7cq45CJ/yDrQ4tPi/aQPg/0ABNTVcYxbJrP/Y3RRUKyOqY 6b1QU557s6vSQCkkQtmS3kyKPQV6Zqeh48dvbwhUERypHEPmjw3a0l/7IzV5/1RuWzn8 MOvffBhF9O2lB5D5IHVgyb6pwtMnZ4x/i4/42lHIlNdKZ/aWa+5OcCgG6/8Bh44UWQSx liE8qXRE8vymzsNZCnmwU3oYmGYGRM1odZC5hWl/eAI/8HY2XeDCRxfAv/tjTN/MaQ18 VNrQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=JfmDzvOdziMXvJPGjGFWFfPjteAgRal78GmL4YKiUqc=; b=kpAmanVnWdmo8wT2jYVXua+a3tp3ZdOsw9mGguoBN9dVv5zFPfCdQbv+dRPKPTCkjl uGbIr/o+ZMsM/Q1ei2kRFciZHHwLclWeC4D4jVLd8CKVvHznTIJqDdCQP8TEAxhznHf2 hHewOuK60qjEMBMOUNJOhboulj4gslWXtBcGv/c5C95vnqXxr4v5pkcuBnQ1hz4z0KyA e2G2KNL6sThIK99QjkYNM1jFvFx3TEde1yGm9kauRiCAQiQaWB0um1+ErA/SuQLw4n9w oPfZIXX804PTtDLeinEjGwZIfNPGEABoA3z7gUeLiTmHusEcb2Z4hgEfGmKPqsx1zRWO ctGA==
X-Gm-Message-State: AOAM531Bq+2K/ngUFGwfAIpBR18W6VFD3sHUjaOkSoxTlSsiI/s8C+VL LIYo45t0ulu4ZH3ugZ/jtpUCtlM13U/sRQ==
X-Google-Smtp-Source: ABdhPJzVEA1C0DOyrQ9Yy5RX7wJD9QqybRlxBCp6ejFdSAyE46JtcCODdfEAew+RKE3VlVHWYrcIZg==
X-Received: by 2002:a17:90b:60b:: with SMTP id gb11mr24045333pjb.122.1608666273816; Tue, 22 Dec 2020 11:44:33 -0800 (PST)
Received: from [192.168.178.20] ([151.210.131.28]) by smtp.gmail.com with ESMTPSA id z10sm21677764pfr.204.2020.12.22.11.44.31 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 Dec 2020 11:44:32 -0800 (PST)
To: john heasley <heas@shrubbery.net>
References: <CCFDE8BD-FC28-4E32-8861-06870AAB5AFE@ietf.org> <X+I2w3vrKZ2rLg1N@shrubbery.net>
Cc: IETF discussion list <ietf@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <acca1f7c-21b7-7e88-7456-5d1fbb0e7983@gmail.com>
Date: Wed, 23 Dec 2020 08:44:29 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <X+I2w3vrKZ2rLg1N@shrubbery.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/admin-discuss/acTfDWjrhQCxRENk5g-Hr71D1oA>
X-Mailman-Approved-At: Tue, 22 Dec 2020 12:29:44 -0800
Subject: Re: [admin-discuss] Proposal to cease accepting IPR disclosures by unstructured email
X-BeenThere: admin-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for IETF LLC administrative issues <admin-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/admin-discuss/>
List-Post: <mailto:admin-discuss@ietf.org>
List-Help: <mailto:admin-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Dec 2020 19:44:37 -0000

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:

> 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
>