IETF Logo Mail Archive

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

Lixia Zhang <lixia@cs.ucla.edu> Sun, 15 February 2026 05:26 UTC

Return-Path: <lixia@cs.ucla.edu>
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 9036CB7C0F5F for <ietf@mail2.ietf.org>; Sat, 14 Feb 2026 21:26:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=cs.ucla.edu
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 LVk9R46MBET6 for <ietf@mail2.ietf.org>; Sat, 14 Feb 2026 21:26:31 -0800 (PST)
Received: from mail.cs.ucla.edu (mail.cs.ucla.edu [131.179.128.66]) (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 AE7F0B7C0BC8 for <ietf@ietf.org>; Sat, 14 Feb 2026 21:26:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id 3BF983C011CA0; Sat, 14 Feb 2026 21:26:13 -0800 (PST)
Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10032) with ESMTP id eJ0wUpAVwRV2; Sat, 14 Feb 2026 21:26:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id 16DC33C013275; Sat, 14 Feb 2026 21:26:13 -0800 (PST)
DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cs.ucla.edu 16DC33C013275
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.ucla.edu; s=9D0B346E-2AEB-11ED-9476-E14B719DCE6C; t=1771133173; bh=lpzb31/h8nOGm9MaFNBqL3jqe4IsBwcOnagRi/xpeKs=; h=Mime-Version:From:Date:Message-Id:To; b=kWE0Nu2pz/r2RUMVmFzv4WbF7wf0iUHaCetE7WNFssQjiYPvoSMEWBx+VvVN5e0nJ hg4m71M+PfZaMPbegr1rvbG8bHpctGXTv0j95JVj0vvjj7/LbDVNGTw+Auso127uiA his+gQtN1yc+lQo6hEt69E8darI5K9Np1JlN1R402OLLNS8fgoW9bEOnsxsSV5Bekr GC4NN0NkDqFJKhb6VasqHrOz9kUf8FdUOrofU3z0EZapeYA7tQN6YEOUfh6ENUzIgX X/uwIrn7csgJftAgVOap2kgkdWDqyyQ5EZ+B3L/yz3yXEE4Rmt+t/6Ee2wqgZiLXxu 5W05Mqkldjbqw==
X-Virus-Scanned: amavis at mail.cs.ucla.edu
Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id UHRgVdNQKzeC; Sat, 14 Feb 2026 21:26:12 -0800 (PST)
Received: from smtpclient.apple (unknown [76.91.6.91]) by mail.cs.ucla.edu (Postfix) with ESMTPSA id D8C4C3C011CA0; Sat, 14 Feb 2026 21:26:12 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.300.41.1.7\))
Subject: Re: AI disclosure [was: AI slop "contributions" to IETF working groups]
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <13577ccf-e206-7fdd-0ad3-807fbd256637@taugh.com>
Date: Sat, 14 Feb 2026 21:26:02 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B4107802-846D-4482-B398-19AA347D9A81@cs.ucla.edu>
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> <42FF8C5A-AA7C-4F51-A2F2-34682E2A4C14@cs.ucla.edu> <13577ccf-e206-7fdd-0ad3-807fbd256637@taugh.com>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3864.300.41.1.7)
Message-ID-Hash: HWNBEYGMII6GKS54ZD7JIFU5CW5Q62RR
X-Message-ID-Hash: HWNBEYGMII6GKS54ZD7JIFU5CW5Q62RR
X-MailFrom: lixia@cs.ucla.edu
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: IETF general 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/9fac6yaoA9oH5dQuBQ3YmlOAVc8>
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 Feb 11, 2026, at 11:37 AM, John R Levine <johnl@taugh.com> wrote:
> 
> On Wed, 11 Feb 2026, Lixia Zhang wrote:
> 
>> The real question, as I see it, is whether IETF contributions should be submitted by accountable human participants. I believe they should. ...
> 
> I agree that would be a good idea, but it's not what we've done in the past.  There are plenty of messages on IETF mailing lists and the occasional I-D where literally all we know about the contributor is his, her, or its mailing address.
> 
> R's,
> John

I think it’s important to separate two things: what may have happened historically, and what principle we want to guide the process going forward. 

If we agree that IETF contributions should come from accountable human participants, then it seems reasonable for the process to evolve to better reflect that principle.

My 2 cents, Lixia

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