IETF Logo Mail Archive

RE: AI slop "contributions" to IETF working groups

Cheng Li <c.l@huawei.com> Tue, 10 February 2026 03:28 UTC

Return-Path: <c.l@huawei.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 0AF38B47A20C for <ietf@mail2.ietf.org>; Mon, 9 Feb 2026 19:28:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -3.627
X-Spam-Level:
X-Spam-Status: No, score=-3.627 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=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
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 g3tYE6qQzNui for <ietf@mail2.ietf.org>; Mon, 9 Feb 2026 19:28:10 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (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 DDED5B47A201 for <ietf@ietf.org>; Mon, 9 Feb 2026 19:28:09 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.224.150]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4f96SF4y98zJ468L for <ietf@ietf.org>; Tue, 10 Feb 2026 11:27:09 +0800 (CST)
Received: from frapema100003.china.huawei.com (unknown [7.182.19.100]) by mail.maildlp.com (Postfix) with ESMTPS id EC06A40539 for <ietf@ietf.org>; Tue, 10 Feb 2026 11:28:07 +0800 (CST)
Received: from frapema500005.china.huawei.com (7.182.19.99) by frapema100003.china.huawei.com (7.182.19.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.36; Tue, 10 Feb 2026 04:28:07 +0100
Received: from frapema500005.china.huawei.com ([7.182.19.99]) by frapema500005.china.huawei.com ([7.182.19.99]) with mapi id 15.02.1544.011; Tue, 10 Feb 2026 04:28:07 +0100
From: Cheng Li <c.l@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: AI slop "contributions" to IETF working groups
Thread-Topic: AI slop "contributions" to IETF working groups
Thread-Index: AQHcmGDtxAyio+iJnE6hqotpu4sKQ7V3jXiAgAAHSoCAAE3TgIAAF++AgALFLgCAAIoYGQ==
Date: Tue, 10 Feb 2026 03:28:07 +0000
Message-ID: CDBFC30F-6CB7-465A-9D36-72918EC2CC5E
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>
In-Reply-To: <cd492277-0bca-4219-a3ad-eb75ccd2ebe7@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_CDBFC30F6CB7465A9D3672918EC2CC5E_"
MIME-Version: 1.0
Message-ID-Hash: ETNVB2REUE6XB4QTOENGW3EFTC33QS2G
X-Message-ID-Hash: ETNVB2REUE6XB4QTOENGW3EFTC33QS2G
X-MailFrom: c.l@huawei.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" <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/1a33Y1MNzQctRr0VyddWtLijSAQ>
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>

Agree with Bob and Brian that we need to request a disclosure of using AI.

I do not like to read an AI generated document, especially, without human checking, feeling unprofessional and uncomfortable.



Thanks,
Cheng



________________________________

李呈 Li Cheng
Mobile: +86-15116983550(中国电话)
Mail: c.l@huawei.com

发件人：Brian E Carpenter <brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>>
收件人：ietf@ietf.org <ietf@ietf.org<mailto:ietf@ietf.org>>
时 间：2026-02-10 04:14:21
主 题：Re: AI slop "contributions" to IETF working groups

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]

The attachment was generated by ChatGPT.

    Brian

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