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

Eliot Lear <lear@lear.ch> Sat, 25 June 2022 13:04 UTC

Return-Path: <lear@lear.ch>
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 6844EC15AAD4 for <gendispatch@ietfa.amsl.com>; Sat, 25 Jun 2022 06:04:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.972
X-Spam-Level:
X-Spam-Status: No, score=-3.972 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, NICE_REPLY_A=-1.876, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, 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 (1024-bit key) header.d=lear.ch
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 wcMX_T-LuKJF for <gendispatch@ietfa.amsl.com>; Sat, 25 Jun 2022 06:03:58 -0700 (PDT)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (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 AFC23C14F747 for <gendispatch@ietf.org>; Sat, 25 Jun 2022 06:03:55 -0700 (PDT)
Received: from [192.168.0.227] (77-58-144-232.dclient.hispeed.ch [77.58.144.232]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 25PD3n26090747 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Sat, 25 Jun 2022 15:03:50 +0200
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1656162230; bh=9MMGgyhoG/KRkbLZDEpm9tgtEIEIoRFnMPAmtyjt1jQ=; h=Date:To:References:From:Subject:In-Reply-To:From; b=iFeYbTIoYb+Ut3cBUT45bKemnIpOi9KFiB8EdbmF6tJzjMFNkxR6rlKvqMidcICR4 O2ttxkcyHE0WerngDtnxyB240wZZOo692zJYTfAa2y23g1wVXAon2n2iwmLrKG8oh3 tm6+KkLcxNAxADQO0LnpQghO/NSStMT/XP+q0ZTc=
Message-ID: <b5180ca1-f7a6-edfb-2ac6-31fe64ed88c1@lear.ch>
Date: Sat, 25 Jun 2022 15:03:49 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, gendispatch@ietf.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>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <bbafcb27-cf1d-665b-785c-137d4d20e2a9@cs.tcd.ie>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------8JkGoLgbMQN6Ub0OQCrNKIip"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/yYy9VCqZEpn55D_G7fKgmj5Lzr8>
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: Sat, 25 Jun 2022 13:04:03 -0000

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