IETF Logo Mail Archive

Re: BCP 78 policy / copyright / Generative AI / LLM .. is there a FAQ?

Joe Touch <touch@strayalpha.com> Mon, 18 August 2025 17:55 UTC

Return-Path: <touch@strayalpha.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 E02FB558AB1E for <ietf@mail2.ietf.org>; Mon, 18 Aug 2025 10:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: 1.237
X-Spam-Level: *
X-Spam-Status: No, score=1.237 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_SBL_CSS=3.335, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 Jox_uIgabnZ4 for <ietf@mail2.ietf.org>; Mon, 18 Aug 2025 10:55:56 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 71F01558AB17 for <ietf@ietf.org>; Mon, 18 Aug 2025 10:55:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Transfer-Encoding:Content-Type:Sender: Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender :Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=RwpGsu1ctNiZAuhKTnEwZAkfzcmH4HFb68CZ2335is0=; b=omoG0zDpxLkSFZVoxvL8WU6mWg X8xtqesmdQu4YbM86AIEa3CoRCkqYiO2yG9Nr+kwi6Eq/r7VZKyjM9WrKq+ndlAe2c0VzOoBykwUT CK4E4LrhtHSvijQVO+KyzBEmGB+h/sCXHgipJOfSUd1oa4Ni8xs+WGQUojMkUtMNxlXVGVCVrFeop SBdeBcb53o8CS6XXyuUOr+mtdJP3NynsRtQM2bkUHi8OvzK4+xc3ZtQEQcYm9rYETpzQ7ojUMjhK8 fM0UEjxGrqIKe1LBLmxtbF9LMEPa7phI0UXvyZGzPEkKHmZjHZGoFtJ3Asf911c6UOU83LAMSZwJ9 F7FmfEOA==;
Received: from [172.56.54.76] (port=31719 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from <touch@strayalpha.com>) id 1uo45K-0000000EjRX-0hn4; Mon, 18 Aug 2025 13:55:54 -0400
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: BCP 78 policy / copyright / Generative AI / LLM .. is there a FAQ?
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <aKNapPeW6Q30nLfP@anton.sobornost.net>
Date: Mon, 18 Aug 2025 10:55:41 -0700
Message-Id: <C1346079-24EA-4523-8C6C-2ABB2E9D2003@strayalpha.com>
References: <aKNapPeW6Q30nLfP@anton.sobornost.net>
To: Job Snijders <job@sobornost.net>
X-Mailer: iPhone Mail (22G90)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
X-Rspamd-Queue-Id: 1uo45K-0000000EjRX-0hn4
Message-ID-Hash: M64DTETB4NSUEUV2ST4P5CF5ALKNB4C3
X-Message-ID-Hash: M64DTETB4NSUEUV2ST4P5CF5ALKNB4C3
X-MailFrom: touch@strayalpha.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: Colin Perkins <csp@csperkins.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/3ToBWsqDWdz1AiaeYKhAR0p_kpo>
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 Aug 18, 2025, at 9:54 AM, Job Snijders <job@sobornost.net> wrote:
> 
>> Or, in response to such generated drafts, why wouldn’t I just ask AI
>> to generate a 5GB “expert” review of such documents?
> 
> Such a strategy seems problematic, it there might be unintended negative
> consequences such as people leaving working groups because the stream of
> information became unmanagable.

No, that’s an INTENDED consequence. 

I see these uses of AI as DOS attack; a counterattack seems appropriate. 

Or at least that’s what Chat-gpt suggested :-)

Joe

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