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

Lars Eggert <lars@eggert.org> Tue, 16 February 2021 14:05 UTC

Return-Path: <lars@eggert.org>
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 276013A0CF2 for <gendispatch@ietfa.amsl.com>; Tue, 16 Feb 2021 06:05:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 fbXVXfrP9i2O for <gendispatch@ietfa.amsl.com>; Tue, 16 Feb 2021 06:05:34 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90D3D3A0CF1 for <gendispatch@ietf.org>; Tue, 16 Feb 2021 06:05:34 -0800 (PST)
Received: from [IPv6:2a00:ac00:4000:400:e437:e43d:7072:b449] (unknown [IPv6:2a00:ac00:4000:400:e437:e43d:7072:b449]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id B44E56002FE; Tue, 16 Feb 2021 16:05:27 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1613484327; bh=OYAvjcOXpBx2bhNfuYYjyAJLK4Xhz65k45cqdjPeGWs=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=PLJCnm6YpFqns4MG/nlYs6pNE12xFPJHe+AsCRJQjTLnrPcuXHA7FK7Vlw/I64XRI ketXM4lvjYGMWvtAgrFsV+axgKmxthb08sYdvAasp+QkYZTdygxByLclJK1UE1jL3E IWgqvvw+v1fSHXClAMwyDg0O/1fhUj1KXyKLE1rk=
From: Lars Eggert <lars@eggert.org>
Message-Id: <EF2C1572-2485-44AA-B8C2-C8508AB7BDF6@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_C8905C26-1B57-4867-BD07-6645FDCB816A"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Tue, 16 Feb 2021 16:05:24 +0200
In-Reply-To: <21B2B2C6-5F2A-47C4-92BC-F184D93AAC40@cisco.com>
Cc: Martin Thomson <mt@lowentropy.net>, gendispatch@ietf.org
To: Eliot Lear <lear@cisco.com>
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>
X-MailScanner-ID: B44E56002FE.A4CCE
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/mop-jQ-NvVoDVe0FZoB00ytYByA>
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 14:05:36 -0000

Hi,

On 2021-2-16, at 14:59, Eliot Lear <lear@cisco.com> wrote:
> May we please have these two issues resolved first?

I'll comment on the issues below, but could you try and explain why they need to be resolved first, i.e., before this chartering can go forward?

> The first issue is the point that Fernando has raised.  What he has said, something with which I agree, is that there are many other issues to address.  Having a catalog of these issues, and where they need to be sorted, would be useful.

I agree that it would be useful.

>   If, Lars, you would agree to AD sponsor such a doc, that would also be fine with me.  If you think it’s a or a standing document that is NOT an RFC, that is ALSO fine with me.  But some approach going forward is necessary.

I would like to wait until there is at least a rough draft of what such a list or document would look like before trying to determine if and how it should get published.

>   Simply saying, “Go form your own working group” is not.  THAT would be obstructionist.

I don't agree. After a lengthy discussion and some interims, we now have a narrowly-scoped charter proposal that attempts to make progress in one particular direction that seems reasonably well understood and aligned with efforts in the broader tech community.

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?

> Second, EKR raised a point that it would be “helpful” to speak of the principles that guide the work.  Here I go further and say that it is more than just helpful, but necessary.  Again, that hasn’t really been addressed.  That’s important because otherwise we’ll end up arguing incessantly in every working group about which words are and are not offensive, and what this issue has shown is that such arguments themselves are counterproductive.

I read Ekr's email as suggestion for a charter text clarification about the planned content of the deliverables, not as prerequisite to chartering it.

Thanks,
Lars;