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

Eliot Lear <lear@cisco.com> Tue, 16 February 2021 20:02 UTC

Return-Path: <lear@cisco.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 747133A1044 for <gendispatch@ietfa.amsl.com>; Tue, 16 Feb 2021 12:02:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level:
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 IRQbFX4pjEWw for <gendispatch@ietfa.amsl.com>; Tue, 16 Feb 2021 12:02:41 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D88103A1300 for <gendispatch@ietf.org>; Tue, 16 Feb 2021 12:01:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2879; q=dns/txt; s=iport; t=1613505715; x=1614715315; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=kdJ2B4YvkV4siVlZW8xcLwT13QPalvwWbNpwiqqif2A=; b=CTTCoJrve+Z3D4/OJL8KJhOfkZLLRtwg3ipkcaDV44fEHSy0RV0TTLcZ 6L+4KY/EgZOkgQsfyu+FsOuphaDRfg1yAnk0Jv25kWkWpLbk4Mzjd4jmm 57M5S9wMSlnxjeyoZ5p3Rj9r3rN5RyZAs24M3B6EX1sif+tBRzLXMZa5f A=;
X-Files: signature.asc : 488
X-IPAS-Result: A0CdAADOIyxgjBbLJq1iHAEBAQEBAQcBARIBAQQEAQGBfgQBAQsBg3YBJxIxhEGJBIhRnEcEBwEBAQoDAQE0BAEBhE0CggomNwYOAgMBAQEDAgMBAQEBBQEBAQIBBgQUAQEBAYZHhkQBAQEDASNWBQsLGCoCAlcGE4JwAYJmIK1FdoEyhViEchCBOAGBUottQoICgTgcglc+h1Q0gisEgU+BX0MZGYFBgRGSf4lSiwCRSYMEgyuBOpcmAx+DMYpIhUaPbo5uo1WDcwIEBgUCFoFrIoFZMxoIGxVlAYI+PhIZDY4rDgmOKEADLzcCBgEJAQEDCYwTAQE
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.81,184,1610409600"; d="asc'?scan'208";a="33499607"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 16 Feb 2021 20:01:50 +0000
Received: from [10.61.174.100] ([10.61.174.100]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 11GK1n8c016402 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 16 Feb 2021 20:01:50 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <0C7B8766-E58A-4F66-9B07-AA1ACB750871@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_01AE3189-CD50-4AED-979F-B8E9DC787C75"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Tue, 16 Feb 2021 21:01:49 +0100
In-Reply-To: <B9EFFFAF-485D-4FB6-A2AD-9FE8A5CC0742@eggert.org>
Cc: GENDISPATCH List <gendispatch@ietf.org>, Martin Thomson <mt@lowentropy.net>
To: Lars Eggert <lars@eggert.org>
References: <A531C377-33A4-4138-BE28-788FF5FE267E@sn3rd.com> <681a1e99-68a3-4079-b5fb-37d015c3722c@www.fastmail.com> <C1ADE976-219A-42C1-9399-152B99608E5E@eggert.org> <21B2B2C6-5F2A-47C4-92BC-F184D93AAC40@cisco.com> <EF2C1572-2485-44AA-B8C2-C8508AB7BDF6@eggert.org> <F8F322B3-C10F-4799-BBEB-A26954019400@cisco.com> <B9EFFFAF-485D-4FB6-A2AD-9FE8A5CC0742@eggert.org>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
X-Outbound-SMTP-Client: 10.61.174.100, [10.61.174.100]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/3mT4zzwf4x3YB4bSISH7cH1D4rg>
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: Tue, 16 Feb 2021 20:02:43 -0000


> On 16 Feb 2021, at 20:19, Lars Eggert <lars@eggert.org> wrote:
> 
> I fail to understand how chartering this WG prevents discussion of and work on other initiatives that can make far more of a difference in terms of inclusivity.

The difference is talking about doing and just getting on with the job.

> 
> I see this as starting a particular effort that we've discussed for a long time and have at least some consensus on. This is a beginning, not an end?

I should hope.

> 
>> And just on this:
>> 
>>> As many others have already said, that doesn't mean that this effort should or will be the only thing we'll do towards increasing inclusivity. I fully expect that we'll discuss objectives and proposals for other activities in the future, possibly based on the catalog you mention above. But I see no reason to postpone the start of this particular activity until we know what else we might want to do?
>> 
>> I have not suggested that.  I suggested that we allow a specific optional work item to be discussed in the new WG.  What I don’t understand is the argument opposing.  But sure.  We could come back here, and have the argument to dispatch… again.
> 
> Is the specific optional work item you are referring to the "catalog of diversity issues"? (Please correct me if I misunderstood and/or summarized incorrectly.) If so, I see that as a useful activity, but one that is outside the narrow charter of this proposed WG.
> 
> We should absolutely come up with other initiatives to increase inclusivity and charter or otherwise realize them. But I see no good reason to delay the start of this particular initiative until we're ready to also start others.
> 

Do we lack consensus on the one narrow point I mentioned?  If so, I’m just saying let’s get on with it.

Eliot