Re: [Gendispatch] draft charter text: terminology-related WG

Keith Moore <moore@network-heretics.com> Sun, 14 February 2021 00:29 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 5D86D3A11C7 for <gendispatch@ietfa.amsl.com>; Sat, 13 Feb 2021 16:29:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 fzh1xxiqAJAl for <gendispatch@ietfa.amsl.com>; Sat, 13 Feb 2021 16:29:53 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB6453A11C3 for <gendispatch@ietf.org>; Sat, 13 Feb 2021 16:29:52 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 454225C0087 for <gendispatch@ietf.org>; Sat, 13 Feb 2021 19:29:52 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sat, 13 Feb 2021 19:29:52 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding: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=fm2; bh=zlqdada1+iy5uGXHiw0gTJRHllO0DDviU3mXZ5hWB 8E=; b=URkgJ8673IG799Oovk2ld+jcJUiCDuxYej0nczPGGg6MF1/D7cfFyafIX qimRuBbDpBNea5YVDrhQsDTeGqh4XuQeaDfs/4188X1eGsw56RbbG+0h5vx221vb +VfdccO4itU6KbF1TORio+PkJ8lPHSpsbeP+HsBhL0Y3APRSnw7FUFxYkYpfhegv iWtkSp7fwZt/K2fVzK48D8A5Eua5WhmWVrJzcVpPCK6YyZGqjHj6d9oyiEDSrydy vFodx2WPG+QB9/TFq5KJmgefpmhslnmCqwhCCDc+kUvEbBPM1usTTUI3dM6C1Bn/ qU5qR44C07408W+edyzjSy9PpcAtQ==
X-ME-Sender: <xms:_24oYJoBmOplWb441_BwpMaD2QI2DquVNuJyo4a8qbcUjKBTLTUPSw> <xme:_24oYLomF8KPe0gT6SR6Gzp97A3h_hXQ_Ru57Jkqb4AkDso6z1GvO-yCvo6XGhhvt R2qhftR8wraig>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrieeggddvudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekre dttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhephefhuedtheefgf efgffhkeehgfeugfeiudeugeejkeefleelueeiffetfeeuudeunecukfhppedutdekrddv vddurddukedtrdduheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:_24oYGPxfmfnGQH1KQn8vz-LI0RbafMdZF6myzN0QzC29fwx5Twj1Q> <xmx:_24oYE4lE8T53smPovnPIIky7OdnVHFaYuhFcuvuqn66AoJ0cXtA4Q> <xmx:_24oYI661vNQOa6YuRJkXmMPV3OyzA3NzGETWdQj9x1yIovZV7A8Mg> <xmx:AG8oYPIWstalyOCnqk-mNhI0rEwOUGjY8GQBNHg7hQDkWv6o6ZyECA>
Received: from [192.168.1.90] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 446D3108005C for <gendispatch@ietf.org>; Sat, 13 Feb 2021 19:29:51 -0500 (EST)
To: gendispatch@ietf.org
References: <20210212205351.27E4B6DDB49D@ary.qy> <3b4ea13c-0743-c882-7fc0-1fe7288f6d07@gont.com.ar> <a2e6c65e-076a-8875-c374-56c825105a6c@cs.tcd.ie> <CAGVFjM+sgyRDhuVYvkPC1XbH4yL-Q_Qpbs_naZpS3D3ApPO92A@mail.gmail.com> <772fa23e-4170-82d2-8ee2-caececd83904@si6networks.com> <E53D1060-5F25-4495-8C97-6A0F0EFD2117@mnot.net> <47ff90d4-b960-f159-c064-1f963c717c31@network-heretics.com> <3535f045-f2cb-58bc-8e91-fd92c65b16fe@joelhalpern.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <e7c93dc7-4701-21c8-2831-7fb79f0ca107@network-heretics.com>
Date: Sat, 13 Feb 2021 19:29:50 -0500
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: <3535f045-f2cb-58bc-8e91-fd92c65b16fe@joelhalpern.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/Zbu2YJEw8_kKo72Kby_fcl_5JPM>
Subject: Re: [Gendispatch] draft charter text: terminology-related WG
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Feb 2021 00:29:54 -0000

On 2/13/21 7:11 PM, Joel M. Halpern wrote:

> What I am wondering is if any of the folks who are concerned abut 
> issues outside of language selection can draft a charter.  Then we, 
> and the IETF, can decide (assuming we agree on the value of the 
> proposal) if the two charters should be combined, if we should have 
> two working groups, or if we should have only one (and which.)
>
> I don't think it is really fair to the proponents of this proposal to 
> object on the grounds that we should do some unspecified different thing. 

It is if doing one of these things takes up energy that would otherwise 
be used to address the broader problem.

But unlike publishing a document, diversity and inclusion isn't a 
check-off item.   It's not a problem that you can solve once and move 
on.   It's something that has to be built into community values and 
maintained indefinitely by the whole community (or most of it).   Simply 
publishing yet another RFC won't do that.     So we can't rely on our 
habits or familiar processes, we have to work through out to do it and 
make it part of our normal discussions. There used to be a lot of this 
value in IETF culture, and I think there's still some left.   How do we 
revive and expand it?

Keith