[Mod-discuss] Re: one last issue from my side

John C Klensin <john-ietf@jck.com> Wed, 10 September 2025 18: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 696A16092FB4; Wed, 10 Sep 2025 11:14:06 -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 SfnJKXg45Jv9; Wed, 10 Sep 2025 11:14:05 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by mail2.ietf.org (Postfix) with ESMTP id 1D4BA6092F92; Wed, 10 Sep 2025 11:14:05 -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 1uwPKM-0003dk-I5; Wed, 10 Sep 2025 14:13:54 -0400
Date: Wed, 10 Sep 2025 14:13:48 -0400
From: John C Klensin <john-ietf@jck.com>
To: Eliot Lear <lear@lear.ch>, "Rob Wilton (rwilton)" <rwilton=40cisco.com@dmarc.ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, mod-discuss@ietf.org
Message-ID: <03F92E30336D9F306D563770@PSB>
In-Reply-To: <e466d443-bc26-4db5-a0ed-b626142eff1b@lear.ch>
References: <bccb0bda-ea90-40ba-a2c9-520c226a6b4e@lear.ch> <695b2282-61b6-450c-88df-d1fcc57c2af7@gmail.com> <AB78D433E641F572043EC9AC@PSB> <LV8PR11MB853677C18B823A783F741999B50EA@LV8PR11MB8536.namprd11.prod.outlook.com> <e466d443-bc26-4db5-a0ed-b626142eff1b@lear.ch>
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: 2H5B6GLF2ZHDPTY3V5GZTDQP3XF5HYSD
X-Message-ID-Hash: 2H5B6GLF2ZHDPTY3V5GZTDQP3XF5HYSD
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; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Mod-discuss] Re: one last issue from my side
List-Id: Discussion list for IETF moderation policies and practices <mod-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mod-discuss/V-Kf6uE3HVI20GiKcPi_8k-GNBY>
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>


--On Wednesday, September 10, 2025 17:13 +0100 Eliot Lear
<lear@lear.ch> wrote:

> I am not entirely sure we can get three, fwiw.

Eliot, 

I don't think I'm ready to advocate, much less try to insist, that we
write this into the document but, if we can't get five, or even
three, people who not only volunteer but have the right set of
motives, skills, etc. (see forthcoming note and some of my earlier
ones), I think it should be grounds for pulling the plug on this
model and going back to the drawing board.

Indeed, if we are very uncertain that it is possible to get enough
people on the moderation team to make the other specifications of the
document feasible, maybe we should be trying to advance the document
as Experimental, with the IESG (or some other mechanism) required to
determine the experiment was unsuccessful and figure out whether
going back to a (probably rechartered) WG or deciding to leave the
status quo alone for a few years being the next decision.

What I think would be really unfortunate and scary for the IETF would
be to move ahead with something that clearly wasn't working --with
inability to get even three good volunteers being about as clear as
one could get-- simply because this WG put in all of these months of
arguing and then published a BCP which has to be followed because it
is there, working or not.

   john