Re: Complaint to ADs regarding censorship of dissent

[Paul Wouters <[e-mail]>]

On Mon, Nov 24, 2025 at 6:22 AM D. J. Bernstein <[e-mail]> wrote:

[ message not quoted as it contains as a derivative clause  ]

Dan,

The TLS WG Chairs had cleared your moderation flag at the 30 day mark on
Nov 17 as per RFC 3934.
Your recent message to the tls list was not "censored" (nor moderated).

What happened is that your message was held by mailman for "posting by a
non-list member". This means that the email
address you attempted to use is not subscribed to ANY ietf mailing list,
including the [e-mail] list. The ietf mailman
daemon sent you a message stating this. Based on your long email, you did
not read that message our system sent you,
or your AI auto-responder opt-out handler prevented you from seeing the
message.

It will take a few days due to the Thanksgiving period to figure out the
exact details of what happened, but I assume this
is similar to past messages where you seem to use ephemeral email addresses
to subscribe to different IETF lists, thus not
getting the advantage of the IETF global accept list that allows posting to
all lists even if you are only subscribed to one list.
Somehow, your ephemeral address used for the tls list got unsubscribed -
possibly because it no longer exists on your end,
or because it generated excessive bounces, or perhaps because of a mail
loop with your AI auto responder. I hope to find out
more next week. I have instructed the TLS WG Chairs not to approve the
pending email, so that we do not disturb the current
state for that mail connectivity investigation.

If you wish to post in the meanwhile, you can do what everyone else who
uses the IETF mailing lists does, and properly subscribe
your email address to any list and then post, without using intermediate
ephemeral addresses. You should also disable your
QRsecretary auto-responder if you want to receive informative mailer-daemon
/ mailman messages from the IETF lists.

With the continued use of your derivative clause - your issues might spread
to more mailing lists for you as you get moderated
there too. Again, all of this can simply be avoided by ceasing to use the
misleading and incorrect derivative clause in your emails,
as indicated in the IESG Statement:
https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-derivative-works-rights/


Paul Wouters
Security Area Director for TLS