IETF Logo Mail Archive

[Gendispatch] Re: A policy for disclosing use of AI in IETF documents and processes?

Nico Williams <nico@cryptonector.com> Wed, 08 April 2026 19:40 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: gendispatch@mail2.ietf.org
Delivered-To: gendispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 3F03AD84A44F for <gendispatch@mail2.ietf.org>; Wed, 8 Apr 2026 12:40:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1775677207; bh=7Jeb59oHcSajTECnfgf3GGRQiME+YECkALme+R4OOFI=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=jrtg/mWnDpny+i7uxwjy+NbysbcLsScqlwJur2o6p4oEcL2Cs+h2WEG2+FYLNNrBK 2tVU14GPkUmgvfncgpYqtYmPk+OFeYynJ/H7wmkTYPvw+gv1gs+89Bfezj8umZJcxu o+mcPeZomFdTLlMUwso/Gu1hYKSBTV5AxZb1Kjho=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=0.001, 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=cryptonector.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 EraK2-pW9-oT for <gendispatch@mail2.ietf.org>; Wed, 8 Apr 2026 12:40:06 -0700 (PDT)
Received: from shrimp.cherry.relay.mailchannels.net (shrimp.cherry.relay.mailchannels.net [23.83.223.164]) (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 A9F06D84A449 for <gendispatch@ietf.org>; Wed, 8 Apr 2026 12:40:06 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 6585E63767; Wed, 08 Apr 2026 19:40:00 +0000 (UTC)
Received: from pdx1-sub0-mail-a251.dreamhost.com (100-100-127-191.trex-nlb.outbound.svc.cluster.local [100.100.127.191]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 11872636A6; Wed, 08 Apr 2026 19:40:00 +0000 (UTC)
ARC-Seal: i=1; a=rsa-sha256; d=mailchannels.net; s=arc-2022; cv=none; t=1775677200; b=OFS235hyN/Ii2QRCDwpEN1Aihdqfi/rVnzmZp8Ysdhk+wp/OG+5lgipFW/WmR6uuAgoVhj Dw+G2O4oRhG6ie9OMA0LW7rJQrs29Alhg21oJ7VFAqQJfB1o93rzPBFBbHXUsp1bnGYr+G wK+ajE85NV5GxqlytERKcn0tMeKXIGTPe0EF8fZEVLzOjCicac7CYv632tmSJq7U3f3jKJ j1o143AwFY1pLoQj8f8UCXeL3NmamU8hufjDj7XRudWGH/XLOcQzUH4mhDjMgXZ8WrHuvb Lu0J44r5q89/7WK9RsgcA31eqB7Oy3uV3M8d9CeLCi6hUQnKMwkSHOGzgRlnjw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1775677200; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=GBBPQqYerWp3fKujI+Dx3ZtbS6AFWB7j5t0XJDBIfa8=; b=6EmQ9VnpiJo5E07Jpdllyxi7DF+xe57mJkBViSvosBthQHSQo/21HlvE5kHwXPUSZw2X9m xzLMoNp829kaWiBlEjida1lxCYRrbaA/4UBmWf52HO0X8S4o1wcUpkYwGo7612lSL+H5QS WNXGGyiQ2lQytAksR+1vWoznybDpV4/8zqhnZiiAUY9cAPQ1i3bONytfzWi8wtbwxYhGXB 0q2qztFg6o/xxya7pHoPX8JwbGdXKLdQDjODXIM/SC1GJJ3kTsBiTxSTOKym1tTJmoW1nP r5rJylJ/dKhFF+UFDmEEU2LbnQjouoyYM8SSIsuGdC2rH02IG68h4DgvuLOfqQ==
ARC-Authentication-Results: i=1; rspamd-bd48b9d95-nmd7z; auth=pass smtp.auth=dreamhost smtp.mailfrom=nico@cryptonector.com
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Illegal-Cooperative: 5336cacc0e2d800d_1775677200282_1727306848
X-MC-Loop-Signature: 1775677200282:790877263
X-MC-Ingress-Time: 1775677200282
Received: from pdx1-sub0-mail-a251.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.100.127.191 (trex/7.1.5); Wed, 08 Apr 2026 19:40:00 +0000
Received: from ubby (unknown [75.81.95.64]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a251.dreamhost.com (Postfix) with ESMTPSA id 4frYLR3mT6z107X; Wed, 8 Apr 2026 12:39:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptonector.com; s=dreamhost; t=1775677199; bh=GBBPQqYerWp3fKujI+Dx3ZtbS6AFWB7j5t0XJDBIfa8=; h=Date:From:To:Cc:Subject:Content-Type:Content-Transfer-Encoding; b=fNjGlJ+9O0Lvi8UWsQuivNv5EvX6Z02fIGkn6J80P/FnFNXm0y1pYSSMs92nxQdKb mUCikDzx+I4RnikfwBhMM5oB3Exu7L6ra/t6vHIXdhlCnVJ8fn7mhd1W6YrftQNMQ6 KO7h4jf2QwIOdsd3V7Lvc93FWWP7s5V6mID9voJQY9h+10BMNwPuGT6vl764Nem+5t Bn/kYXkSiekj/tt9D/o85eSvGWMYcXFIW4KZGr83YUu7z5dwFeggfHXbaAgwYIgPNU ycTFOm3PIH18/MkcaSOzBEYWU6ExHCfijMOQl6TpQ+iH9y+3YMMuIetv2+HsE7CmWS 1v1fw8TWM3+ZA==
Date: Wed, 08 Apr 2026 14:39:57 -0500
From: Nico Williams <nico@cryptonector.com>
To: Joel Halpern <jmh@joelhalpern.com>
Message-ID: <adavDUnkIw/g1Uha@ubby>
References: <dcae2c01-5579-40b9-a098-996a4e6f59df@app.fastmail.com> <CABcZeBMK02kkU50BrqB5mH4SxZiTTOCg_SB_CKyC3L-vZdRppw@mail.gmail.com> <9B719B13-B677-4E69-B78F-5259D8CE99C3@mnot.net> <adaAzDZVxw0WBlEs@ubby> <0b3ed81d-5a28-4b11-b8bd-f301b87d895d@joelhalpern.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <0b3ed81d-5a28-4b11-b8bd-f301b87d895d@joelhalpern.com>
Message-ID-Hash: G2UXS6LPT5X4K5DBVWKOCTMHMOOPD3CQ
X-Message-ID-Hash: G2UXS6LPT5X4K5DBVWKOCTMHMOOPD3CQ
X-MailFrom: nico@cryptonector.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: gendispatch@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Gendispatch] Re: A policy for disclosing use of AI in IETF documents and processes?
List-Id: General Area Dispatch <gendispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/wc7MHEB4v8vjl3d4MvrBVLwQeUE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Owner: <mailto:gendispatch-owner@ietf.org>
List-Post: <mailto:gendispatch@ietf.org>
List-Subscribe: <mailto:gendispatch-join@ietf.org>
List-Unsubscribe: <mailto:gendispatch-leave@ietf.org>

On Wed, Apr 08, 2026 at 12:51:34PM -0400, Joel Halpern wrote:
> The problem I see not very far down the road is that this could easily
> become a deluge of comments on many documents.  [...]

This happens lots outside IETF, so I'm certain that you're right.

I think the way we'll learn to handle that will be:

 - authors will learn to use LLMs to review their work before
   submitting, not just self-review

 - authors / lists will ask the noise makers to stop

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