AI disclosure [was: AI slop "contributions" to IETF working groups]

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 10 February 2026 19:58 UTC

Return-Path: <brian.e.carpenter@gmail.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 D7DB3B4ED25E for <ietf@mail2.ietf.org>; Tue, 10 Feb 2026 11:58:43 -0800 (PST)
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=ham 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 TEj6li1sFG3N for <ietf@mail2.ietf.org>; Tue, 10 Feb 2026 11:58:43 -0800 (PST)
Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (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 7D008B4ED259 for <ietf@ietf.org>; Tue, 10 Feb 2026 11:58:43 -0800 (PST)
Received: by mail-pf1-x429.google.com with SMTP id d2e1a72fcca58-8230c2d3128so635750b3a.0 for <ietf@ietf.org>; Tue, 10 Feb 2026 11:58:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1770753522; x=1771358322; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=RB8ZpEbHc0famOQgoeJNpAR3pUltaTxa//zixT1lBYQ=; b=ju+YVyAKw4UT1dlEGWyJezVNgspg44e9zEoHIVdURVU/inuTPAsWvs7SS2LJOPhf+1 tsWGpp0AqWOa60FcxjX8nGphto4K1mDTw2V0/1d9eGceih7dbfDzFRYF9J89UYYQht9P aP2iCD02NrLk+DHOixvPxZTdILVSuP/tQ5QaM1sVcexIAWgJ8JXMf9UQVHVWYlnFGQJ5 9n0Lz82V6Nq2n20RFbPMAS5AL7datfZrTUPkBLa2A4rjwgu1UG+VJC9RdbZc1PQ3auPi 1KFdfcx8s0iZZuFZspjS1MurJkt1ZPtNTa0/ygMHTxbTbLCBDVSsf8G0J5JmUu5dXJSz pgeA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1770753523; x=1771358323; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=RB8ZpEbHc0famOQgoeJNpAR3pUltaTxa//zixT1lBYQ=; b=kjjWzDpY/hdQqPhWIf5jxqrjbBu+jcWohzQvn4TZ2FUUJIFsMzOjpL1Qqmsr8v7YOv dtNxm5y+AULqqpTNFnaj/FF0BPgr9ASsSyL4gPlESiesM9n8UAoH4+Mbu06WG1G3mq/K qimq8Nd/URglo9Y/zobgUDuqCcIs5X+0N8Y9kNkS3DqBvjHhmrLA60zKM4WdW5p1Y/7Q 7daFpafqIRhpShN6ZX8rUmQItX43vdOnc1d2lw1sfz/cYYbMd5cI0K6NFiCqiLcSamiI RIE7ME3kfB8fQS3dER9j14Rz8j60dAdtM+w00daJZ6GvoiL1fJl4LGfdzIgE3P/uWqNt 4lEQ==
X-Gm-Message-State: AOJu0Yyp8HGYmZB3uXfMxF3YQu+m1NsvZ9zTIz2K1rynWuKA5PhDVz66 ijFhdI5bpXk7QqM9S2q5QA6Z0KY4aJ85NvzxXbjIVqkjiIqgXh+x3Ecn2HuP0gGr
X-Gm-Gg: AZuq6aLE46f8nQifTGT5y9oXZ6Uy92wcyZ9rw348s1VuyZAL3g7UlCvOf4x21IaHXJT nO2pYpcmfprtETkXskvcFYnk50ThqspmVJ+z07ajodNiOg4/79ygT2JAL2NjZQhdQCGaVJfFYU0 9OGIWhNboFLcOBkc6Pcw0BK/thPDATXD48KcQ+eyuTh8Nv2kyGaNjOTjTHF1ODRmsmB9GsumZO4 a/IvOB/VDDP7ZAtuVldZC/BLU1QoqSo26JLZ3ax8fkpOnp+xMzGtqi3vHDpq95IjgDNJG03cWW8 dHBdwZ/mDUx/Fe6driSZjf76ymeJoKza1ieOhsqIGICCh3JTH9KbLJpVWD5c/jlPD4ZQpgxUFQR T63KtYltMBGxhQQIygYU+xc0fp4qfw1x0fuCu9/jgV4O1aXf4c8+D7GbhZfc3bJLecVOXkytfuN uQwjzBlM2FrUVKjGkUCCB5Up0EZGZOtbOZOOv/6JdAu/qvHK5MHPM4IXxQNL7AOM1raZIr8YGzR JSo49do1d+mcxAlyw==
X-Received: by 2002:a05:6a21:3990:b0:371:53a7:a48a with SMTP id adf61e73a8af0-393acf8fa3fmr14855102637.1.1770753522493; Tue, 10 Feb 2026 11:58:42 -0800 (PST)
Received: from ?IPV6:2404:4400:a100:1829:53f3:a236:d026:a00b? ([2404:4400:a100:1829:53f3:a236:d026:a00b]) by smtp.gmail.com with ESMTPSA id 41be03b00d2f7-c6dcb5249a0sm12497444a12.11.2026.02.10.11.58.40 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 10 Feb 2026 11:58:42 -0800 (PST)
Message-ID: <4ab039e3-35d8-4323-993a-9e2fb88b3bf6@gmail.com>
Date: Wed, 11 Feb 2026 08:58:38 +1300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: AI disclosure [was: AI slop "contributions" to IETF working groups]
Content-Language: en-US
To: 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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <m27bsk6d9c.fsf@ja.int.chopps.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Message-ID-Hash: ZNSGUSZOFCQMKTNEA7C3XONRGBF22HNP
X-Message-ID-Hash: ZNSGUSZOFCQMKTNEA7C3XONRGBF22HNP
X-MailFrom: brian.e.carpenter@gmail.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/SQ4ts4B7dF7H0Iva_s5Btg1hW1w>
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>

On 11-Feb-26 00:37, Christian Hopps wrote:
> 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.

For code, I agree, this is a rational policy (as long as the code is licensed without warranty).

For documents that may end up as contractual requirements or as footballs in intellectual property disputes, I think we have to be asking for disclosure. I am definitely not a lawyer but I think that the legal status of ideas originated by an AI is still very unclear. It's rather like claiming that my cat invented a better mousetrap - who owns the IPR, and who is to blame when the mousetrap breaks?

This is quite distinct from the original question about AI slop disrupting IETF discussion, so I changed the subject.

     Brian

> 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]…