[Mod-discuss] Re: disliking (bits of) the draft is not about incompetence or corruption

John C Klensin <john-ietf@jck.com> Tue, 07 October 2025 17:14 UTC

Return-Path: <john-ietf@jck.com>
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 935566EC8976 for <mod-discuss@mail2.ietf.org>; Tue, 7 Oct 2025 10:14:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 jRugSEa7bEli for <mod-discuss@mail2.ietf.org>; Tue, 7 Oct 2025 10:14:44 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by mail2.ietf.org (Postfix) with ESMTP id 00AC56EC8969 for <mod-discuss@ietf.org>; Tue, 7 Oct 2025 10:14:43 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1v6BGq-0005gy-OJ; Tue, 07 Oct 2025 13:14:40 -0400
Date: Tue, 07 Oct 2025 13:14:34 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <mellon@fugue.com>
Message-ID: <171A4C45469C94D0B3CE5FE9@PSB>
In-Reply-To: <460ABFDE-8101-4777-9429-0884B8B25291@fugue.com>
References: <dca99dac-51e8-47ba-8725-1cab6b2f2267@cs.tcd.ie> <caf12bb8-c5d4-46cd-9df6-9c7ec084948e@network-heretics.com> <460ABFDE-8101-4777-9429-0884B8B25291@fugue.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Message-ID-Hash: GPXH6ADWPYMXZC3ORU47YAXDORBNOUYN
X-Message-ID-Hash: GPXH6ADWPYMXZC3ORU47YAXDORBNOUYN
X-MailFrom: john-ietf@jck.com
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; header-match-mod-discuss.ietf.org-7; header-match-mod-discuss.ietf.org-8; header-match-mod-discuss.ietf.org-9; header-match-mod-discuss.ietf.org-10; header-match-mod-discuss.ietf.org-11; header-match-mod-discuss.ietf.org-12; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: mod-discuss@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Mod-discuss] Re: disliking (bits of) the draft is not about incompetence or corruption
List-Id: Discussion list for IETF moderation policies and practices <mod-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mod-discuss/-6SzUD-szi_pO2HVtjWiCy21pBo>
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>

Ted,

I agree with you about censorship but partially because I see the
largest risks as being about people and not about ideas or even how
those ideas are expressed.  Maybe that makes my views different from
those of Stephen, Simon, or Keith; maybe not.  

But I see a distinction between the present situation and the
proposed one that may be important.  I see the IESG as not wanting to
deal with moderation or disruption sorts of problems.  I think that
is rational: they are busy and I think it is a safe guess that no one
signed up to be an AD because managing disruptions (actual or
alleged) was the main reason why they volunteered.  The community's
reaction to the most recent times they have tried to use BCP 83
almost certainly reinforced disinclination to get involved with the
issues.  There has also been some evidence of ADs responding to
complaints about WG chairs favoring some positions or arguments over
others by siding with the chairs because they are not following the
relevant WG closely or making the question of whether action should
be taken about trust rather than content.  And I think we've see the
IAB respond to appeals involving IETF process by essentially saying
that it is the IESG's area of responsibility and they see no reason
to second-guess them.

All of that is, from some perspectives (including mine) fairly
reasonable or at least predictable.  As others, I think including
you, have suggested, that turns the question before this WG into
whether the proposed mechanisms will make things better or worse.  If
the defense against certain types of fears is that the document
forbids the relevant behavior, I think there is a case for "worse"
because it makes it far easier for ADs (or the whole IESG) to say
"there is a moderation team, they are the experts, and we see no
reason to try to second-guess them".   Using censorship as an
example, if, contrary to the document, moderators start sanctioning
people to suppress their ideas, would the IESG reverse that on
appeal?  I certainly hope so.  I would even get optimistic enough to
say "probably".  But there is very real chance of the IESG not
wanting to deal with the question, especially during particularly
busy times.

As another example, suppose someone appears to be behaving, in a
particular WG or on a particular topic, in a fashion consistent with
what we have historically considered troll-like ways.  If someone
then tries to counter that behavior by pointing at them (in a meeting
or online) and saying "you are a troll", doing so often enough would
be disruptive.   In terms of disruption worthy of sanctions, who is
the offender?    If one does not have a clear answer to that question
and confidence that it will be applied consistently no matter who the
actors are (even if one is reasonably well-connected in the IETF and
the other is not), maybe that contributes to an understanding of what
some of us are concerned about.

Finally, I agree with Keith on at least part of this.  He and I may
be looking in different places rather than under the lampposts (or
under different lampposts), but I believe we have already seen
instances of the problems, rather than being able to believe that
problems have never occurred and therefore probably won't.  As far as
solidarity is concerned, I agree with you up to a point, but then
suggest that the easiest was to get solidarity in a group is to be
sure that group is homogeneous wrt views.  In turn, one way to get
that level of homogeneity in a group is to push out everyone with
views that differ from those of the group leadership out by putting
labels on them and then banning or discouraging anyone associated
with those labels.

   john


--On Tuesday, October 7, 2025 15:27 +0200 Ted Lemon
<mellon@fugue.com> wrote:

> I feel like I'm somewhere in the middle of A Fire Upon The Deep or
> something. Sheesh, folks.
> 
> This is not about censorship. Censorship is explicitly forbidden by
> the draft as it is currently written.
> 
> If we really think that things can go bad in the ways that folks
> have described, this is already possible, because we always have to
> trust nomcom and the IESG and the chairs to call consensus fairly.
> We have to trust the IAB appeals path. If the people in these
> positions don't call consensus fairly, and the IAB doesn't call
> them on it, they can pretty much do whatever they want.
> 
> The reason this hasn't already happened is that we don't want it
> to. That is the thing we need to maintain. No amount of
> wordsmithing will substitute for solidarity.
> 
> 
> _______________________________________________
> Mod-discuss mailing list -- mod-discuss@ietf.org
> To unsubscribe send an email to mod-discuss-leave@ietf.org