IETF Logo Mail Archive

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

Bob Hinden <bob.hinden@gmail.com> Wed, 08 April 2026 16:34 UTC

Return-Path: <bob.hinden@gmail.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 0A477D82B69E for <gendispatch@mail2.ietf.org>; Wed, 8 Apr 2026 09:34:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1775666051; bh=vxyI509lA6hcWX+mQMjYn3WHgz7BSexZimLCbHWRcso=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=bcipcYTq+tONWA3b2ZjGDOwoSA+sZmPvab0F4M5fcHHkCaGKVAGsQ7v8Ofs6D1PoL 4JW/sHVWSRSpThKzisjloyvRMG4paoUT+jxV0/hvYmZFzTtMNTcW/E+JhMjaF8QV7Q 0uLgHUCBuVTsoNW/oheh5bGrVNy5UM0+9X+V4QoI=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 TSURbm3alsuh for <gendispatch@mail2.ietf.org>; Wed, 8 Apr 2026 09:34:10 -0700 (PDT)
Received: from mail-yx1-xb12e.google.com (mail-yx1-xb12e.google.com [IPv6:2607:f8b0:4864:20::b12e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id C7EA3D82B699 for <gendispatch@ietf.org>; Wed, 8 Apr 2026 09:34:10 -0700 (PDT)
Received: by mail-yx1-xb12e.google.com with SMTP id 956f58d0204a3-650775f427eso3002568d50.2 for <gendispatch@ietf.org>; Wed, 08 Apr 2026 09:34:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1775666044; x=1776270844; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=eJsZscvpNlKd/jsXfRrCmVT2tRq38sRbepZq52bSJnA=; b=I3XNm1KXWgEJe0zeBW/zWWp8+Bh+fKW3+hhh3dQgeGs6uGxc6lWCpt2tgopItz6jeE g1ZzuXOs01vwqJWaXab3vCqFygyY2inV3MIbW3BY+WurTjZILnlj3xC/vHxcJEmo8FWD 1yDwZVgZy0vSC+etsnrgDFTMU9NWd/R0OX1fuubvvdwYNphCHn1AcIAOYpSIR35lnoFn URi2v8OaP+/XY8Fn0QQ5+FAFu/tW3GcFDzjB1dxqZcAtpMG0Bs78szNcsc4tBLH5snu0 /xMYgPPUg4i8WZVThIYIoWEM5XoQ5GkYBqOwWMoPR17lo1emiDKO4FFRbjTGPj44obbq HhGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1775666044; x=1776270844; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-gg:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=eJsZscvpNlKd/jsXfRrCmVT2tRq38sRbepZq52bSJnA=; b=WNZMZIG+ZU4ofhp7ELrafvWrXvXjYxFbNrC2OscrnutsD/ExBjJT2wwqyg/LLSwNtk quX1nZAFEU0ragEA9DNt57mdM8nkVPdlKbMeNvJ5B1xRcqD2HK64SdlBYyRr/UHgSbCj jwKtsZiVn4gsFA+1IH6nCsoel3yKQ28+sSJRy8Km7cosXHuMiJhH2oYBmfcvzkO8XeAy qpRmi9AeiO/KbjhBLyhuczM4g+HbPcpv0ZaDwbRbwBfcWyYYAWT+N8/yNCnQKeik5WZp AmxGAHJuFFr0MPXZBHcy+m5v6g+E+W/BCl40OHJK8i1Fnq48+bf4PlGOQQ8lE7cDkyQi 62fg==
X-Forwarded-Encrypted: i=1; AJvYcCWIXcbPpUcUnflmTZewXYlTRcqYfLd6we6G8VKYILSxjzT0jTyfDuTR5keakHj8yD+2f7EvaujhHWjspg==@ietf.org
X-Gm-Message-State: AOJu0YxKBpHqZ4iPCtl7axP7PayYah+k+JtJEm/4vv0bV7DSnVe2PAtt WBRDpRi2x1fLPArCBkj1hu44UMOGzqtb3H3Hfyy2jqD74MC8cZ/xKE0O
X-Gm-Gg: AeBDievDqDI0bzebu7381T0yQiCuenxmmzKnnxKJcRNUGE5372C3ZKlbtkJiWyhvwJx VDtuYf6FcoSvVCcLTHjgHSlw53IlbC+b1olzECJgWzRbM/P01PLK8u8fD93x0zPKhv7aA5Lfuw5 4yY1OhS8Py0uFbrvQT2eNlHeyFbWO+RjZbRg01zal67sGDP5Rkhk4+eurEkIbDxIkUXwc/HXqXs wKaACnhG/80Sz77H0fWMLiIzjqD7rp7jRByJZMLH8dX30/SwYeOQo49WAFXKG7b+iNMbm5qsItQ WyjZstINdXA1TKLp6CsUhHeLuhS5jhU8T6W7bqOkJNclS20+htZ3oo719flSbOc48kxvlWWS4HP KWWbd59RUwacs4YykRIsMXhNL/N/TATphFUb77TXEEFoBySpbPTEGJy6q6u8jLg6kMi9dLY3oBZ FNg9SRDQOTEk431qS+S3Ljw2K3satCYAq0m1uyXdno38Aiy/cjGOBgR2PV
X-Received: by 2002:a05:690e:419c:b0:650:36e6:2ace with SMTP id 956f58d0204a3-65048769416mr22161022d50.31.1775666044023; Wed, 08 Apr 2026 09:34:04 -0700 (PDT)
Received: from smtpclient.apple ([2600:1700:4383:c05f:7599:7c05:11e9:f4eb]) by smtp.gmail.com with ESMTPSA id 956f58d0204a3-6503a9a9271sm9587831d50.15.2026.04.08.09.34.02 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Apr 2026 09:34:03 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.1\))
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <adaBZbZ38Y2BaXRc@ubby>
Date: Wed, 08 Apr 2026 09:33:42 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <00E0729E-80E4-4576-90C8-B8E00AD59995@gmail.com>
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> <adaBZbZ38Y2BaXRc@ubby>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.3864.600.1)
Message-ID-Hash: GEU3FGAI2QKX757BTASOJIW4C4BC5CYP
X-Message-ID-Hash: GEU3FGAI2QKX757BTASOJIW4C4BC5CYP
X-MailFrom: bob.hinden@gmail.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: Bob Hinden <bob.hinden@gmail.com>, Jay Daley <exec-director@ietf.org>, 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/9ddYTIZtixPB33PS-1g93vkCcjg>
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>

Nico,

> On Apr 8, 2026, at 9:25 AM, Nico Williams <nico@cryptonector.com> wrote:
> 
> 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.

Yes, but even without AI, authors make major mistakes in drafts.   That’s why we have multiple steps of review in the IETF process.  These reviews commonly find problems, sometimes major ones.   

Bob

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