Re: [Gendispatch] New Version Notification for draft-ecahc-moderation-00.txt
Eric Rescorla <ekr@rtfm.com> Fri, 07 July 2023 04:17 UTC
Return-Path: <ekr@rtfm.com>
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 618B8C152575 for <gendispatch@ietfa.amsl.com>; Thu, 6 Jul 2023 21:17:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.894
X-Spam-Level:
X-Spam-Status: No, score=-6.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=rtfm-com.20221208.gappssmtp.com
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 0ceDqWUkqpMd for <gendispatch@ietfa.amsl.com>; Thu, 6 Jul 2023 21:17:51 -0700 (PDT)
Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 7F561C1524BC for <gendispatch@ietf.org>; Thu, 6 Jul 2023 21:17:51 -0700 (PDT)
Received: by mail-yb1-xb33.google.com with SMTP id 3f1490d57ef6-c5cf26e9669so1547951276.0 for <gendispatch@ietf.org>; Thu, 06 Jul 2023 21:17:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20221208.gappssmtp.com; s=20221208; t=1688703470; x=1691295470; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=VUqpT0pgZtt6CRh/WvUzAVlCAnegGWJkpKBqRh9OZfk=; b=zywh2d2YHLy0isn3PfO8cU/ppE85CqcsrAYWrpRRyvO0no5X0cAnco+EJgCGRMoxnw W+6850w3rvco7YsD4LzQ27US7mzaF0ZAvBEHobpW1hacRqhNyKKdd6mJoszYYCiEVZkS 9EzJYxHM6VvC1qLcw5kgUqIpIV/QapXLzytiF+zzXsZ0kecY4zcUDkrAxtofavousCFw 1FavznaXuER81lE5scQ9rGl68EN8SXNXPj2AdtwEmoMbMNNcMx1VMHjiCY9y0F88ybLV gcYSaAbigUcC2yy41rLjWr+GPzg6YTwrbiMZYHmE2NkorwBVLvZoXmEJ3tFzaG3iEh+9 +TjA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688703470; x=1691295470; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=VUqpT0pgZtt6CRh/WvUzAVlCAnegGWJkpKBqRh9OZfk=; b=ggEd80o7mKPkTMzDyszhqZgn9VzFd+uOVbDo8BWf0uMpGJ9S5f47IxrpyTQVHSQo4K fU1JO1HWSwk3UFTW1BQMv0upInwjIHpmc//rfFGALg080H+hxFhlUPnEDX2Gg7lsdiGf kZmwbQeyMkBpOiwboZZO0wAu49eKvZw/370vYok2I8g25eToXaloUj14Oyih9tAFZMZr Q2zctVCR9V8cZgFs5jZgi+XP07CjnZMnQUqm86dM+QTFxl7FQ+ZIolvtOppNnVMcFsuf Hb0+tJVCjfTcl7PXKpVtIkLEQyUMaZQ5luE/jDrCrTesIivHOyYq1NOocoSECbDDij74 +68A==
X-Gm-Message-State: ABy/qLZYwTjvlgiJ35PFEuDwBaDrx39CUZ6NzO4+FF5dSz9R/CEqtcTJ QI2oy9ZXEZwfW/ElGeWjS2I0w0Xmmt9rSyH9vzlmhw==
X-Google-Smtp-Source: APBJJlF4zvcNMkp2LKTmi2nh1y7vvNNUY7zQCdwNaDBXm2+O8J8DVSn8efwiqMi0CflDfWrWlqq4Umaz3lX7VEOpTWI=
X-Received: by 2002:a0d:e284:0:b0:570:28a9:fe40 with SMTP id l126-20020a0de284000000b0057028a9fe40mr4161067ywe.5.1688703470508; Thu, 06 Jul 2023 21:17:50 -0700 (PDT)
MIME-Version: 1.0
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> <F5DB78AB-A5D8-408A-956D-8599DD6B9641@mnot.net> <798e2268-9035-222a-8d9a-0c723ddd2acc@gmail.com>
In-Reply-To: <798e2268-9035-222a-8d9a-0c723ddd2acc@gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 06 Jul 2023 21:17:14 -0700
Message-ID: <CABcZeBMwthcU7SQXqYo-O9MHDzRXk6QJXqz_qb2d9BQeXgaeWQ@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Mark Nottingham <mnot@mnot.net>, "gendispatch@ietf.org" <gendispatch@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007db23505ffddea36"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/BDcq_Bp_i9wYowSJE0M6j56Xeb4>
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 04:17:55 -0000
On Thu, Jul 6, 2023 at 9:02 PM Brian E Carpenter < brian.e.carpenter@gmail.com> wrote: > Just responding to one of Mark's excellent points: > > On 07-Jul-23 13:56, Mark Nottingham wrote: > > > 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? > > I think that a published set of IETF-wide criteria for moderation will, > over time, level out the differences between WGs to some extent. But it > makes perfect sense that not all WGs will be the same; why should they be? > > That's why my personal opinion is that WG Chairs should definitely be able > to moderate, with the ability for them to invoke the moderator team after a > few days. Some WG chairs might not want to do that, so they could call in > the moderators without delay. Others might prefer to handle the problem > themselves if possible. Why would we need a fixed rule about that? > > Typing that, I realised that the draft doesn't define the term > "moderation". Probably we should define it to embrace notification ("Your > messages are on the edge of disruptive."), persuasion ("Please dial it back > and stick to the technical topic."), warning ("If you don't stop, we'll > have to take action.") and action. Perhaps we need a rule that only the > moderation team itself can decide to block a sender? That would help to > clarify the role of the WG Chairs. > I don't yet have a firm opinion on whether this is a good thing, but I would note that at present RFC 3934 [0] allows a chair to suspend posting privileges unilaterally (though of course this is appealable), so this would be a change to the chair's authority. -Ekr [0] https://www.rfc-editor.org/rfc/rfc3934#section-2 > Brian >
- Re: [Gendispatch] New Version Notification for dr… Salz, Rich
- Re: [Gendispatch] New Version Notification for dr… Eric Rescorla
- Re: [Gendispatch] New Version Notification for dr… John Levine
- Re: [Gendispatch] New Version Notification for dr… Mark Nottingham
- Re: [Gendispatch] New Version Notification for dr… Brian E Carpenter
- Re: [Gendispatch] New Version Notification for dr… Eric Rescorla
- Re: [Gendispatch] New Version Notification for dr… Jari Arkko
- Re: [Gendispatch] New Version Notification for dr… Eric Rescorla
- [Gendispatch] New Version Notification for draft-… Stephen Farrell
- Re: [Gendispatch] New Version Notification for dr… John R Levine
- Re: [Gendispatch] New Version Notification for dr… Mark Nottingham
- Re: [Gendispatch] New Version Notification for dr… Eric Rescorla
- Re: [Gendispatch] New Version Notification for dr… Brian E Carpenter
- Re: [Gendispatch] New Version Notification for dr… Paul Wouters
- Re: [Gendispatch] New Version Notification for dr… John R Levine
- Re: [Gendispatch] New Version Notification for dr… Vittorio Bertola
- Re: [Gendispatch] New Version Notification for dr… Brian E Carpenter
- Re: [Gendispatch] New Version Notification for dr… Mark Nottingham
- Re: [Gendispatch] New Version Notification for dr… Rob Sayre
- Re: [Gendispatch] New Version Notification for dr… Rob Sayre
- Re: [Gendispatch] New Version Notification for dr… Salz, Rich
- Re: [Gendispatch] New Version Notification for dr… Stephen Farrell
- Re: [Gendispatch] New Version Notification for dr… Brian E Carpenter
- Re: [Gendispatch] New Version Notification for dr… Stephen Farrell
- Re: [Gendispatch] New Version Notification for dr… Brian E Carpenter
- Re: [Gendispatch] New Version Notification for dr… Stephen Farrell
- Re: [Gendispatch] New Version Notification for dr… Eric Rescorla
- Re: [Gendispatch] New Version Notification for dr… Jari Arkko
- Re: [Gendispatch] New Version Notification for dr… Salz, Rich
- Re: [Gendispatch] New Version Notification for dr… Brian E Carpenter
- Re: [Gendispatch] New Version Notification for dr… Rob Sayre
- Re: [Gendispatch] New Version Notification for dr… Stephen Farrell
- Re: [Gendispatch] New Version Notification for dr… Alissa Cooper
- Re: [Gendispatch] New Version Notification for dr… Rob Sayre
- Re: [Gendispatch] New Version Notification for dr… Lloyd W
- Re: [Gendispatch] New Version Notification for dr… Lloyd W
- Re: [Gendispatch] New Version Notification for dr… Rob Sayre
- Re: [Gendispatch] New Version Notification for dr… Lloyd W
- Re: [Gendispatch] New Version Notification for dr… Lars Eggert
- Re: [Gendispatch] New Version Notification for dr… Lars Eggert
- Re: [Gendispatch] New Version Notification for dr… Lars Eggert
- Re: [Gendispatch] New Version Notification for dr… Salz, Rich
- Re: [Gendispatch] New Version Notification for dr… Rob Sayre
- Re: [Gendispatch] New Version Notification for dr… John Levine