[Mod-discuss] Broad consensus

"D. J. Bernstein" <djb@cr.yp.to> Tue, 02 September 2025 08:15 UTC

Return-Path: <djb-dsn2-1406711340.7506@cr.yp.to>
X-Original-To: mod-discuss@mail2.ietf.org
Delivered-To: mod-discuss@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id D697F5C01842 for <mod-discuss@mail2.ietf.org>; Tue, 2 Sep 2025 01:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 c4WwX9MPCNUo for <mod-discuss@mail2.ietf.org>; Tue, 2 Sep 2025 01:15:20 -0700 (PDT)
Received: from salsa.cs.uic.edu (salsa.cs.uic.edu [131.193.32.108]) by mail2.ietf.org (Postfix) with SMTP id 422625C01836 for <mod-discuss@ietf.org>; Tue, 2 Sep 2025 01:15:20 -0700 (PDT)
Received: (qmail 968921 invoked by uid 1010); 2 Sep 2025 08:15:19 -0000
Received: from unknown (unknown) by unknown with QMTP; 2 Sep 2025 08:15:19 -0000
Received: (qmail 468426 invoked by uid 1000); 2 Sep 2025 08:15:10 -0000
Date: Tue, 02 Sep 2025 08:15:10 -0000
Message-ID: <20250902081510.468424.qmail@cr.yp.to>
From: "D. J. Bernstein" <djb@cr.yp.to>
To: mod-discuss@ietf.org
Mail-Followup-To: mod-discuss@ietf.org
In-Reply-To: <68645cd8-151e-420e-9641-3ca2c83d1c6b@cs.tcd.ie>
Message-ID-Hash: 2RDXCC7TDOJ7WSAIOX5LGCJXF3A6MRXA
X-Message-ID-Hash: 2RDXCC7TDOJ7WSAIOX5LGCJXF3A6MRXA
X-MailFrom: djb-dsn2-1406711340.7506@cr.yp.to
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mod-discuss.ietf.org-0; header-match-mod-discuss.ietf.org-1; header-match-mod-discuss.ietf.org-2; header-match-mod-discuss.ietf.org-3; header-match-mod-discuss.ietf.org-4; header-match-mod-discuss.ietf.org-5; header-match-mod-discuss.ietf.org-6; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Mod-discuss] Broad consensus
List-Id: Discussion list for IETF moderation policies and practices <mod-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mod-discuss/NMDOQiNYstKzTrtr3hYQs5e_14s>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mod-discuss>
List-Help: <mailto:mod-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:mod-discuss-owner@ietf.org>
List-Post: <mailto:mod-discuss@ietf.org>
List-Subscribe: <mailto:mod-discuss-join@ietf.org>
List-Unsubscribe: <mailto:mod-discuss-leave@ietf.org>

Stephen Farrell writes:
> On 29/08/2025 20:40, D. J. Bernstein wrote:
> > Is it so hard to understand how error-prone this process is?
> That IMO is a fair point.
  [ ... ]
> I hope the AD and IESG try do something about that, e.g. to
> include a plenary presentation/discussion on this topic before
> the end of IETF LC.

Let me point out a very easy way to see why that's inadequate:

    * https://www.ietf.org/blog/ietf-llc-statement-competition-law-issues/
      includes the following statement: "IETF activities are conducted
      with extreme transparency, in public forums. Decision-making
      requires achieving broad consensus via these public processes."

    * IETF Last Call is a broad process, but not a consensus process.
      Decisions are made by a small group, IESG. Last Call is just
      inviting everyone to provide input to IESG; it isn't requiring
      decisions to achieve IETF-wide consensus.

    * The only consensus process is within the WG. But the MODPOD WG is
      tiny, so even a _unanimous_ decision within the WG wouldn't be
      "broad consensus".

I conclude that the chairs are obliged to reach out to broaden the WG
membership before allowing any WG decisions.

I imagine that IETF-wide email from the chairs as follows would help
broaden membership: "The MODPOD charter says, in short, that MODPOD's
goal is to resolve inconsistencies in current procedures. However,
MODPOD's current draft actually creates new censorship powers, such as
adding five new IETF-wide censors, removing RFC 3934's requirement of
prior warnings, and adding a new list of content-based categories of
material that the censors are authorized to selectively ban. We know
censorship can be controversial. As chairs, we would like to broaden WG
participation to make sure that there is a balance of interests before
any WG decisions are made."

---D. J. Bernstein