Re: [Gendispatch] Updating the IETF Discussion List Charter (was: Fwd: New Version Notification for draft-eggert-bcp45bis-02.txt)

Lars Eggert <lars@eggert.org> Mon, 04 July 2022 10:40 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 706B1C15948D for <gendispatch@ietfa.amsl.com>; Mon, 4 Jul 2022 03:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-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 Vc9Rhm8lA5iR for <gendispatch@ietfa.amsl.com>; Mon, 4 Jul 2022 03:40:51 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 406B8C157B5B for <gendispatch@ietf.org>; Mon, 4 Jul 2022 03:40:51 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:307a:24d:c8a1:615c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 4B1F91F026F; Mon, 4 Jul 2022 13:40:42 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1656931242; bh=EnWgYi8eG8Xgs6QNWAV8f3DE4HTsNPzbcNseyxoDy3w=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=Rry2RNeIwZ/5GWOJdTImDq1x6rehrkmhlO2at9HI5kojvPS4IZ+PNOS8+jyFOcAUp Nf3pBo7XFkWkMUQRgDhl0/kGZObze98f3umD7vxbl41X00M4M1Lo12/NUhBVKcMJ7z AFzqLEJJLlF0//WIkEvfhrdAqCMXf6VNpcbV8VBc=
Content-Type: multipart/signed; boundary="Apple-Mail=_24E25149-A94C-4475-8DE8-48F06AA293A0"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <1902630E-B2FC-40F9-9AC9-5907D4EE6713@mnot.net>
Date: Mon, 04 Jul 2022 13:40:41 +0300
Cc: Eliot Lear <lear@lear.ch>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, gendispatch@ietf.org
Message-Id: <76EFD000-3084-44EB-BD61-200448156C82@eggert.org>
References: <162444929705.22096.2956472779291079641@ietfa.amsl.com> <ED2832A3-F392-4F7F-8483-071140AB8FF6@eggert.org> <07736465-1FEB-4419-B6F5-B18ABB23865C@eggert.org> <CAChr6SzvXDxzi49ZG3oCJGVDh03iSOMgVVqj4EaOUM9TsJxFgQ@mail.gmail.com> <cfac3427-510b-fcf0-fdce-e1b3b7908a52@network-heretics.com> <bbafcb27-cf1d-665b-785c-137d4d20e2a9@cs.tcd.ie> <b5180ca1-f7a6-edfb-2ac6-31fe64ed88c1@lear.ch> <1902630E-B2FC-40F9-9AC9-5907D4EE6713@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-MailScanner-ID: 4B1F91F026F.A3B34
X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/pHuO6mFzsvmZhR_niX_2UKFO0VU>
Subject: Re: [Gendispatch] Updating the IETF Discussion List Charter (was: Fwd: New Version Notification for draft-eggert-bcp45bis-02.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: Mon, 04 Jul 2022 10:40:55 -0000

Hi,

sorry for the delay in responding, I was out on vacation.

On 2022-6-26, at 7:19, Mark Nottingham <mnot@mnot.net> wrote:
> I think one root of the problem* is that past attempts at moderation have been attacked as illegitimate, overreaching, etc. So to improve things, I think we need two things:
> 
> 1) A well-defined purpose and scope for the plenary function (which implies that what it is *not* is also defined), and
> 2) A well-thought-out moderation function that's broadly seen as legitimate.
> 
> I think we could get a start on both at our next synchronous plenary if the IESG Chair were to ask some well-crafted questions to the community in the form of hums.

the community discussion around BCP45bis (which is now RFC9245) made it very clear that at least part of the community does not want me or the IESG to take a lead in this space.

So while I'd be happy to facilitate a discussion - including hums at the plenary if that is deemed useful - any effort here should be community-driven.

(I believe Eliot Lear has recently posted about starting a team to work on a "new model for plenary", for which something like this may be in scope. There may be other activities that I am unaware of.)

Thanks,
Lars