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

John C Klensin <john-ietf@jck.com> Mon, 18 July 2022 16:38 UTC

Return-Path: <john-ietf@jck.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 9F0CDC16ECA0 for <ipr-wg@ietfa.amsl.com>; Mon, 18 Jul 2022 09:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham 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 lOex4B3nN9DN for <ipr-wg@ietfa.amsl.com>; Mon, 18 Jul 2022 09:38:04 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF4EBC134859 for <ipr-wg@ietf.org>; Mon, 18 Jul 2022 09:37:49 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1oDTkf-000HaM-GT; Mon, 18 Jul 2022 12:37:45 -0400
Date: Mon, 18 Jul 2022 12:37:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Bradner, Scott" <sob@harvard.edu>, Alan Clark <alan.d.clark@telchemy.com>
cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, ipr-wg@ietf.org
Subject: Re: ipr-wg was Proposal to cease accepting IPR disclosures by unstructured email
Message-ID: <5F13E83A33CDF8248A023AAB@PSB>
In-Reply-To: <3DAA135C-F0FA-43DB-8EF0-2C1AE6EA0E43@harvard.edu>
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> <CANMZLAbT_3ipDmyn9GkJH3TLxva-rftcUvmeaWWs48w=4T=yGA@mail.gmail.com> <581e9916-cef3-b3ac-5087-a54f45d44b40@gmail.com> <7914fc8f-70cb-f915-232a-fb25b745395a@telchemy.com> <3DAA135C-F0FA-43DB-8EF0-2C1AE6EA0E43@harvard.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipr-wg/W9JRaHZFw65jWeEtn3Y4AnNDblY>
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 16:38:06 -0000


--On Monday, July 18, 2022 13:11 +0000 "Bradner, Scott"
<sob@harvard.edu> wrote:

>> On Jul 18, 2022, at 9:07 AM, Alan Clark
>> <alan.d.clark@telchemy.com> wrote:
> ...
> 
>> IMHO it would be ideal to make participation in IETF
>> conditional upon early disclosure 
> 
> it is if the participant personally knows of the IPR or
> should, because of his or her job, know of the IPR and has
> been for quite a while

Scott, yes.  But to split an important hair, that prohibition
depends almost entirely on the honesty and good will of the
would-be participant.  If someone decides to conceal IPR they
know about personally, we normally don't find out until much
later.  To the best of my knowledge, we have never withdrawn a
standard because we found out later that the disclosure rules
were not followed even if we might start an effort to supercede
it with something less encumbered.  We have never un-published
an RFC because of disclosure failures, much less tried to sue a
participant for not complying with the rules [1].  Even the most
severe punishments we have for bad behavior --  AFAICT, RFC 3683
revocation of posting rights -- may not be sufficient to prevent
"participation".  IMO (YMMD) there are no real penalties under
the Code of Conduct and the scope of the Ombudsteam does not
include lying to the IETF rather than bad acts against
individuals.  If someone with the authority to do so (IESG?
Trustees? -- not clear to me that there is such an entity)
decided that someone was evil for not disclosing as required, it
isn't clear that there is any documented basis for telling them
they could not register for and attend an IETF meeting.

So, that requirement depends a great deal on good will,
understanding of the provisions, and good intentions.   Without
knowing what Alan by "make ... conditional", if the late
disclosure is deliberate and a deliberate violation of those
rules, the requirement is, AFAICT, fairly toothless.

I don't have an opinion as to whether that could be fixed
without risking even more damage to the IETF.

best,
   john

[1] if one thinks the Note Well and surrounding materials
constitute an actual contract between the participant and the
IETF I presume that would be, in theory, possible.  But IANAL.