Re: legal consultation (was List moderator action)

Joel Halpern <jmh@joelhalpern.com> Fri, 08 May 2026 16:06 UTC

Return-Path: <jmh@joelhalpern.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 37D3EEB46E10 for <ietf@mail2.ietf.org>; Fri, 8 May 2026 09:06:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778256396; bh=D/R0eNSBFOhYokbgsoh5k1Rn9ezgSaDjdHihZPM4j04=; h=Date:Subject:To:References:From:In-Reply-To; b=ZLWHZJBAXc2ieS+Zrq+yFdtH/nA4Y3YAxkJfb+f6CkkEK0WUENwk5BRfMUNM7U0b2 2zVXVXUdTE962J7rhjjC99l6K9JVESsObbgwgztqzR+SH3cTHAaPWVDhp7vvBXg+G1 UA2W2OU6+2QOSgmPE/JhLEfqxcdB1rFK558cZWaY=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 IQaJ5avXyvML for <ietf@mail2.ietf.org>; Fri, 8 May 2026 09:06:32 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 296ADEB46D3B for <ietf@ietf.org>; Fri, 8 May 2026 09:05:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1778256316; bh=vx6wEnDWo4UcFhi04j4uyDHxk/gZQiBGDU7ZBPwSC+4=; h=Date:Subject:To:References:From:In-Reply-To:From; b=JnDTAmveHMbJWIn+V8hEloQ8gL0Q6u9JYu3onPDC+LcP+7UdsTdPO5DU0xGO5rLB2 42WvewzCB5DyW9WCQxGtrBprfc6kk9skzAAUL7XWPdjbBMODFEgkopEH0Jm6/aEwYN 6U8Nyle9y6dFNYvx4zbH5lj7vip4TYQOj113qzUU=
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4gBv8r3F70z2GcmV; Fri, 8 May 2026 09:05:16 -0700 (PDT)
X-Quarantine-ID: <l3fQIT3GV7zp>
X-Virus-Scanned: Debian amavis at b2.tigertech.net
Received: from [IPV6:2600:8806:101:d200:acd1:8915:7dc8:f408] (unknown [IPv6:2600:8806:101:d200:acd1:8915:7dc8:f408]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4gBv8q2pJKz1pd0c; Fri, 8 May 2026 09:05:14 -0700 (PDT)
Message-ID: <a6e333a1-f7f7-4072-a69c-5977c64ffbcf@joelhalpern.com>
Date: Fri, 08 May 2026 12:05:12 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: legal consultation (was List moderator action)
To: Jacob Appelbaum <jacob@appelbaum.net>, ietf@ietf.org
References: <CAChr6Sy1jsjNzh1qMEDVx7ABp_1_uPkfx_tY-T7zPpXTdZiXtQ@mail.gmail.com> <877bpgb7bq.fsf@josefsson.org> <c7aae006-be27-4beb-9553-0b8efb4bd600@gmail.com> <90ff4853-a4e3-421d-a2f5-91e64c7fcb88@gmail.com> <LV8PR11MB8536275B26F2477999444366B53D2@LV8PR11MB8536.namprd11.prod.outlook.com> <3c1c7b27-14fa-4544-8e81-0379e541cda1@appelbaum.net>
Content-Language: en-US
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <3c1c7b27-14fa-4544-8e81-0379e541cda1@appelbaum.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: S37HVUV3DS6I3RMVHUGIKXX6KAU6N24U
X-Message-ID-Hash: S37HVUV3DS6I3RMVHUGIKXX6KAU6N24U
X-MailFrom: jmh@joelhalpern.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
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/jo9k2fLEREVvCU1_cas_E5zvDM8>
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>

That would be a much larger change than what has been discussed in this 
thread.  I would hope we don't go there.

Yours,

Joel

On 5/8/2026 11:52 AM, Jacob Appelbaum wrote:
> Hi Rob,
>
> On 5/8/26 17:13, Rob Wilton (rwilton) wrote:
>> For some reason, I suspect because many of us are engineers, the
>> IETF often seems to avoid the simplest solution to a given problem.
>>
>> We publish lots of RFCs, a very tiny fraction of them use the no
>> derivatives clause.  The pain & hassle of allowing for "no
>> derivatives" vastly outweighs any benefits of allowing it.
>>
>> At John pointed out, there are loads of alternative ways to publish
>> stuff on the Internet.  Let's just get rid of this (ideally from all
>> streams, but at least the IETF stream) and move on with a very
>> slightly simpler IETF/RFC process than we have today.
>>
>
> I think your suggestion is reasonable for the future.
>
> Could we set the standard that people making contributions are 
> automatically placed into the public domain?
>
> It would resolve the data usage equity discussion relating to AI and 
> other consumers of the data.
>
> Kind regards,
> Jacob
>
> P.S.
> This email is hereby placed into the public domain.
>