Re: BCP 78 policy / copyright / Generative AI / LLM .. is there a FAQ?
Simon Josefsson <simon@josefsson.org> Mon, 18 August 2025 17:01 UTC
Return-Path: <simon@josefsson.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 E0EC755820B7 for <ietf@mail2.ietf.org>; Mon, 18 Aug 2025 10:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.401
X-Spam-Level:
X-Spam-Status: No, score=-4.401 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_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=josefsson.org header.b="8xl8KcbJ"; dkim=pass (2736-bit key) header.d=josefsson.org header.b="n8PFXrnN"
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 GobTXK04w3Dw for <ietf@mail2.ietf.org>; Mon, 18 Aug 2025 10:01:09 -0700 (PDT)
Received: from uggla.sjd.se (uggla.sjd.se [IPv6:2001:9b1:8633::107]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id B0A7B55820AD for <ietf@ietf.org>; Mon, 18 Aug 2025 10:01:09 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; q=dns/txt; c=relaxed/relaxed; d=josefsson.org; s=ed2303; h=Content-Type:MIME-Version:Message-ID:Date: References:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=U8F/qHWWC93bd6Q/QRe22pnqY/49hyBkN/Y5/fOCM2A=; t=1755536467; x=1756746067; b=8xl8KcbJDtSKBPuXurPKHtSeEPun8rJU0ZZ/Ro4CXJ4dtSbbtGtQ21HqdpIrN7ynyFwm0QqDyBQ q7F7ilRnCDg==;
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=josefsson.org; s=rsa2303; h=Content-Type:MIME-Version:Message-ID:Date: References:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=U8F/qHWWC93bd6Q/QRe22pnqY/49hyBkN/Y5/fOCM2A=; t=1755536467; x=1756746067; b=n8PFXrnN/c1cH1yQfA4pTwVilqhnOO2aE/H+FZ8Fi+MuRBmR8J6VSbIOub25N9vuuZsHOwTfcNP KFrpqM7p94+HENbPBMm9PuamsE7HWxlxHn8rZi/4AikOfluGGIVXDDvzVwGsR6ANgviXcynvdK38L 933JduuC3WQbqCsEBjvvBYTrSWei+4SBHxaG1DUYDKi7EmOvZb1Qrp/ERE6rltDIq0mC1V3vWD9oK //MqiAC07omtaBmLkFXHB/nQaHS8YGhLF1ppGQlbjZ89c68m+j99e6HxrjMY94liLq/VytdkmSLPO Hi3X14HND6itGLV78iR6gVq/XrD+XBaNSWqv+4XNXEpmpdpvGXm9zmYfAn71wiuf6hFH74FdBr/+b DOtYbu49bxVGLIgfxe8AUduyxr+ocHGdcJ+/7CSPhSy70PVWMQaj08vpoVcZ50AZXxJkbfgjp;
Received: from h-178-174-130-130.a498.priv.bahnhof.se ([178.174.130.130]:38892 helo=kaka) by uggla.sjd.se with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from <simon@josefsson.org>) id 1uo3EG-005rLf-MI; Mon, 18 Aug 2025 17:01:04 +0000
From: Simon Josefsson <simon@josefsson.org>
To: John Levine <johnl@taugh.com>
Subject: Re: BCP 78 policy / copyright / Generative AI / LLM .. is there a FAQ?
In-Reply-To: <20250818163604.19021D83CEA0@ary.qy> (John Levine's message of "18 Aug 2025 12:36:03 -0400")
References: <aKMhl8l1zjs_Q7CX@anton.sobornost.net> <20250818163604.19021D83CEA0@ary.qy>
OpenPGP: id=B1D2BD1375BECB784CF4F8C4D73CF638C53C06BE; url=https://josefsson.org/key-20190320.txt
X-Hashcash: 1:23:250818:ietf@ietf.org::xE78OW+Fu21LIWdM:3RlA
X-Hashcash: 1:23:250818:job@sobornost.net::eZzdF+4j4R9/ga6Q:AitW
X-Hashcash: 1:23:250818:johnl@taugh.com::HiBSDc7/5I0OM9TI:mIkY
Date: Mon, 18 Aug 2025 19:01:00 +0200
Message-ID: <87349owomr.fsf@josefsson.org>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Message-ID-Hash: VE67LI4WEDRCJCX7J5XS2JZJNTMDVMPB
X-Message-ID-Hash: VE67LI4WEDRCJCX7J5XS2JZJNTMDVMPB
X-MailFrom: simon@josefsson.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, job@sobornost.net
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/nXjS681Nb8KmVDkFYU-825kDgXc>
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>
"John Levine" <johnl@taugh.com> writes: > To connect the dots, when you submit an I-D you have to grant all the > rights described in section 5 of BCP78, which says: > > The Contributor is further deemed to have agreed that he/she has > obtained the necessary permissions to enter into such an agreement > from any party that the Contributor reasonably and personally knows > may have rights in the Contribution, including, but not limited to, > the Contributor's sponsor or employer. > > In view of the many ongoing lawsuits against AI companies by people who claim > that the training material for LLMs and in some cases the LLM output have > violated their copyrights, I don't see any way that you could make those > assurances for LLM generated material. How about if you trained your own LLM on existing IETF RFCs only? And/or IETF mailing list discussions? And/or some free software available under permissive license? With a short acknowledgement a'la "This draft contains text written by a LLM trained on all IETF RFCs." (or similar) it seems that it could be argued to pass the above test. Even e-mails are contributions to the IETF, I think, and I suspect plenty of people already use LLMs to "improve" their e-mails, so I think we are already down in this rathole. /Simon
- Re: BCP 78 policy / copyright / Generative AI / L… Colin Perkins
- BCP 78 policy / copyright / Generative AI / LLM .… Job Snijders
- Re: BCP 78 policy / copyright / Generative AI / L… Tobias Fiebig
- Re: BCP 78 policy / copyright / Generative AI / L… Joe Touch
- Re: BCP 78 policy / copyright / Generative AI / L… Job Snijders
- Re: BCP 78 policy / copyright / Generative AI / L… Tobias Fiebig
- Re: BCP 78 policy / copyright / Generative AI / L… Jeffrey Walton
- Re: BCP 78 policy / copyright / Generative AI / L… Joe Touch
- Re: BCP 78 policy / copyright / Generative AI / L… John Levine
- Re: BCP 78 policy / copyright / Generative AI / L… Simon Josefsson
- Re: BCP 78 policy / copyright / Generative AI / L… Michael Richardson
- Re: BCP 78 policy / copyright / Generative AI / L… Job Snijders
- Re: BCP 78 policy / copyright / Generative AI / L… Behcet Sarikaya
- Re: BCP 78 policy / copyright / Generative AI / L… Job Snijders
- Re: BCP 78 policy / copyright / Generative AI / L… John R Levine
- Re: BCP 78 policy / copyright / Generative AI / L… John R Levine
- Re: BCP 78 policy / copyright / Generative AI / L… Michael De Roover
- Re: BCP 78 policy / copyright / Generative AI / L… Jay Daley
- Re: BCP 78 policy / copyright / Generative AI / L… Arturo Servin