Re: Complaint to ADs regarding censorship of dissent

"D. J. Bernstein" <djb@cr.yp.to> Tue, 25 November 2025 10:33 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 A136E9022A0D for <ietf@mail2.ietf.org>; Tue, 25 Nov 2025 02:33:53 -0800 (PST)
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=unavailable 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 UTseb2dBYsA5 for <ietf@mail2.ietf.org>; Tue, 25 Nov 2025 02:33:53 -0800 (PST)
Received: from salsa.cs.uic.edu (salsa.cs.uic.edu [131.193.32.108]) by mail2.ietf.org (Postfix) with SMTP id 258BB9022A01 for <ietf@ietf.org>; Tue, 25 Nov 2025 02:33:53 -0800 (PST)
Received: (qmail 3768331 invoked by uid 1010); 25 Nov 2025 10:33:52 -0000
Received: from unknown (unknown) by unknown with QMTP; 25 Nov 2025 10:33:52 -0000
Received: (qmail 280755 invoked by uid 1000); 25 Nov 2025 10:33:41 -0000
Date: Tue, 25 Nov 2025 10:33:41 -0000
Message-ID: <20251125103341.280753.qmail@cr.yp.to>
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, sec-ads@ietf.org
Mail-Followup-To: ietf@ietf.org, sec-ads@ietf.org
Subject: Re: Complaint to ADs regarding censorship of dissent
In-Reply-To: <87wm3ebitx.fsf@josefsson.org>
Message-ID-Hash: RWHBGIGPPSO2GHCFLYINKII2VG76E3QJ
X-Message-ID-Hash: RWHBGIGPPSO2GHCFLYINKII2VG76E3QJ
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
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/uYUtz4SV_pM12qECXbT_j5UV_QQ>
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>

Simon Josefsson writes:
> Are the subscriber e-mail addresses for IETF lists publicly available?

I agree that IETF management generally shouldn't be leaking information
about subscription addresses, and I agree that it's an error to conflate
the _subscription_ question with transparency regarding who's _posting_.

However, I don't think this matters for the specific case here. I had
already publicly noted in another context that I joined the TLS mailing
list in 1999.

The current sideshow about subscription addresses is much more of a
problem in how it leads casual readers to believe, falsely, that I was
posting the message from an address I hadn't registered. This deflects
from the (still unreleased) logs of how the address "got unsubscribed".

---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. Legend language
also appears in, e.g., RFC 5831. For further background on the relevant
IETF rules, see https://cr.yp.to/2025/20251024-rules.pdf.)