IETF Logo Mail Archive

Re: List moderator action

Lars Eggert <lars@eggert.org> Thu, 30 April 2026 11:07 UTC

Return-Path: <lars@eggert.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 35B48E67B768 for <ietf@mail2.ietf.org>; Thu, 30 Apr 2026 04:07:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777547221; bh=or075YTzCqCtHRAqRL6mfcU6sFqn++G6VfSL5toLWBE=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=E/mGu8lKSsC6XvLF3QL1GpQZ3P413+Xlr1zE7HOEeptsbsamCkM3uRN7yBYv/K5sd KO8rvYaEwj3LB+lNU5F2VvTtuUDZ7WpMu5njvhlMK+kLQjPOUsdFJAyi9FhA65tp81 OP+UPx97bEplayKLLoiPlaF0ZKtE823fK3gCHcEA=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=eggert.org
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 NP7PEI2qL7U1 for <ietf@mail2.ietf.org>; Thu, 30 Apr 2026 04:07:01 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [89.167.44.90]) (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 7ED2BE67B752 for <ietf@ietf.org>; Thu, 30 Apr 2026 04:07:00 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 666EA5DE9C; Thu, 30 Apr 2026 14:06:52 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eggert.org; s=dkim; t=1777547212; h=from:subject:date:message-id:to:cc:mime-version:content-type: in-reply-to:references; bh=9xH/JMD/ytEstTIpCy/gRznkNEjwgvzARYST1ZKaNzA=; b=Lh5UQ7QYXJFgzcye61Bi1X4noDpdPRd7glgl4uQpFC/ksr0LvPtMK9iDwCK5gxAK/aJxFe p8vi8bixXhVYLRAumBQX79GFzli08nGmH1nx9avAyqInpZfRSxWf7Z/kCpRQokvEHwzBJM jVq7wROtQ6xJIBsyXwdMNQ2G/oYC+XIpYnL0LsrvjAptuCU/r+DXcAoSTTukvjfv0hP+/R 8aK2Vf4o/1Tl0XmwE+V6Phhcf+CG2wg7LdkOZG3kjd2V0s9sz6WcRAI/rVd3P/myDxoSjy MunHmnCtB5A0k9bNHWviLisunxb1+4O5534/Ug9mNZz44XWGepN74QS64huuKA==
Content-Type: multipart/signed; boundary="Apple-Mail=_28573DBB-FCC2-45C1-BA5D-337F6D10C283"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.500.181\))
Subject: Re: List moderator action
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <CAL9Qcx5TVBwUP=3zL=0pSkJCGmmhzyM77qpvWqBeNbUTSTyLiA@mail.gmail.com>
Date: Thu, 30 Apr 2026 14:06:40 +0300
Message-Id: <1BF821A4-F8B1-4DB5-96B9-B48C14BF1227@eggert.org>
References: <CACJ6M160zcRWCVr5_NCEZ8u2_iRcozCXAQsrkM2CDJ1Ms+oH8w@mail.gmail.com> <CACJ6M16wV1eqhmGav2dL5fNvwbLVCcLEW0Bto4m-sPu4D69viw@mail.gmail.com> <CAOnLz-Fv_gVAODftZ+=Wk9SkK0c1-1mg-mMnsHGCiyfVuze+BQ@mail.gmail.com> <c90c28ae-5c23-4e35-ad12-482e080595c0@cs.tcd.ie> <1961492b-4225-f84e-b250-0ce42e4eac8b@foobar.org> <m2y0i6y37k.fsf@ja.int.chopps.org> <87h5out91z.fsf@josefsson.org> <CAL9Qcx5TVBwUP=3zL=0pSkJCGmmhzyM77qpvWqBeNbUTSTyLiA@mail.gmail.com>
To: Tom Beecher <beecher@beecher.cc>
X-Mailer: Apple Mail (2.3864.500.181)
X-Last-TLS-Session-Version: TLSv1.2
Message-ID-Hash: 3Z54VLWG5M3GIDTCESWGQ6RSF6GFSMLP
X-Message-ID-Hash: 3Z54VLWG5M3GIDTCESWGQ6RSF6GFSMLP
X-MailFrom: lars@eggert.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: Simon Josefsson <simon=40josefsson.org@dmarc.ietf.org>, IETF Discussion List <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/UlzZrPwolAqope8tRBF0dYLdyDM>
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>

Hi,

On Apr 29, 2026, at 17:43, Tom Beecher <beecher@beecher.cc> wrote:
>> Section 5.3(c) of RFC 5378 describes how the derivative work license can be withheld through the use of conforming Legend Instructions in the context of the narrow exemptions of Section 3.3. This section does not permit the application of Legend Instructions to any other kind of IETF Contribution.
> No-derivative legend instructions in email contributons are allowed, **in specific contexts**.  

If you read Section 3.3 of RFC 5378 you will find the “specific context” is about documents.

Thanks,
Lars

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