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

Keith Moore <moore@network-heretics.com> Fri, 24 June 2022 19:23 UTC

Return-Path: <moore@network-heretics.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 E8E7CC157B41 for <gendispatch@ietfa.amsl.com>; Fri, 24 Jun 2022 12:23:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.781
X-Spam-Level:
X-Spam-Status: No, score=-3.781 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-1.876, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-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 (2048-bit key) header.d=messagingengine.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 vKUkBVvN3z0N for <gendispatch@ietfa.amsl.com>; Fri, 24 Jun 2022 12:23:31 -0700 (PDT)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (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 C0DD3C159480 for <gendispatch@ietf.org>; Fri, 24 Jun 2022 12:23:25 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 1DBCA3200708; Fri, 24 Jun 2022 15:23:23 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Fri, 24 Jun 2022 15:23:23 -0400
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=1656098602; x= 1656185002; bh=PoF1uAEG+9zuIt3UcE/FhvYNo48kfJZXukb9sFUgl1c=; b=L E2BvtKVSzgoUWTmqHagWSX29dwM/TMh8jI6sXujRGdRHrRyJ3ij2qKebeiVHs2HI nq0aznsvGS/1CV3AzzZQ2A2xIBlyeg1+5/PG0tZzzBmugCDj4I+W6DQRKudXX5lE VOtuFVloxiZgYD1N6byMfxEW587SxJ0U+SUPqD7Ai0LYnnjkrMD9v5d1jn00CII5 MSm9+AppVNCGaGqp1vfFu08uIfbxgRnDbETVz9iqdTa8TFOS+BbtQ8ex3p1yFdr6 urxNbjeHqDmlMHGVQk+Xb95YrNdbIDkaa2qXLp/aB3xazIceHMN4i5q433SuMskG b+T8lzbsOJdIlQI+1lysg==
X-ME-Sender: <xms:Kg-2Ymn4oHlsraV3U4WHII148ZXpic8lxsIfmCO_cfZPDjlhsApZxw> <xme:Kg-2Yt02er-6tELwbRz2Y0N6h0DFxPCKzqxqOqUZJQ0Y30GUnG4paclcD2jKwiPlK hySWphmWgsoWg>
X-ME-Received: <xmr:Kg-2YkpCcIUldKkV99j7Lt2-UDi_YFfUCc4BMuCg4tMIt2spZdpEWJctlEaVrnx8JrV_MEoTRwRWHnnQJ0HEP-SbYxuKiANMlNw9iOn9m6E8mQj0GInmSw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudefledgudefgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfevfhfhjggtgfesthekredttdefjeenucfhrhhomhepmfgv ihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtg homheqnecuggftrfgrthhtvghrnhepuedvheehteefudeujedtleduiefgvefggfduveev keduvdehveevgeekffdvjedvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:Kg-2YqkhdjnJsmWiuXtUYfnhxe8ztzVafalewAhXbFKBiThD4Q4Ymg> <xmx:Kg-2Yk3vmWv4RnDzTLIikyO6YBIHQ4S_pw7725X3H33HrBukvNq_-w> <xmx:Kg-2YhuubP8V3hZEYk_gxy1RQ19_C2aYGsa_VaJmHsw8-9KX0itu9Q> <xmx:Kg-2Yp-eo59S_3CCwmHhVw7m_0qL3LywcyLehwhFNfX8XVzOZMY0EQ>
Feedback-ID: i5d8c41f0:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 24 Jun 2022 15:23:22 -0400 (EDT)
Message-ID: <709d7ce0-aee7-7564-150c-d0c403cf1f0b@network-heretics.com>
Date: Fri, 24 Jun 2022 15:23:21 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1
Content-Language: en-US
To: Rob Sayre <sayrer@gmail.com>, Barry Leiba <barryleiba@computer.org>
Cc: GENDISPATCH List <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> <CALaySJ+NE9X+YyXixAq2Xbe79EP5+M7Yha4QKtfokQ+AX+eLkA@mail.gmail.com> <CAChr6Swua0bTuB-ZRzGbM+5ZPLLtSZ9FvYo4AQ-wF8=bjbah3Q@mail.gmail.com>
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAChr6Swua0bTuB-ZRzGbM+5ZPLLtSZ9FvYo4AQ-wF8=bjbah3Q@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/RrDEfRNVqrRjY-xi2HIvGMYWCik>
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: Fri, 24 Jun 2022 19:23:36 -0000

On 6/24/22 15:10, Rob Sayre wrote:

> I agree that it is a reasonable topic, but I question whether "the 
> most general IETF list" is the right place for it.

The same argument could be made for any topic discussed on the IETF 
list.   How many lists should IETF participants have to follow in order 
to participate in community discussions?    Is there an explicit goal of 
discouraging input from  generalists, or is that a completely accidental 
effect?  (Hint: it's no longer accidental once you're aware of it.)

This is the exact opposite of inclusion.  It's overt discrimination.


> The IETF list often ratholes on meeting planning issues (and related 
> politics). People actually get paid to think about the problem. There 
> are event planners and insurance policies, etc.
>
Yes, and if those people operate without community input, they will make 
poor decisions.   And completely aside from meeting planning issues, 
individual participants need to be able to make informed decisions about 
whether to attend.

Keith