IETF Logo Mail Archive

Re: AI disclosure [was: AI slop "contributions" to IETF working groups]

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 12 February 2026 13:16 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 6A99BB6370F6 for <ietf@mail2.ietf.org>; Thu, 12 Feb 2026 05:16:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 kMhSDgF1UTtB for <ietf@mail2.ietf.org>; Thu, 12 Feb 2026 05:16:40 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 16729B6370EE for <ietf@ietf.org>; Thu, 12 Feb 2026 05:16:40 -0800 (PST)
Received: from dyas.sandelman.ca (unknown [206.0.75.24]) by relay.sandelman.ca (Postfix) with ESMTPS id 3E41D1F469; Thu, 12 Feb 2026 13:16:39 +0000 (UTC)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id AFAC9A01C6; Thu, 12 Feb 2026 08:16:36 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>
Subject: Re: AI disclosure [was: AI slop "contributions" to IETF working groups]
In-Reply-To: <bde787fe-fa31-51bd-abf9-20950c83a3dd@taugh.com>
References: <7b702e8f-d2be-5b08-e262-33fbed538f98@foobar.org> <460BCE12-4C45-45D0-94C8-83B8E2D45049@gmail.com> <922b6d08-1cb5-4791-974f-ff17850de25f@gmail.com> <5DCE2993-39C8-4FAC-AD91-7B8E504E996C@gmail.com> <20260208015537.8D945F5944ED@ary.qy> <cd492277-0bca-4219-a3ad-eb75ccd2ebe7@gmail.com> <m27bsk6d9c.fsf@ja.int.chopps.org> <4ab039e3-35d8-4323-993a-9e2fb88b3bf6@gmail.com> <20260210202604.B0FCFF60E82F@ary.qy> <2215475.1770820599@dyas> <bde787fe-fa31-51bd-abf9-20950c83a3dd@taugh.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 29.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 12 Feb 2026 14:16:36 +0100
Message-ID: <2322748.1770902196@dyas>
Message-ID-Hash: OVL4MXM7O3JYKADGJHQUEVQYBECQX5IR
X-Message-ID-Hash: OVL4MXM7O3JYKADGJHQUEVQYBECQX5IR
X-MailFrom: mcr+ietf@sandelman.ca
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/Ma730MRBzwLbKWeCHSFnTfUSeUA>
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>

John R Levine <johnl@taugh.com> wrote:
    >> > In the United States, the answer is nobody.  US courts have held
    >> that > only people can create copyrighted or patented material, not
    >> robots or > monkeys.*
    >>
    >> So, if IETF (Trust) can't own/license a copyright on an I-D/RFC
    >> produced like that, then I don't think it can pass NoteWell.

    > It's the other way around.  Only material written by people can be
    > copyrighted so anything written by a monkey or a robot is in the public
    > domain and anyone can do anything they want with it.  It's sort of like
    > material written by the US federal government which by policy is also
    > public domain.

So, the IETF Trust/RPC can apply a copyright to this public domain content?
I'm not certain that actually works world-wide.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*

v2.41.0 | Report a Bug | By Email | System Status