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

Mark Nottingham <mnot@mnot.net> Sun, 26 June 2022 04:19 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 91CBBC15AAD0 for <gendispatch@ietfa.amsl.com>; Sat, 25 Jun 2022 21:19:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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_BLOCKED=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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=xDmQsMGt; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=sse1JNR8
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 ORRaLkxpdSDM for <gendispatch@ietfa.amsl.com>; Sat, 25 Jun 2022 21:19:27 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 8F321C159481 for <gendispatch@ietf.org>; Sat, 25 Jun 2022 21:19:27 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id DFFDF5C00D7; Sun, 26 Jun 2022 00:19:25 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sun, 26 Jun 2022 00:19:25 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :cc:content-transfer-encoding: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=1656217165; x= 1656303565; bh=WjLdbAIlK78HpC7docZuzFmgl99S7GULXYzmXlzjBvk=; b=x DmQsMGtvlAbC8IzJHyzdeIy4SDzctukgHukfcXpYSA8Mc7xr1SBLAy6LM9dupr2p T0KMIjo9Y2LuPyTRD5JbDo6FWChL11HiR6Wf/R6Ncf4xBfF9hKX8Nes/G3cavWGj uwoTjl6YrhNzRXCAsf9RL12lXnkO+sOBiqdPXREmZ49ygEwtqbOCiLxm0wRLRx8S bvpXXW1R2uryM7KCUspxGBGaRL16CXXZv7xTpQi8HGA+LYYXoo6YoBVqA0KGnUJm sKgjHislm2mZM7xLk7clVOwI9hEavCguvwVK+ac/LdTx8GX2ZDNDJI5dC9i//7Ud MBB93Kyn9ey/TCw/SJg5A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :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=1656217165; x= 1656303565; bh=WjLdbAIlK78HpC7docZuzFmgl99S7GULXYzmXlzjBvk=; b=s se1JNR8vyeOCqLbWa9LJlbF3MAXORE2UzWBpwhb/EsJO1+6ajtyubWVPK+frIYMy iAU3/hnG60331V7fA3ch+7V7lM3cgdXkAVXUcXUVn8gIQU2yw9tjsScrF0gY3tfK o/AejjUMwcL3Jm4ALpDZHYZp0CujsNhU9iD96ymeFZl6f2vATjXLf174+S762XPn qx8/4OVNZ0lunir8htlexcU7TxF1SIuWChWqT5AZ4hB7lB8MgtHNIr0hfj1PSJFU Hx2GuXcUlAAnsXI4toweAfK20/E83HLgjL5h051c3eM/DQlNgWCxf6hYVgRTJyYQ j6Tx4TaMH0hd40A7jShaw==
X-ME-Sender: <xms:Td63YkAEnAsUzM9NGWaalGaOnafBdfmbui2ty1lh31-NXy7Z7QPGQQ> <xme:Td63YmhrNdACd9Hji4CMgaGt3BioXj_umX6R5qeC_YxxHMnVLqOijMn7FJ_yaLhdA W1iHpV3rR03rXcCug>
X-ME-Received: <xmr:Td63YnmDftCDZtFdgGNdlPU4W4oDB1cQ1mlBKU5XvJivGoXMThuIYW_UivIoUtOb80wqjTb6NtlOdS62-gpwD1G_31L47ohrwNUGGkbce_kCSzEWQZlqTVTY>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudegvddgkeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffvefgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghr khcupfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrth htvghrnhepgeelgeektdegueeffeevhfdvgfffhfehleehgfdttddvvdejgedvfeejtedv udelnecuffhomhgrihhnpehivghtfhdrohhrghdpmhhnohhtrdhnvghtnecuvehluhhsth gvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdr nhgvth
X-ME-Proxy: <xmx:Td63YqwcbNbZV0GIrNeu8GVtcUHMj8RWGSLUtC0CGMCuFgXR-_QhiQ> <xmx:Td63YpSBnkA9AeNhUTN6ItLxWA0gu3E3nZloeAnNRD3bbpSvcVBJ3w> <xmx:Td63YlbAPjnY7_wx-Ek2ASgQmQDwV65LU3QlqVcTRr0V16Xqwh1PGQ> <xmx:Td63YketGCpk2q0wwvW9e1xznSwuNTrQUY5DFqiZlzt_HDSUUMmLtQ>
Feedback-ID: ie6694242:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 26 Jun 2022 00:19:23 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <b5180ca1-f7a6-edfb-2ac6-31fe64ed88c1@lear.ch>
Date: Sun, 26 Jun 2022 14:19:17 +1000
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, gendispatch@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1902630E-B2FC-40F9-9AC9-5907D4EE6713@mnot.net>
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>
To: Eliot Lear <lear@lear.ch>
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/EgKYcllgUmpjIWZTF1h6lvW35mM>
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: Sun, 26 Jun 2022 04:19:32 -0000

Just my .02 - 

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.

Cheers,

* there may be more


> On 25 Jun 2022, at 11:03 pm, Eliot Lear <lear@lear.ch> wrote:
> 
> 
> On 25.06.22 02:30, Stephen Farrell wrote:
>> But, the above isn't that important, I think what's below is
>> moreso:
>> 
>> On 24/06/2022 05:29, Keith Moore wrote:
>>> IMO it's long past time to stop trying to kill IETF's sense of community and high time to start trying to restore one. 
>> 
>> I very strongly agree with the above. 
> 
> Me too.
> 
>> There are quite a few
>> aspects of that diminishing "sense of community" that could
>> be teased out, but IMO it'd likely be more productive to try
>> foster such things than dissect and try reconstruct 'em.
> 
> If what you mean in by dissecting and reconstructing is the splitting of lists and removal of plenary power from the IETF list, then I agree that we have fragmented that function in a way that has harmed the organization's community identity and, I believe, the Internet architecture.  Plenary is needed not only for that identity but so that the left hand (or however many hands we have) knows what the right hand is doing.
> 
> But that doesn't mean that there should be  a free-for-all on a mailing list.  Endless bickering about the same old subjects is not helpful.  Debating points not within the power of the IETF is counter-productive.
> 
> A plenary function need not consist of a single medium, but can be woven together between a mailing list, a chat room , f2f meetings, and documents.  A discussion has to have a beginning, a middle, and an end; with possible actions.  And it should be grounded in well thought out positions, preferrably in Internet-draft form.  If people can't take the time to write those, then whatever it is, it can't be SO important as to take the time and attention of the entire organization.
> 
> And yes, I've been thinking about this for a while.
> 
> Eliot
> 
> -- 
> Gendispatch mailing list
> Gendispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/gendispatch

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