Re: Complaint to IAB regarding IESG decisions

"D. J. Bernstein" <djb@cr.yp.to> Sat, 01 November 2025 11:36 UTC

Return-Path: <djb-dsn2-1406711340.7506@cr.yp.to>
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 E43067FF62EC for <ietf@mail2.ietf.org>; Sat, 1 Nov 2025 04:36:45 -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 EqbYztdTDCGM for <ietf@mail2.ietf.org>; Sat, 1 Nov 2025 04:36:45 -0700 (PDT)
Received: from salsa.cs.uic.edu (salsa.cs.uic.edu [131.193.32.108]) by mail2.ietf.org (Postfix) with SMTP id 61D727FF62E4 for <ietf@ietf.org>; Sat, 1 Nov 2025 04:36:45 -0700 (PDT)
Received: (qmail 3013123 invoked by uid 1010); 1 Nov 2025 11:36:44 -0000
Received: from unknown (unknown) by unknown with QMTP; 1 Nov 2025 11:36:44 -0000
Received: (qmail 1682617 invoked by uid 1000); 1 Nov 2025 11:36:32 -0000
Date: Sat, 01 Nov 2025 11:36:32 -0000
Message-ID: <20251101113632.1682615.qmail@cr.yp.to>
From: "D. J. Bernstein" <djb@cr.yp.to>
To: iab@iab.org
Mail-Followup-To: iab@iab.org, ietf@ietf.org
Subject: Re: Complaint to IAB regarding IESG decisions
In-Reply-To: <20251024132051.1114397.qmail@cr.yp.to>
Message-ID-Hash: TF4Z3ZRUICDBCVQTRDJ3C2Y5EWABWLBA
X-Message-ID-Hash: TF4Z3ZRUICDBCVQTRDJ3C2Y5EWABWLBA
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-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/LlsaxP4RzUOsmQxQElw6N92RssY>
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>

Dear IAB, cc'ing ietf@ietf.org for transparency:

My filing https://cr.yp.to/2025/20251024-rules.pdf included a list of
five requested IAB actions. The fourth action had two parts, where the
first part ("please reverse IESG's decision to violate this") has now
been overtaken by events, so I am no longer asking IAB for that part. To
be clear, the second part of the fourth request remains applicable, as
do the first, second, third, and fifth requests.

Concretely, on 1 November 2025, IESG finally instructed the AD to
address the underlying consensus question. However, IESG has not revoked
its decisions regarding transparency, regarding multiple-AD obligations,
regarding the BCP 9 complaint chain, regarding the BCP 78 rules, or
regarding the procedural question of whether an "Informational" RFC such
as RFC 3710 can override a seeming IETF policy such as RFC 2026.

A few added notes seem warranted regarding BCP 78. IESG continues to
misrepresent BCP 78, and has issued a renewed threat to disregard any
future appeals that invoke the BCP 78 opt-out procedure. The IETF
"moderators", citing IESG's recent dictates on the topic, claimed that
my invocation of the BCP 78 opt-out procedure was "disruptive behavior",
and they threatened a list ban if I did it again. As far as I can tell,
neither IESG nor the IETF "moderators" have any authority to issue a ban
on this basis. I asked the "moderators" on 25 October 2025 (off list) to
publicly quote and answer the following questions:

    (1) "What exactly do you claim this opt-out provision is
        disrupting?"

    (2) "Why exactly do you believe that you and/or IESG have authority
        under IETF policy to threaten a ban in response to opt-out
        provisions?"

    (3) "RFC 9245 specifies what's inappropriate for the IETF mailing
        list. RFC 9245 doesn't authorize you to take action in other
        cases. Are you claiming that the opt-out provision is 'unrelated
        to IETF policy'?"

On 29 October 2025 (off list), the IETF "moderators" refused to answer.
The threatened ban by the "moderators" is not currently the subject of
an appeal to IAB, but it is an example of the continuing importance of
the IESG decisions that I have appealed to IAB.

Please let me know if you have any questions.

---D. J. Bernstein


===== NOTICES =====

This document may not be modified, and derivative works of it may not be
created, and it may not be published except as an Internet-Draft. (That
sentence is the official language from IETF's "Legend Instructions" for
the situation that "the Contributor does not wish to allow modifications
nor to allow publication as an RFC". I'm fine with redistribution of
copies of this document; the issue is with modification.)