Re: [Gendispatch] New Version Notification for draft-ecahc-moderation-00.txt

Mark Nottingham <mnot@mnot.net> Fri, 07 July 2023 01:56 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A96C8C1519BB for <gendispatch@ietfa.amsl.com>; Thu, 6 Jul 2023 18:56:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.287
X-Spam-Level:
X-Spam-Status: No, score=-4.287 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RAZOR2_CF_RANGE_51_100=1.886, RAZOR2_CHECK=0.922, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b="frMlkl4/"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="W3gM+KN7"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k6r6Awch4yqN for <gendispatch@ietfa.amsl.com>; Thu, 6 Jul 2023 18:56:55 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF41CC15109F for <gendispatch@ietf.org>; Thu, 6 Jul 2023 18:56:54 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id E716B5C0068; Thu, 6 Jul 2023 21:56:53 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 06 Jul 2023 21:56:53 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1688695013; x=1688781413; bh=HRJJP31Ow4AsbdBvbwW18LzV+HQ4Em6GlTm 1342rw/I=; b=frMlkl4/712WUz9ARwgqEb3wSO0Gm2/b7ljicDFz9C8meQJE/Ly XEGIUjwrOt/fzrH4jXFBsDhyMZOeIG5fyCwb1AD+i3gz0jUYU3S5fkc4Oi4HimV+ VPr9hAhnnfYr/PCIzZQuPaKa0BSbAgfXLmexTYc/FoPva23dMV7zsPAi8y3r0T6h SUxfY6s1wBpF5+vb3rQXthhrbdcos+xmmR89uh/mXWss4qJsn0K71udfPadYOBB+ ipdJpqMCVr5uV6xIuFn5mfVn3BMYxRS2MN0uzf0trk3Eq3ydsZKzF1aoqoxmM34w 9y3uQwK8w778FWHm8UDP38UwuKkEIokepuQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1688695013; x=1688781413; bh=HRJJP31Ow4AsbdBvbwW18LzV+HQ4Em6GlTm 1342rw/I=; b=W3gM+KN71N+ndtbs52ldhy5kI+QbgLDboorkYDgzfudKHQDOaaf tPA88m6nZ5rT0Jbi4l8adiSNMTFq9WDwMOsOAzuJdzIJC7qnIDeLmTG5HDI5JxIF KJ1IyAmEIMQW4APUYtlv83L/CUPg+nc2sPcUhDIlqIxUUJbGLDTdEIQrhbED4g/D snuGpoDw0SJwr3g0sBUqE275odLX2I0m6B9jPTQP2bZ/bDbPKjdekFXmlsc9usD0 vO1uARpIGQrcKLCgWO6f+wQof0ZnSREmeAwZacKh/WM98iQ8ldhtRxHSloOsoMsm W3UVs+PTnKIeXHkCu8RIz3uYZndQ2blg+UQ==
X-ME-Sender: <xms:5XCnZGTvNoFH3F4Q-aUDKFwLuebT5x0wUFcxdpKGYtFj0X_FXddfPQ> <xme:5XCnZLzhnQ8B_Fd_91s7_VjuQpavgYmvz44BU-IAp36G4KpV97fqC-GqqzXogjBRY PeYI6GvxqKfgwqVwQ>
X-ME-Received: <xmr:5XCnZD1duJeCLq0YOhs34DYD9KbErIr5L7MM8iJ8Ou2EsSW6DKUcZM8DatorHeyzJdF2fh3O25N0N0CzR5RdV48smCA8omFUa5u5pENNwZVNrzMTcSuJUeQ2>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrvddtgdehtdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurheptggguffhjgffvefgkfhfvffosehtqh hmtdhhtddvnecuhfhrohhmpeforghrkhcupfhothhtihhnghhhrghmuceomhhnohhtsehm nhhothdrnhgvtheqnecuggftrfgrthhtvghrnheptddtgefgueevtddugfdtkeffudegve etffegjeelhfdvtedvueejteegueegteetnecuffhomhgrihhnpehmnhhothdrnhgvthen ucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhoth esmhhnohhtrdhnvght
X-ME-Proxy: <xmx:5XCnZCDtY1yrL2h-E747nOLtSyRlEkUWW24G49cWVv8enlPtLiJVKQ> <xmx:5XCnZPh6WrMUz3bYp2N09jSsZ3OEf0eOYUX87OrEcalF5JWcFl5aqw> <xmx:5XCnZOrHh5U_i7nIDh31Wu7_lDNkmk_r5ryu_DhRD7bD_zpLx8RBFA> <xmx:5XCnZPIEy5XcIUuzSGVoqIGhuI4DLX0olJ9RK5CP2xRGnjAt6k0gCw>
Feedback-ID: ie6694242:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 6 Jul 2023 21:56:52 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CABcZeBMxq0BCMqTZ49BB=W+ka1X1uLxd5HjcfKmeQ5i3TZWWFw@mail.gmail.com>
Date: Fri, 07 Jul 2023 11:56:49 +1000
Cc: Eric Rescorla <ekr@rtfm.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F5DB78AB-A5D8-408A-956D-8599DD6B9641@mnot.net>
References: <168866528948.9864.11683631235677115587@ietfa.amsl.com> <C923D27E-85C3-4E57-A7D1-7850F0D82703@eggert.org> <F588647C-A9E1-40EF-8F7A-648221C5FAA3@akamai.com> <CABcZeBMxq0BCMqTZ49BB=W+ka1X1uLxd5HjcfKmeQ5i3TZWWFw@mail.gmail.com>
To: "gendispatch@ietf.org" <gendispatch@ietf.org>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/jH0HvkgXwvCdX-JJ4K_AW5HaI4M>
Subject: Re: [Gendispatch] New Version Notification for draft-ecahc-moderation-00.txt
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2023 01:56:59 -0000

