IETF Logo Mail Archive

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

Lars Eggert <lars@eggert.org> Tue, 16 February 2021 08:47 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 5B5573A10B0 for <gendispatch@ietfa.amsl.com>; Tue, 16 Feb 2021 00:47:02 -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 DmeYUTSZdwdv for <gendispatch@ietfa.amsl.com>; Tue, 16 Feb 2021 00:47:01 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 24D9A3A10AC for <gendispatch@ietf.org>; Tue, 16 Feb 2021 00:47:01 -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 792876002FE; Tue, 16 Feb 2021 10:46:50 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1613465210; bh=/U/Slw51pYGU+AYdujpmQxciuZATz1pVfwn91adYIvk=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=YCnqgG2o1c8dO5CPg55MAq5KEtWJmCpZqAl4QVTidKq2nLJlVpL9KxBdPIsoe1EEY ztKueHpgXcLlXeHIUO9mGmcvWlebj9ZPqLcMZWFZs9fkz5P/ThPYbcFzVqIKtX9Wfa R3tsoM3+cIy3bcbitdWTVyvSnywQeLuODNnpUmSU=
From: Lars Eggert <lars@eggert.org>
Message-Id: <C1ADE976-219A-42C1-9399-152B99608E5E@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_620E3B40-F4BD-44BF-8D00-3D64DDA21EA9"; 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 10:46:46 +0200
In-Reply-To: <681a1e99-68a3-4079-b5fb-37d015c3722c@www.fastmail.com>
Cc: gendispatch@ietf.org
To: Martin Thomson <mt@lowentropy.net>
References: <A531C377-33A4-4138-BE28-788FF5FE267E@sn3rd.com> <681a1e99-68a3-4079-b5fb-37d015c3722c@www.fastmail.com>
X-MailScanner-ID: 792876002FE.AFB7D
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/NQqtuyE1J1o-yrtsofWJg1832rY>
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 08:47:02 -0000

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