Re: AI slop "contributions" to IETF working groups

Joel Halpern <jmh@joelhalpern.com> Tue, 10 February 2026 15:35 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 23FA5B4C2EF1 for <ietf@mail2.ietf.org>; Tue, 10 Feb 2026 07:35:17 -0800 (PST)
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 kkQr7Mk-8KZI for <ietf@mail2.ietf.org>; Tue, 10 Feb 2026 07:35:16 -0800 (PST)
Received: from maila1.tigertech.net (maila1.tigertech.net [208.80.4.151]) (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 A2475B4C2EEC for <ietf@ietf.org>; Tue, 10 Feb 2026 07:35:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1770737709; bh=GMu1Zeqt8Nvi/VaUvbNBUvfzDIcv42sVpgzAM8UjZLU=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=MoC2TNxWBClf8AJq9LrKqJsKVYnF9lOLVxs8I4QHppxhFx0jJvho8UVEMeBQFZdUK fQbxVudH11OhWnSJCF5PBaW1KXyTg7pjzh2k22QZ42PyQGzkKr4tSpfBaF9iASHguY 1BQSNqbkFZ0pbMkqPSfnoexUVT/4VTFDE37TGMEM=
Received: from localhost (localhost [127.0.0.1]) by maila1.tigertech.net (Postfix) with ESMTP id 4f9QcF6H3Wz4TQpL; Tue, 10 Feb 2026 07:35:09 -0800 (PST)
X-Quarantine-ID: <YOQIGhbvlPrB>
X-Virus-Scanned: Debian amavis at a1.tigertech.net
Received: from [IPV6:2600:8806:103:9500:c9f3:ed7:d3:67bb] (unknown [IPv6:2600:8806:103:9500:c9f3:ed7:d3:67bb]) (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 maila1.tigertech.net (Postfix) with ESMTPSA id 4f9QcF0xFSz4TQbj; Tue, 10 Feb 2026 07:35:08 -0800 (PST)
Message-ID: <b94b3e13-ebc9-4fb1-932f-89b05c2ce3ec@joelhalpern.com>
Date: Tue, 10 Feb 2026 10:35:07 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: AI slop "contributions" to IETF working groups
To: Nick Hilliard <nick@foobar.org>, Christian Hopps <chopps@chopps.org>
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> <d5bccc8e-f013-c3e5-09cc-30913983b2f0@foobar.org>
Content-Language: en-US
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <d5bccc8e-f013-c3e5-09cc-30913983b2f0@foobar.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: RJUFWDF24ZILEOJCX53IWWGOLE4GQ2Z4
X-Message-ID-Hash: RJUFWDF24ZILEOJCX53IWWGOLE4GQ2Z4
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
CC: 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/ArKVib6tBwb2DqdjkLS5ODyhq34>
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>

I presume most folks in this discussiona re aware that we are far from 
alone in this problem?  For example, Bruce Schneier has a nice summary 
of some of the examples and dimensions in 
https://www.schneier.com/blog/archives/2026/02/the-ai-generated-text-arms-race.html

Yours,

Joel

On 2/10/2026 7:05 AM, Nick Hilliard wrote:
> Christian Hopps wrote on 10/02/2026 11:37:
>> So anyway, while we’re (IETF) considering requiring disclosure of AI
>> tool use here, I think it’s worth considering what exactly we’d like
>> this disclosure to accomplish. Is it a filter flag (i.e., if checked
>> “Yes” it get’s dropped to /dev/null by a personal email filter)? Does
>> it help in reviewing the document knowing that AI tools were used.
> IDs and formal documents are only part of the issue. Possibly a 
> greater problem is a contingent of people who are issuing commands like:
>
> "ingest {URL of I-D}, identify 3 substantial problems in the text, 
> write a single paragraph of concise text for each problem in a format 
> suitable for submission to an ietf mailing list"
>
> then cut-n-paste the output into an email.
>
> Nick
>