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

Lars Eggert <lars@eggert.org> Fri, 08 September 2023 12:09 UTC

Return-Path: <lars@eggert.org>
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 920E7C14CE39 for <gendispatch@ietfa.amsl.com>; Fri, 8 Sep 2023 05:09:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=eggert.org
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 DeZnPssWr4qF for <gendispatch@ietfa.amsl.com>; Fri, 8 Sep 2023 05:09:43 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 887A2C151062 for <gendispatch@ietf.org>; Fri, 8 Sep 2023 05:09:43 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 451368086B; Fri, 8 Sep 2023 15:09:40 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eggert.org; s=dkim; t=1694174981; h=from:subject:date:message-id:to:cc:mime-version:content-type: in-reply-to:references; bh=Lu9V0MM0did61QKaLEB4sNtLrNa6DD09bmuBWfbPaEY=; b=UbHpbSLQCz4xyCahDTyAcpTir0bAz3p/xgF70Qsz1fjY1me5pL24fMnA/h6TmgTTbckdIr WyUBceNUZQN7OW6s3/2RVxSbcCmitNu8etC2y1fBx503h+PpIp65HB4cwjv1OgCJXQgVgF 0nJbG1TeGRFPvwWhewl3mrUtVQUMI96kQMcxKiCcJHJ1lBvTebKgDH7NqseIqQmYlNV/vc 4qSaI9F7sTBoYK5FGo3Op9gZeV41A/90MRceIORdsW3yfRKZS+LlZXIz1Ju3B8jHt5yNdt o+wTqePitYEG0vZN/SljPp3kOAlFFhznbxrwtT8Oh6ObsECLUNidrVTmcH1gWw==
Content-Type: multipart/signed; boundary="Apple-Mail=_50F2B4FB-D857-47E1-BCDD-1825A18D598D"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <CABcZeBMxq0BCMqTZ49BB=W+ka1X1uLxd5HjcfKmeQ5i3TZWWFw@mail.gmail.com>
Date: Fri, 08 Sep 2023 15:09:42 +0300
Cc: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "gendispatch@ietf.org" <gendispatch@ietf.org>
Message-Id: <21CEF956-1440-464A-A4CE-60784D5AF1D0@eggert.org>
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: Eric Rescorla <ekr@rtfm.com>
X-Last-TLS-Session-Version: TLSv1.2
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/vSAoSHp9o5jbyOYHHOKhWi9m1Tg>
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, 08 Sep 2023 12:09:47 -0000

Hi,

I have some suggested changes based on your comments in https://github.com/larseggert/moderation/pull/33

On Jul 6, 2023, at 23:04, Eric Rescorla <ekr@rtfm.com> wrote:
> 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?

that was the current intent. I've added a todo on whether some boundaries should be defined.

> 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.

I'd agree. Maybe that to-be-added paragraph about boundaries can clarify this.

Thanks,
Lars