Piggybacking additional feedback on EKR's because I agree with much^H^H^H^Hall of it.

> On 7 Jul 2023, at 6:04 am, Eric Rescorla <ekr@rtfm.com> wrote:
[...]
> In my experience one of the things that makes moderation difficult
> is when each moderation decision is itself subject to extensive
> debate in the same venue as it is happening. This constitutes a
> DoS on the venue as well as discouraging strong moderation. I
> think it would be good to establish a separate venue for debating
> moderation discussions (e.g., an issue tracker or something)
> that is distinct from the lists being moderated. This will allow
> for public debate where necessary but not subject everyone else to it.

This is a very good suggestion, provided that we very firmly move that discussion there. I'm not sure folks have the discipline.

> S 4.1.
>    The moderator team SHALL operate according to a consistent and
>    uniform set of criteria, processes, and actions.  The moderator team
>    SHALL independently define and execute their role.  They SHALL
>    maintain a public set of moderation criteria, processes, actions, and
>    other material that allows the community to understand and comment on
>    the role of the team.  The moderator team SHOULD consider adopting
>    moderation criteria, processes, and actions that other technical
>    communities have found suitable.  The moderator team's criteria and
>    processes SHALL be developed with community input, but they are not
>    expected to be documented in the RFC series.
> 
> So these do not require approval of IAB or IESG?

This is perhaps the most important point. In the past, there have been very strong disagreements about moderation, and questioning of legitimacy of particular actions within the IETF process. Allowing the moderators to 'define [...] their role' and 'adopt moderation criteria' outside of the IETF consensus process opens up a number of questions about how that works, whether the output is legitimate in the eyes of the community, etc. 

> Maybe I'm missing it, but it's not clear to me what the *powers*
> of moderators are. For instance, can they ban someoen entirely
> from a list? From an IETF list? It just seems to say "moderation
> actions". FWIW my view is they should have quite broad powers.

Yes. It'd also be helpful if this draft listed the RFCs the authors believe will be updated or obsoleted if it is published.

> S 4.4.
>    Due to the global nature of the IETF, the membership of this team
>    SHOULD reflect a diversity of time zones and other participant
>    characteristics that lets it operate effectively around the clock and
>    throughout the year.  Team diversity is also important to ensure any
>    participant observing problematic behavior can identify a moderator
>    they feel comfortable contacting.
> 
> This seems to implicitly assume a very high level of responsiveness
> (24x7). I'm not sure that's necessary but if you think it is, then
> you should say so.

If WG chairs lose the ability to moderate (which I know is an open question), handling an issue through a moderator team is going to inevitably add latency. So I think it is necessary -- IME it's much more effective if bad behaviour is caught and stopped early.

To that question of whether WG chairs should still be able to moderate -- I'm not sure, but I observe very different behaviour in different WGs. What passes in some WGs as normal debate would be flagged by chairs as disruptive. Will moderators appreciate these differences, or set a new level for some WGs? And what will that level be?

Whether or not WG chairs still have the ability to moderate, it'd be good to understand what the expected interactions between chairs and moderators would be. E.g., will moderators check in with chairs on a proposed resolution, to get context and assure that it will work in that community? If chairs retain the ability to moderate, do they need to inform moderators when they act? Etc.

Finally, an editorial nit: I found Section very difficult to read, in part due to the liberal sprinkling of references throughout the text. It might help to move references to the end of the applicable sentence, where possible.

Cheers,



--
Mark Nottingham   https://www.mnot.net/