Re: legal consultation (was List moderator action)

John C Klensin <john-ietf@jck.com> Thu, 07 May 2026 21:53 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 6EBE2EAE01BA for <ietf@mail2.ietf.org>; Thu, 7 May 2026 14:53:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778190824; bh=E5yv2og7hns2Snqt/zv8lx+/7mh0UULLaRnCfFdYoYo=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=nqY4ca9GR2p1EOljCrVFHRfCHP74Um9jy0Oka9LJXPz2yo+wXaucjiGI+uQQ4jhN0 Q65y3rCsUK+5kWPp3NJ6k40qESDxwxfd9mTB4+22lUb2ek65DoZELTXCdpcYBcMQdX PYsCAw94wDTOEG+56oyVb0PCGLvp8nxYZlLuroNA=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jUiQ695OA1-B for <ietf@mail2.ietf.org>; Thu, 7 May 2026 14:53:42 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by mail2.ietf.org (Postfix) with ESMTP id BF50FEAE01B5 for <ietf@ietf.org>; Thu, 7 May 2026 14:53:42 -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 1wL6ex-0002DP-VO; Thu, 07 May 2026 17:53:31 -0400
Date: Thu, 07 May 2026 17:53:26 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Scott Bradner <sob@sobco.com>
Subject: Re: legal consultation (was List moderator action)
Message-ID: <34A42403B6752AFB1D5ADAD4@PSB>
In-Reply-To: <f3508e9a-85c4-4e4d-94d2-dd70262b9a6c@gmail.com>
References: <CAChr6Sy1jsjNzh1qMEDVx7ABp_1_uPkfx_tY-T7zPpXTdZiXtQ@mail.gmail.com> <877bpgb7bq.fsf@josefsson.org> <c7aae006-be27-4beb-9553-0b8efb4bd600@gmail.com> <C52845E5-9189-44B8-8D7F-0BAFF3AC6637@hpe.com> <703DFFB4E2C0103A7A308BB2@PSB> <16781B7E-2AD8-49DA-AD16-BF08F4FAFD50@sobco.com> <f3508e9a-85c4-4e4d-94d2-dd70262b9a6c@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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
Message-ID-Hash: 3IG4QUIHSDIOBS5COY5B7QCPI6SYWLOR
X-Message-ID-Hash: 3IG4QUIHSDIOBS5COY5B7QCPI6SYWLOR
X-MailFrom: john-ietf@jck.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "Scudder, John" <john.scudder@hpe.com>, IETF discussion list <ietf@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vjbi9BlK4rXi4xuSD9FzAWNBY2E>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>


--On Friday, May 8, 2026 09:33 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On 08-May-26 07:57, Scott Bradner wrote:
>> 
>> 
>>> On May 7, 2026, at 3:53 PM, John C Klensin <john-ietf@jck.com>
>>> wrote:
>>> 
>>> ...
>>> 
>>> I don't remember, but I think the strong distinction implied by
>>> "WG adoption" and posting of documents as draft-ietf-WGNAME-...
>>> rather than draft-AuthorName-... came after the no-derivative
>>> language.  If so, that was not a very strong reason.  My memory
>>> could be wrong however.
>> 
>> yup - the non-derivative language needs to be removed in order for
>> a ID to be be adopted (signaled by renaming)
> 
> Yes, but "adoption" is not defined by any of our BCPs.
> 
> However, both Rob and I are proposing in different ways to remove
> this pathway completely.

And Scott, Rich, and I have explained reasons why that would be a bad
idea and tried to suggest ways to mitigate the problems while keeping
the option.  If that means we need to clarify "adoption" first, so be
it -- as you and others have pointed out the number of no-derivatives
documents published in the IETF stream is recent years is not large
enough to require treating this as a huge problem.  And, as I hinted
in another thread, if someone appears to be using the no-derivatives
language as a means of (of with the effect of) causing disruption, we
are, at least IMO, better off focusing on the disruptive behavior
than attacking this provision which might have value in other cases.

   john