Re: List moderator action

S Moonesamy <sm+ietf@elandsys.com> Tue, 05 May 2026 19:24 UTC

Return-Path: <sm@elandsys.com>
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 52384E9774C4 for <ietf@mail2.ietf.org>; Tue, 5 May 2026 12:24:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778009086; bh=5/KfzX1SutgSC5glseWXdnjCKnP6dtDc1qkyj906SGI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=aJy1YmxPRjuWvpmzIjCHf5ATRq6Z2ulQWPnGi9S+Jun4062DZJTw4Eo+nhFGPTsj0 LRAcB3c4KZEz1WiibOPFkoMy+4qbHU+qcqWNCM3BJs1vdF4CHRjY8rny2QgK9LbTG8 D9LKRAVSXfPwt0lCkJnCN/ooLzJ9ziqXpVBFQbyw=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
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 pIZkVoc5gQ0q for <ietf@mail2.ietf.org>; Tue, 5 May 2026 12:24:41 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mail2.ietf.org (Postfix) with ESMTP id 8966EE9774BD for <ietf@ietf.org>; Tue, 5 May 2026 12:24:41 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.100.115]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 645JNgYd008472 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 May 2026 12:24:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1778009061; x=1778095461; i=@elandsys.com; bh=5/KfzX1SutgSC5glseWXdnjCKnP6dtDc1qkyj906SGI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=tc2R9XP+YYtCI4cSDyJTv7nFZNLM/laxY7fL3ZNXAOf5PB2yXCFgfGA8i/5spMehI YFoIiF8zucmLuJQkcfKWbjaqTMLdEcGCTbzWvNBef4ca/5fbXl0Hl6QXc65yxGMkhZ fahb0g4rpKk5q0+kLA3wcWLbLkqs8K2P6no/YxUM=
Message-Id: <6.2.5.6.2.20260505095407.0f0a1498@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 05 May 2026 12:23:27 -0700
To: Jacob Appelbaum <jacob@appelbaum.net>, Simon Josefsson <simon@josefsson.org>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: List moderator action
In-Reply-To: <093d3cbb-fdfe-4e6e-b8e8-eddec9458ff9@appelbaum.net>
References: <CAChr6Sw9NH=jFrnr+rB2aA7C7N9shgE1gjimQCxMvPW-0vh1HA@mail.gmail.com> <323b0599-475c-47ae-b3b1-beeeb2069eaf@gmail.com> <87cxzbd428.fsf@josefsson.org> <ffe1fea6-852d-427b-bd27-50fd2afbe714@gmail.com> <87a4uew9dl.fsf@josefsson.org> <ef58e1e9-2a3c-42ff-90bc-a181581939c2@lear.ch> <093d3cbb-fdfe-4e6e-b8e8-eddec9458ff9@appelbaum.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: 3MGWRSGERVUW232T25W4UDXQLX4NU3QK
X-Message-ID-Hash: 3MGWRSGERVUW232T25W4UDXQLX4NU3QK
X-MailFrom: sm@elandsys.com
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/c9jXCAviu1KVMW6gCE1oesQIXuA>
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>

