Re: New Version Notification for draft-nottingham-discussion-recharter-00.txt

Keith Moore <moore@network-heretics.com> Tue, 18 August 2020 08:49 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C75043A077E for <ietf@ietfa.amsl.com>; Tue, 18 Aug 2020 01:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.844
X-Spam-Level:
X-Spam-Status: No, score=-2.844 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.949, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1mLE_vWwZ_KR for <ietf@ietfa.amsl.com>; Tue, 18 Aug 2020 01:49:11 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 603183A077C for <ietf@ietf.org>; Tue, 18 Aug 2020 01:49:11 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id A1EEB5C00E0 for <ietf@ietf.org>; Tue, 18 Aug 2020 04:49:10 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 18 Aug 2020 04:49:10 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=zLm8k1 H0v8AF8xJf6eLKHpHOPmNNpaaxAcYz5FnGzG0=; b=nCkU7DvAxurNI+rccgEK+C qPu0vU/D/B//h70qp3vVvJG1W6VvHo6LeJjB0h1m4mHId5YWjWHSNjge82w+xlAx WlbUT6n3HKEg/5AsIeX/brxA/YFMmXv4gkDz36z8BQrrW1Y2J4jm6MSB3nsIQT2f sx64OUKqs1Ombdf26RhgJiTxpahgJaYYEN+2+Yp+h9m7f8AF0Mls2OdkRAKI2RPC l8Q6ZLc7xjqfp5ND/uHWPN7nhKgpO4EEu47vqGOXaSs1ZZCNzU6ZmM4WAdjmOXud q5oIncPXuv5DBybVLjB0CBnW0FcjfpUnIbfc5oZYOBnKHV2Sj0jKEulbxyh6sdCQ ==
X-ME-Sender: <xms:BpY7X-wAcGIS_myaxs883C9Tp3KPbnZx7Gsmojy1ZGY1OW4EniC-gQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedruddtiedgtdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgesrgdtre ertdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhepveefteduieegtd elvddvtddufeejjeffvdefteejieeulefgtdfggedtffektedunecukfhppedutdekrddv vddurddukedtrdduheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:BpY7X6SIClRNjHMCmdXSY07jXTlFt-eMxt6b-_AUOOvBuWdf_iA3hg> <xmx:BpY7XwXez2U304Srr6PuV9XcmUrKPXkTw2NcQ8cGYb4l4UO4nYDcfw> <xmx:BpY7X0hyeWLFpHBjAMFFMeE0jP0rPJDoocb3lliX8nQlBpdiY0AkIQ> <xmx:BpY7X3Cxe9UvcEn0XqeFZjPD_WWH0xTsuY4ZSwKr1-dghhncKkKLNg>
Received: from [192.168.1.85] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id CED9830600A9 for <ietf@ietf.org>; Tue, 18 Aug 2020 04:49:09 -0400 (EDT)
Subject: Re: New Version Notification for draft-nottingham-discussion-recharter-00.txt
To: ietf@ietf.org
References: <CAKW6Ri5TFG6ckJTZGv+ox9K63xJuciN8aoNvsLgwbytVW=_F=g@mail.gmail.com> <220a3a9b-5885-1c45-d40f-d53af3a4e797@gmail.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <5ee8ea04-9d32-1efb-9103-8d36e2e3974a@network-heretics.com>
Date: Tue, 18 Aug 2020 04:49:08 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <220a3a9b-5885-1c45-d40f-d53af3a4e797@gmail.com>
Content-Type: multipart/alternative; boundary="------------D77508862514A9F029D9C9C3"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/t6AjiwDeEVT1Rcge-z2oReKoTSg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2020 08:49:13 -0000

On 8/17/20 6:23 PM, Brian E Carpenter wrote:

> 3. Moving contentious issues to dedicated open lists does not suppress debate.

I disagree somewhat, at least for issues that impinge on multiple areas 
of interest.  Every new list that a participant has to subscribe to in 
order to participate, is another impediment to broad participation.

I readily agree that the vast majority of IETF participants don't want 
to be bothered with administrative, policy, and process issues (and 
shouldn't need to be bothered by such things) - /unless/ they perhaps 
threaten fundamental or significant changes to how IETF works.   The 
question in my mind is: How to identify those issues, make the broader 
population aware of them, and make it easy to participate should they 
choose to do so (without bothering them if they don't)?

The low subscriber count to gendispatch is an indication that 
gendispatch isn't a great place to initially discuss, or dispatch, 
potentially controversial topics of widespread interest - precisely 
because its use in such instances would hide potentially controversial 
discussions from broad scrutiny.   And by the time a WG gets chartered, 
it's generally too late to fix its scope.

Sure, WG charters under consideration are posted to ietf-announce, but 
what percentage of participants really has time to read everything that 
gets posted to ietf-announce?  IMO that's another barrier to effective 
participation.

IMO the problem is _mostly_ a tools problem.   It seems like we could do 
a lot better at making it easy for participants to be aware of what's 
going on, without having to slog through enormous numbers of email 
messages.

Keith