IETF Logo Mail Archive

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

Eliot Lear <lear@cisco.com> Tue, 16 February 2021 12:59 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 9EB813A0BC2 for <gendispatch@ietfa.amsl.com>; Tue, 16 Feb 2021 04:59:22 -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 aIi4u-oimrrG for <gendispatch@ietfa.amsl.com>; Tue, 16 Feb 2021 04:59:21 -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 E18EF3A0BB8 for <gendispatch@ietf.org>; Tue, 16 Feb 2021 04:59:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3181; q=dns/txt; s=iport; t=1613480361; x=1614689961; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=7zS2fnJnSGLWRyQyBjQvdR2h7Ej3sYIwJyd/U70f2DQ=; b=m1+QSsnxRF4HPSYR6R9PHGpkjfRO0kF8IH1ucym1FM/e3Krm9es1JM2t WTRxmEJjguAOCfxAethosieDnBZ/wS58CO3H08JDgXWxBpb1+GryhXGNJ AgUkjHPQcp4wNvQF3qCjht5W17E0arYjUfK3kVauB1wlo1rqnObWN622P s=;
X-Files: signature.asc : 488
X-IPAS-Result: A0BDAAASwStgjBbLJq1iHAEBAQEBAQcBARIBAQQEAQGBfQUBAQsBg3YBJxIxhEGJBIhPA5pLgXwEBwEBAQoDAQE0BAEBhE0CggomNgcOAgMBAQEDAgMBAQEBBQEBAQIBBgQUAQEBAYZHhkQBAQEDASNWBQsLGCoCAlcGExSCXAGCZiCsTHaBMoVYhG8QgTgBgVKLb0KCAoE4HIJXPodUNIIrBIFVEAGBRAEDAy8qFwKCUpJ/iVKcSYMEgyuBOpcmAx+DMYpIlTSObqJzYoNzAgQGBQIWgVwLJoFZMxoIGxVlAYI+PhIZDY4rDgmOKEADLzcCBgEJAQEDCYwTAQE
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.81,183,1610409600"; d="asc'?scan'208";a="33490864"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 16 Feb 2021 12:59:16 +0000
Received: from ams3-vpn-dhcp722.cisco.com (ams3-vpn-dhcp722.cisco.com [10.61.66.210]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 11GCxGjB021064 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 16 Feb 2021 12:59:16 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <21B2B2C6-5F2A-47C4-92BC-F184D93AAC40@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_BA0FB5C0-4A33-4AA7-B004-DEE6C0417772"; 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 13:59:14 +0100
In-Reply-To: <C1ADE976-219A-42C1-9399-152B99608E5E@eggert.org>
Cc: Martin Thomson <mt@lowentropy.net>, gendispatch@ietf.org
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>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
X-Outbound-SMTP-Client: 10.61.66.210, ams3-vpn-dhcp722.cisco.com
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/iIykgzt90XsnV4KsRB_RFpQAQ-k>
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 12:59:23 -0000

Hi Lars and Martin,

May we please have these two issues resolved first?

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.   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.  Simply saying, “Go form your own working group” is not.  THAT would be obstructionist.

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.

Eliot

> On 16 Feb 2021, at 09:46, Lars Eggert <lars@eggert.org> wrote:
> 
> Signed PGP part
> Hi,
> 
> On 2021-2-15, at 23:48, Martin Thomson <mt@lowentropy.net> wrote:
>> On Fri, Feb 12, 2021, at 07:39, Sean Turner wrote:
>>> While opinions vary among IETF participants about this topic, there is
>>> general agreement that the IETF community would benefit from
>>> informational recommendations about using effective and inclusive
>>> terminology in IETF documents.
>> 
>> Hi Sean,
>> 
>> Thanks for doing this.  The above statement sums it up pretty well.
> 
> agreed.
> 
>> My suggestion is that we go ahead with the work with the charter verbatim.
> 
> Again, agreed.
> 
> There are certainly several other ways in which we can attempt to increase inclusivity and diversity of the IETF, and we should also come to consensus on starting some of those. But those discussions need not delay us from formally starting this effort.
> 
> Thanks,
> Lars
> 
> 
>

v2.23.0 | Report a Bug | By Email