Hi Jacob, Simon. All,
>This comes off as pretty Orwellian Eliot. Dan did not ban himself as a
>matter of fact.
>
>Dan appears to be subject to sanction(s) including moderation that has
>blocked a new and valid complaint about a claim of consensus to the tls
>list for around a week. This moderation has a material impact on the
>outcome of the PQ/T security of the TLS protocol during a WGLC. That may
>not be the intention of the moderators but it is an observable result.
>It is only a visible result because Dan had the foresight to email all
>dissenters, the tls list, and the chairs a copy of the complaint.
>Noteworthy is that the tls list has still not received a copy of it from
>Dan directly.
>
>There is obviously a dispute about the overall situation and Dan isn't
>the only person that sees a different perspective as is evidenced by
>Simon's good faith read.
>
>I find Simon's interpretation to be a compelling explanation for what is
>going on, and reasonable people do disagree. I had previously thought
>differently and Simon changed my mind. It all seems so pointless, right?
>Why would Dan pick this hill of all the hills? Well, Simon has found a
>plausible explanation. That doesn't mean he is correct, of course. I
>guess none of us have directly asked Dan?
>
>Simon's most recent question was not included in your reply but it seems
>worth addressing when he asked:
>
>>>Where does it follow from https://www.ietf.org/about/note-well/ 
>>>that IESG statements override BCP9, BCP78 etc? I can't find the 
>>>term 'IESG statement' in any of BCP9, BCP78 etc documents.
>
>It does not appear from the evidence that Simon is alone in his analysis
>of the texts and what I perceive as arguments from authority probably
>won't resolve the issue. Those arguments do however result in people
>being moderated at the precise time that there is a WGLC in the tls
>mailing list.
>
>I concur with Simon, I share his curiosity in the questions that he
>posed, and I would welcome being humbled on the facts. I read Simon as
>being a good faith contributor whose questions are not being addressed
>reasonably.
>
>>He knows what he has to do to participate and chooses not to.
>
>If the goal is to have a just and fair outcome, and not merely a one-
>sided interpretation rule following with casting of blame, I would
>suggest extending some grace about the dispute until it is fully
>resolved one way or another.
>
>It sounds like you've made up your mind and in your mind I understand
>that your perspective is that Dan is "banning himself." That doesn't
>sound like a good faith reading of the intentions of a long standing
>participant's behavior to me. Merely sanctioning someone doesn't change
>Simon's fair reading of the relevant regulations (i.e.: RFC text, BCP
>text, etc.).
>
>Amending the relevant text raised by Simon seems like closing a loophole
>if people generally don't like that read. I understand that a few people
>would like to have a discussion about Simon's reading that focuses on
>why that reading is right or wrong.
>
>This discussion quickly turns into an elephant in the room where the
>entire situation leads to a frustrating tension: if Simon's read were to
>be acknowledged, and if a change of the relevant text attempted, then it
>would indicate that Dan fairly disagrees about the interpretation of the
>regulations as they stand. It would also signal that by changing
>the text for a specific interpretation tomorrow that there would be some
>agreement about what it meant yesterday and what it means for Dan's
>actions today.
>
>That discussion about changing the text could reveal that Dan is wrong
>or that indeed Dan isn't banning himself. That is probably part of why
>that discussion isn't happening as the central theme. It is easier to
>demonize Dan as doing it to himself though, so that is part of what we
>see happening here. It is gross to witness and it is a failure of
>leadership on display for the entire world to see. That is another part
>of the harm raised and it would behoove people to at least simulate some
>empathy with other's views on the matter.
>
>What is the steelman of Dan's perspective and actions, in your eyes, I
>wonder?

I had to look up the meaning of one word in the text which I quoted: 
https://www.merriam-webster.com/slang/steelman

It look me about an hour to read the appeal which was recently filed 
with the Internet Architecture Board.  There is a technical 
objection(s) (in my opinion) which could get lost because of the 
procedural disagreements included in the submission.  There is now a 
disagreement on the interpretation of BCP 78.  The words "IESG 
statement" do not appear in BCP 78 or BCP 79.

There was recently a complaint about a decision taken by a working 
group chair(s) (re. second paragraph which I quoted).  Looking at the 
matter in the best light, I'd say that the complaint was sent to the 
working group mailing list.  I did not receive the complaint from the 
mailing list through.  This could be because of a notice included at 
the bottom of the complaint.  This may be linked to what I wrote in 
the previous paragraph, re. BCP 78.

There is a metaphor mentioned in the quoted text: 
https://www.britannica.com/dictionary/eb/qa/the-elephant-in-the-room 
I am not sure whether it would be something to do with the 
interpretation of BCP 78.  If that is the case, It is unlikely that 
the disagreement is about the interpretation given that the notice 
did not appear in messages which the appellant sent around September 2025 [1].

The words "good faith" are mentioned twice in the text which I 
quoted.  There is a definition of "good faith" at 
https://www.britannica.com/dictionary/good-faith  Whether there is 
good faith or not is a matter of appreciation.

Regards,
S. Moonesamy

1. It's based on information in the IETF records.