Re: AI slop "contributions" to IETF working groups

Christian Hopps <chopps@chopps.org> Tue, 10 February 2026 11:37 UTC

Return-Path: <chopps@chopps.org>
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 486DFB4A275D for <ietf@mail2.ietf.org>; Tue, 10 Feb 2026 03:37:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level:
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
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 jozWP7g3Hn63 for <ietf@mail2.ietf.org>; Tue, 10 Feb 2026 03:37:10 -0800 (PST)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by mail2.ietf.org (Postfix) with ESMTP id D770CB4A2758 for <ietf@ietf.org>; Tue, 10 Feb 2026 03:37:10 -0800 (PST)
Received: from ja.int.chopps.org.chopps.org (unknown [172.222.102.4]) (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) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 7498F7D129; Tue, 10 Feb 2026 11:37:04 +0000 (UTC)
From: Christian Hopps <chopps@chopps.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: AI slop "contributions" to IETF working groups
In-Reply-To: <cd492277-0bca-4219-a3ad-eb75ccd2ebe7@gmail.com> (Brian E. Carpenter's message of "Tue, 10 Feb 2026 09:13:52 +1300")
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>
User-Agent: mu4e 1.12.14; emacs 30.2
Date: Tue, 10 Feb 2026 06:37:03 -0500
Message-ID: <m27bsk6d9c.fsf@ja.int.chopps.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
Message-ID-Hash: 4CRMDGBEGRQIFGUYBJL27MQQQLZNSV6H
X-Message-ID-Hash: 4CRMDGBEGRQIFGUYBJL27MQQQLZNSV6H
X-MailFrom: chopps@chopps.org
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/NDPEQOig9Wkq-2KvxA_p7ombVqM>
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>

Brian E Carpenter <brian.e.carpenter@gmail.com> writes:

> On 08-Feb-26 14:55, John Levine wrote:
>> It appears that Bob Hinden  <bob.hinden@gmail.com> said:
>>> I like the idea of requiring a disclosure that an Internet Draft was written with AI tools.  I agree probably not for emails.
>> I expect that the people whose drafts most suffer from being written by an LLM
>> will lie about it, either because
>> their English is too poor to understand the rules, or they have perverse incentives like an an employer that
>> gives them a bonus for publishing an RFC.
>> Then what?  I’m not saying we shouldn’t ask, but I’m saying we need to be
>> prepared for noncompliance.
>
> Of course, but if we make it a submission requirement - check the “AI used” box - there’s really no harm, no shame.
>
> Actually there are perhaps two boxes to check:
>
> 1. Was AI used in the production of this draft? [yes/no]
> 2. If yes, did the authors personally verify the AI-generated material? [yes/no]

So we’ve been discussing this recently in the FRR development community, and we decided sort of the opposite direction. We require a review and approval for all code pull-requests before they can be merged. Since a code submission will either be good and acceptable, or it won’t be, the fact that AI tools were used to a greater or lesser or no extent really doesn’t matter and we didn’t think it should affect the accept/reject decision.

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.

I *think* what’s being looked for here really is a filter-flag to allow people to ignore submissions with the “wrong” disclosure (e.g., “AI was used, Author did not review” :) In this case everyone is also going to realize that that’s what it’s being used for. Given that, do we really think someone who is willing to post a document as their own work, but also not review that document themselves, is really going to also be honest and admit that? I have my doubts.

Thanks,
Chris.


> The attachment was generated by ChatGPT.
>
>    Brian
>
> [2. image/svg+xml; qq.svg]…