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 16:25 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 7CE80D82AE37; Wed, 8 Apr 2026 09:25:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1775665520; bh=ryUQOHuThfJd1mFZTdZM2uyvq8htdxhvr8M0yQIpmuQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=uEdt+HnoLnUHYA/3g7SFjhAXZZUGK1Hr1vrK2mUBy6eHKJ3yCfeiHJo2EAN1vWr2o GNzoY/3S3TeyFGoIq4g1WGMon82skHYobj/yelZFXfF6Z2FLxZym0mefTsnGPxET2m kWFOL9cGmPBTfGPQv5ocUeqq3BNJgOfxmRUSc5qE=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_H3=0.001, RCVD_IN_MSPIKE_WL=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 Jf9X62mNesLS; Wed, 8 Apr 2026 09:25:20 -0700 (PDT)
Received: from giraffe.ash.relay.mailchannels.net (giraffe.ash.relay.mailchannels.net [23.83.222.69]) (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 8F658D82AE0E; Wed, 8 Apr 2026 09:25:19 -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 87A30921890; Wed, 08 Apr 2026 16:25:12 +0000 (UTC)
Received: from pdx1-sub0-mail-a261.dreamhost.com (100-122-235-123.trex-nlb.outbound.svc.cluster.local [100.122.235.123]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 2DD3A922FDB; Wed, 08 Apr 2026 16:25:12 +0000 (UTC)
ARC-Seal: i=1; a=rsa-sha256; d=mailchannels.net; s=arc-2022; cv=none; t=1775665512; b=E23EacGnopJopMbkdr2sHqlMtdULbIvsbJJOG6gXnNgbeMT28MylFy2VujYpr6SpE6kXzd SaP3kCyVjUbM40Eh06PHSz4fFG8EfGGSiMomKSRVU4rAD0i3LwAs7Ww2SfI2euh6dSuVQ4 bXvJra53BCYzPsA/Ku/0L2mMrgVQICOx63KbSPUYq2SqE/uHsp/BVinaELjwNlFVR5oYFS 0Lx7Qpli3KFvdVcy3t1xHmT5mIX0KSYKVIHcrwju4EdVg+gm1a8Qn3a7m+v/NKcGhPo1dd SqLYuUz7vEXG/GaA6NXlQgySGUcH7GnFJui5ymJEuN80CoMSszoi5RpqcMOaHw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1775665512; 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: in-reply-to:in-reply-to:references:references:dkim-signature; bh=bHy59TICn8/YkILT3vQj5sWQFtVpVEwZFDtQKfy83TU=; b=9xF9lQ5oqqHUbLSVvvAwhHz0BBrqnOD7Vt6Go2Pehf0rSkLGpdbHOtLizi+js40kU2HWlt hi9qa3258J/NFxqJHm9L7ZDeq4hm5CaDmIAYPZDEdXzMyMvbyc9akIc4ytA5haH+b0mFjP krjylMwwVfKrT99+rL8B/8xGhHRBWuA4Wlx7cbnEhYxU7NPHgjEQeR59k0vuoNrqTXXAEy Z4A6qoBAagOfVQF6yc/Qy0ii7iRLbuqP/aWhPcW19DvBmRzQLtZJoisuUbDmUiDPue5WUU rKBILc6nCxa2mHRjeza080HTX7gJwjis0BEDf16BFoGyEUnV/oDhZt6Tc0XQ9g==
ARC-Authentication-Results: i=1; rspamd-7d86dcc447-6lzjq; 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-Vacuous-Society: 06878b8a02f13537_1775665512419_3585508217
X-MC-Loop-Signature: 1775665512418:841630084
X-MC-Ingress-Time: 1775665512418
Received: from pdx1-sub0-mail-a261.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.122.235.123 (trex/7.1.5); Wed, 08 Apr 2026 16:25:12 +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-a261.dreamhost.com (Postfix) with ESMTPSA id 4frT1g2n8Dz104q; Wed, 8 Apr 2026 09:25:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptonector.com; s=dreamhost; t=1775665511; bh=bHy59TICn8/YkILT3vQj5sWQFtVpVEwZFDtQKfy83TU=; h=Date:From:To:Cc:Subject:Content-Type; b=EXkpmozHand2GkTpu7cxO2ggzirdshdBsq3b1RXRrkhT7cJcb6N7Rwu+iZyfjpCCP 5cjoqdhPslSMw44EHu8U3zAxOWrxI4xUaoVGEUPiiezzT2UYG/uBG1XIPC3iG511ap tI8fNxXzSTrft39G1s1K+Qm5XhidyZSUZ0W+6+7eXKY0KHn57VAvIsU1uy0REgCu71 rdROGGXnjafsSYKKLj+hRuETwtw7D5JhhM4IfSZaFFdjjjnCx+Y4Mkc0QxyiachItw ArgxVEyURE4+wi8TzyQr80lvpb1B/c/ULHEX46TrlWoYtw4VWg80QSBcj0zEDmHGp+ mk5WkImDmNMbw==
Date: Wed, 08 Apr 2026 11:25:09 -0500
From: Nico Williams <nico@cryptonector.com>
To: Jay Daley <exec-director@ietf.org>
Message-ID: <adaBZbZ38Y2BaXRc@ubby>
References: <dcae2c01-5579-40b9-a098-996a4e6f59df@app.fastmail.com> <CABcZeBMK02kkU50BrqB5mH4SxZiTTOCg_SB_CKyC3L-vZdRppw@mail.gmail.com> <9B719B13-B677-4E69-B78F-5259D8CE99C3@mnot.net> <CABcZeBNORP14FVwDYgcYdbAS91xW55Zwh1jJsoVHcbJZxAnTZw@mail.gmail.com> <4FE3184D-81DB-42C5-A589-F5D05B84AAD6@mnot.net> <CABcZeBPaQ7ZsZXH+ZCWrBZpQfpsrm0FQ=qALfSVcj6Q8-zS=iA@mail.gmail.com> <CAAB58A8-CE74-480D-B793-26BC3A0708C4@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAAB58A8-CE74-480D-B793-26BC3A0708C4@ietf.org>
Message-ID-Hash: ZWWEJKRTKA3NBLLKME7MMUTVKSQD6VJD
X-Message-ID-Hash: ZWWEJKRTKA3NBLLKME7MMUTVKSQD6VJD
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: Eric Rescorla <ekr@rtfm.com>, Mark Nottingham <mnot@mnot.net>, Lucas Pardue <lucas@lucaspardue.com>, 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/3DyWN4dsr2UIMEiGmw_vMiTlSiM>
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:05:05PM +1200, Jay Daley wrote:
> It seems to me that the issue is that some people will (and have)
> treated AI as a distinct entity from the person that used it, thereby
> avoiding responsibility for quality control.  So rather than reiterate
> that AI is a tool, humans approve, etc, it might be simpler just to
> state what the IRTF policy opens with and build on that:
> 
> "Generative artificial intelligence (AI) tools and systems must not be
> listed as authors of [IRTF] documents, presentations, or other
> materials.  Authors cannot shirk responsibility for their text by use
> of AI." 

Excatly.  Reputational risk is a big enough stick and requires no
additional enforcement tools.

Nico
--

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