Re: List moderator action

Simon Josefsson <simon@josefsson.org> Mon, 04 May 2026 07:39 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 30D97E89085A for <ietf@mail2.ietf.org>; Mon, 4 May 2026 00:39:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777880366; bh=Z9yrxs/Jwt04x7R9CjdorFpYzUQ3BQMJKlja2mPv/8w=; h=From:To:Cc:Subject:In-Reply-To:References:Date; b=t+ODX/f8MN0gA7NT09y5RXfysvgq9/ttT90d9zji0RYb9cIEhjFuGx08QfV3CHaE7 Sw/gUz1AiBC5Cyn1ePFGEGhM3uyCZTV8188NoT3+YeMVAxxM8HQF4HP879yTu3w9hS 867CM4j+6SKyc+/J2LcnifEBaWPz24uFJK/fKW/U=
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="CoD9g9q3"; dkim=pass (2736-bit key) header.d=josefsson.org header.b="itTgdztf"
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 RGhhLgkTyqBO for <ietf@mail2.ietf.org>; Mon, 4 May 2026 00:39:25 -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 6FB03E890852 for <ietf@ietf.org>; Mon, 4 May 2026 00:39:25 -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=JSDHBUTh5SWg9+jvmkBUDrNF8ifuiK7z/tkVyE3HtX0=; t=1777880364; x=1779089964; b=CoD9g9q3LMnls1lIm/6esFyqw8ycG29+SBlieBzDbLYR+xvUThUC/oRxJycW7UEzEMi2P3/uCyo j+dw1vE2SAw==;
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=JSDHBUTh5SWg9+jvmkBUDrNF8ifuiK7z/tkVyE3HtX0=; t=1777880364; x=1779089964; b=itTgdztfouJCP3YQ5wgPUqgzlHKeRbDvWXnNGWE50gLLp6mUbQ3+fkuxWJxYotyJ++zPgNxilfi qUlv5ZlxcE7Euu0fTxM8RbjxFPYLAA1MqntlSJk++qPV0ofkgGdIu5A7jASPPahiLyhqha4l1X9dH 9JQ20RCOXC20plkK7+wJycnFOqUbYIzn4oMA8pSoHP/WgSpE9B1MRNM/1gawLo8r++DQ/MugO2GpB 3u/6FAjg89lpZIf2uIDCPlWAqeqcFnDAeMywUGiNozBwT8KyCtJYTF+Ov1gdV7dTf+4/We+F7pch7 Nb4EbVIQYtH8bYtwHhtSS+lSNl/7vokAT7X6PwXEOgV9Egda/YFB42ANzvnXasamkFQtl9eNa/axU etSDHMIxQdqfWzCI8MeSU9iB6/vfhS5BThlfQSjkIFE9uxQNXuBsxWmRDrObhb/U/Gr4bqvfV;
Received: from h-178-174-130-130.a498.priv.bahnhof.se ([178.174.130.130]:53914 helo=frallan) 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 1wJntj-0003DB-L3; Mon, 04 May 2026 07:39:23 +0000
From: Simon Josefsson <simon@josefsson.org>
To: Chris Box <chris.box.ietf@gmail.com>
Subject: Re: List moderator action
In-Reply-To: <CACJ6M14ovSBLsawH9r1TVG-vUQHouTrNdpcf5wZjpcmA73A2Mw@mail.gmail.com> (Chris Box's message of "Thu, 30 Apr 2026 17:39:19 +0100")
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> <CACJ6M14ovSBLsawH9r1TVG-vUQHouTrNdpcf5wZjpcmA73A2Mw@mail.gmail.com>
OpenPGP: id=B1D2BD1375BECB784CF4F8C4D73CF638C53C06BE; url=https://josefsson.org/key-20190320.txt
X-Hashcash: 1:23:260504:simon=40josefsson.org@dmarc.ietf.org::HxStvkSgRO6L+KFs:Vg/B
X-Hashcash: 1:23:260504:ietf@ietf.org::DU7bD3/26fyXzjbo:0LmZe
X-Hashcash: 1:23:260504:chris.box.ietf@gmail.com::VB+c5s74PwD86GPw:0tcQr
Date: Mon, 04 May 2026 09:39:24 +0200
Message-ID: <878q9zd3o3.fsf@josefsson.org>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Message-ID-Hash: 2WDRU6NLEXCDFQVWVYZRKKMOK2GSKMHV
X-Message-ID-Hash: 2WDRU6NLEXCDFQVWVYZRKKMOK2GSKMHV
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
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/-VuCkrbxjUwuDN8EbUEIUgQ26us>
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>

Chris Box <chris.box.ietf@gmail.com> writes:

> On Wed, 29 Apr 2026 at 10:23, Simon Josefsson <simon=
> 40josefsson.org@dmarc.ietf.org> wrote:
>
>> The same advice could be given to the policy makers and moderators of
>> this list.  What is the goal of banning DJB from making these posts?
>>
>
> In this case, my goal is to avoid continued disruptive derivative rights
> claims, as defined by IESG Statement on Clarifying Derivative Works Rights
> <https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-derivative-works-rights/>.
> If DJB posts to the list without such a notice then it would be allowed
> through, unless of course a different community-defined line is crossed.
>
>
>> I don't understand what the moderators hope to achieve here.  It seems
>
> weird that the moderator action does not even cite what policy grants
>> them the authority to make their decision.
>>
>
> It's my fault for not being clear about that when acting. Let me try to
> remedy that now.
>
> RFC 3934 <https://www.rfc-editor.org/rfc/rfc3934.html> gives WG chairs the
> ability to restrict posting for 30 days following disruption and warnings.
> IESG Statement on Disruptive Posting
> <https://datatracker.ietf.org/doc/statement-iesg-iesg-statement-on-disruptive-posting-20060217/>
> extends
> the RFC3934 power to administrators of non-WG lists.
> RFC 9245 <https://www.rfc-editor.org/rfc/rfc9245.html> grants the
> moderators administrative authority over the ietf@ietf.org list.
> IESG Statement on Clarifying Derivative Works Rights
> <https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-derivative-works-rights/>
> defines
> which derivative rights claims are disruptive.
>
> I hope that makes it clear?

Thanks for clarifying, Chris.  Maybe something like that could be added
to future decisions?

Yes, it does make it clear to me that you are not acting based on any
moderation process that has been subject to IETF-wide consensus, but
instead act based on an IESG-driven agenda that appears to be about
personal difference to silence opposition to non-hybrid/NIST PQ crypto.

Please think again if banning people from participating in the
standardization process based on the above rationale is a net positive
for the IETF and wider Internet community.

/Simon