[Mod-discuss] Re: Keith Moore's response to WGLC (was Re: WG Last call for draft-ietf-modpod-group-processes-10)

Eliot Lear <lear@lear.ch> Wed, 17 September 2025 05:24 UTC

Return-Path: <lear@lear.ch>
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 6E4CD640A946; Tue, 16 Sep 2025 22:24:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -0.89
X-Spam-Level:
X-Spam-Status: No, score=-0.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01] 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=lear.ch
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 kd6PP3R1ISMH; Tue, 16 Sep 2025 22:24:26 -0700 (PDT)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [IPv6:2a00:bd80:aa::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id CD9FC640A937; Tue, 16 Sep 2025 22:24:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1758086662; bh=L+ZXbfJaMGGdcuY+55/tAqqzujo+1HlWRjDhmrJJ5+Q=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=f8cF+9FvQOPy1WaXCOkccg4ZHvf5pSELYfuFsduWcmeeQ0V+YLpxGwdYlypp4ocX0 S3NxcOkRzRoJz35v4ZaQ1GS17Q4k2qyVKNmSt/zk/zo8ogMgIXPeeGHg0kUy/unL2x /oz/1SULjHRCRPyj8aLNDUkhJg53qFcr5Gz2UjtQ=
Received: from [IPV6:2a02:1210:2c9b:e200:d942:ed6e:a011:4c7a] (0.1.2.1.2.0.a.2.dynamic.cust.swisscom.net [IPv6:2a02:1210:2c9b:e200:d942:ed6e:a011:4c7a] (may be forged)) (authenticated bits=0) by upstairs.ofcourseimright.com (8.18.1/8.18.1/Debian-2) with ESMTPSA id 58H5OJxe3090415 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Wed, 17 Sep 2025 07:24:22 +0200
Message-ID: <337eed33-67b8-46da-90f9-6c006700e9c8@lear.ch>
Date: Wed, 17 Sep 2025 07:24:19 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: John C Klensin <john-ietf@jck.com>, Pete Resnick <resnick=40episteme.net@dmarc.ietf.org>
References: <CAEi+uC7gCEjLzc3_KZL6Mq_FFgvUL8pL5rD-PXaoYr5eR7Ky1g@mail. gmail.com> <7b92e1a2-c480-4274-9af0-be0a36a5259e@network-heretics.com> <87plbw7iq3.fsf@josefsson.org> <5273C1E0-43BD-44C4-9B10-11DF68B7853D@episteme.net> <874it5wdu6.fsf@josefsson.org> <082230DC-347D-4D19-9E6C-99FD3803BBB5@episteme.net> <6CB797C77BD3448B129C6144@PSB> <B8AC7173-0E78-4665-B8C8-FF1E237FEE76@episteme.net> <E5C9DA668FFD091C84710BCD@PSB> <90209b4f-e19d-489c-adb6-154a69ea8a0a@lear.ch> <3AF4FB44B6B519B13BF6F793@PSB>
Content-Language: en-US
From: Eliot Lear <lear@lear.ch>
Autocrypt: addr=lear@lear.ch; keydata= xsBNBFMe1UQBCADdYOS5APDpIpF2ohAxB+nxg1GpAYr8iKwGIb86Wp9NkK5+QwbW9H035clT lpVLciExtN8E3MCTPOIm7aITPlruixAVwlBY3g7U9eRppSw9O2H/7bie2GOnYxqmsw4v1yNZ 9NcMLlD8raY0UcQ5r698c8JD4xUTLqybZXaK2sPeJkxzT+IwupRSQ+vXEvFFGhERQ88zo5Ca Sa1Gw/Rv54oH0Dq2XYkO41rhxQ60BKZLZuQK1d9+1y3I+An3AJeD3AA31fJZD3H8YRKOBgqe ILPILbw1mM7gCtCjfvFCt6AFCwEsjITGx55ceoQ+t5B5XGYJEppMWsIFrwZsfbL+gP31ABEB AAHNGUVsaW90IExlYXIgPGxlYXJAbGVhci5jaD7CwI4EEwECADgCGwMCHgECF4AWIQSY0L2Q Rh2wkqeyYR2HtmtG2dJ6MwUCWxJwMwULCQgHAgYVCAkKCwIEFgIDAQAKCRCHtmtG2dJ6M8KI B/46pFrJX+4Ockl2fHR303ais9Lyx8jv6mXKKOr8WR0UYcJ0syQrhaaZNG1VV98tYQHHK9F5 y7hH4YCsrr3odZ6zoavnx5X1X/2xw8y732f/irVoOOkYLid9IGPxa2e2nYXCZpde5/yvv3we XVE4mG4dEAD5T8iKS4Hz/3fKGJQ15o79Jv92HgC7RpCt0WaiQ0b6acP3PuwjDJzJzLFZzb7j IiB3izxQESSWE1GNRmoAK/k0gW6kmx1/87tQENrK+3Nn4CJSFQWF6entLnY7UeVm95wbMQkJ evwddDWUO2huDbmZnmxgKXGzSSpuNq7n8ICAOlbt0HfdJAZQfy25bwvezsBNBFMe1UQBCAC0 WV7Ydbv95xYGPhthTdChBIpPtl7JPCV/c6/3iEmvjpfGuFNaK4Macj9le20EA5A1BH7PgLGo HOiPM65NysRpZ96RRVX3TNfLmhGMFr5hPOGNdq+xcGHVutmwPV9U7bKeUNRiPFx3YdEkExdd qV2E8FltT0x2FSKe2xszPPHB6gVtMckX5buI9p1K3fbVhXdvEkcYY/jB0JEJGyhS5aEbct5c HUvDAkT81/YFK5Jfg8RRwu1q1t1YuIJSOWAZQ9J9oUsg6D9RpClU+tIFBoe3iTp1AUfJcypu cGKgLYKtpu/aygcpQONHYkYW5003mPsrajFhReVF5veycMbHs4u5ABEBAAHCwF8EGAECAAkF AlMe1UQCGwwACgkQh7ZrRtnSejOSuQgA27p2rYB7Kh20dym6V8c62pWpBHHTgxr/32zevxHS iXl6xvUCg5T8WUwfUk8OvgDcBErK/blDAMXQzSg3sp450JhR8RnXHXF5Zz2T04X7HnlIVJGw f2CjnwyEAJCqMzaCmI+g3Imvg/8L4nyBFvhlFHDv+kIvMiujyycjPAu7xxKplBs1/IEwmDoA MjneFmawvfeQnwdMhSKK8PjKSuzGU5uUmxj3GBfRqvTM0qpmhMPFOmDhJSmH55HLAky2Mlmq JYXJPt/9EfSEhFiua1M6gLiuNEuPkp+8jcnHQqKr0IeHt8UqcwLt2mGfIyl0FVdF9hvWPjNR zGbgqoT1Di03RQ==
In-Reply-To: <3AF4FB44B6B519B13BF6F793@PSB>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------cV5O8WpVfNgGRqqsBydg4jT3"
Message-ID-Hash: 7G3N63NSM2NGCMDLSRUPCNVXT3PEK4MJ
X-Message-ID-Hash: 7G3N63NSM2NGCMDLSRUPCNVXT3PEK4MJ
X-MailFrom: lear@lear.ch
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; 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: Keith Moore's response to WGLC (was Re: WG Last call for draft-ietf-modpod-group-processes-10)
List-Id: Discussion list for IETF moderation policies and practices <mod-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mod-discuss/5GWnd1bn7edqu5jrXeYsgo59Dd8>
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>

Hi John,

On 17.09.2025 01:16, John C Klensin wrote:
> I am assuming, as the document seems to me to assume (and as I
> believe for other reasons), that suspensions (including RFC 3683-like
> Posting Rights actions) are the most serious moderation actions the
> IETF can take.  So I am suggesting, for moderation decisions that
> include suspensions (no change to anything else)...
>
>   * For a suspension made by a moderation team member, review
> 	by the team either before the action takes effect or, if
> 	there is an emergency, review by the team within a reasonable
> 	period thereafter.    I hope we don't need to specify either
> 	a definition for "reasonable", how the team does that review,
> 	etc.  I don't expect it to happen often, but that review
> 	could result in a change to the decision.
> 	
>   * For a suspension made by a WG Chair or other Administrator,
> 	I note that the document (Section 3, paragraph 4) already
> 	requires them to "address reports of inappropriate behavior
> 	in a timely fashion, apprising moderators of their
> 	disposition".  Once apprised of a suspension-type action, the
> 	moderation team will conduct a review, also in a timely
> 	fashion, and make recommendations to the Administrator as
> 	appropriate.  For other actions, the moderation team should
> 	do such a review if requested by either the Administrator or
> 	the Offender/ Subject of the action... again, purely to
> 	advise the Administrator.  Of course, if there is a severe
> 	disagreement between the Administrator and the Moderation
> 	Team, the appeals procedure could be exercised.
> 	
>   * In addition, if an appeal occurs, the AD or IESG MAY ask
> 	the moderation team to review the situation and offer advice.
> 	That advice would, again, not be binding on anyone, but, if
> 	the moderation team produced a report that was generally
> 	perceived as fair, it could help minimize IESG workload for
> 	the appeal.

We already have text that requires administrators to inform both the AD 
and the moderation team on the disposition of complaints. I think what 
you're asking for is additional review by the moderation team.  That's 
possible with the existing text but not required.  Because suspension is 
a pretty serious thing, I agree that we could add some text that says 
something like, "the moderation team should review all suspensions and 
bans".

?

Eliot


> In addition to removing the ambiguity that I (and maybe Simon and
> others) see in the current text, this reduces the chances of anyone
> -- individual moderator, WG Chair or other Administrator, or even an
> AD -- operating in a King-like fashion without really being aware of
> it and with only a heavyweight appeals procedure as a remedy.
>
> best,
>      john
>
>