IETF Logo Mail Archive

Re: [Terminology] [Gendispatch] WG Review: Effective Terminology in IETF Documents (term)

Keith Moore <moore@network-heretics.com> Fri, 30 April 2021 00:58 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: terminology@ietfa.amsl.com
Delivered-To: terminology@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA6973A1A91 for <terminology@ietfa.amsl.com>; Thu, 29 Apr 2021 17:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 EIy554QTSpGE for <terminology@ietfa.amsl.com>; Thu, 29 Apr 2021 17:58:47 -0700 (PDT)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B2E43A1A8E for <terminology@ietf.org>; Thu, 29 Apr 2021 17:58:47 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id E4A1F1682 for <terminology@ietf.org>; Thu, 29 Apr 2021 20:58:45 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 29 Apr 2021 20:58:46 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=yVIb/h KGFpXLI8y0TEm7JP+VvQWGw4rdLo7P5JeLxWI=; b=k1gpGxh+etiMsWd0+yZvNZ BBpO27hxSoQME/APnbqX+fFVSa9L93Mh1WHJUi2ahdXqgnjivsF/GrDM0Mgip4/Q wH3PG4gbA3ITWxJKy2bphmksMifU/1n/LiT55Ab1lo9D8G2JwjsvU1gqwkE9uyaO th+7sAfN5ryn3V8ahwaGO/HOmD5QzLMh7LkCJw3yL4iOpVQYhkzd2N0pNf+ECmEy Z2ej8wwMkAMleKHBvay6hXRIiH9iWINXf58V7sOwgtCcdZBlUArb4aQLC3/ezcax tQEjOaziL7HN3lWSEyXhbSxkMszvZqWz6A6+rIwGW5Jnq611h0ULN95nd2RKKK3g ==
X-ME-Sender: <xms:RFaLYGKCbQxsVxBB47ygfuq0JZdKgxpvhkCNpQ7IkCEpEAT3TJw1Nw> <xme:RFaLYOKrEiRu3POnHavUGGnDSqmrd7OqMg8Gye0njTbp29oTyAkC6UwWwkplkiFSU 9iPfHz4Cc4cFA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddvhedggedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgfrhhlucfvnfffucdlqddutddmnecujfgurhepuf fvfhfhkffffgggjggtsegrtderredtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgv uceomhhoohhrvgesnhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhmqeenucggtffrrg htthgvrhhnpeefhffgtdejieetueefgffhkefgkeeifffgffeukeegueevleehudfftefg feeigfenucffohhmrghinhepnhhishhtrdhgohhvnecukfhppeejfedruddufedrudeile driedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep mhhoohhrvgesnhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:RFaLYGuTGIq9OIdgLyssCJ-unPDGlr5Als5Ie2OCHz7QZl2_zj_XhQ> <xmx:RFaLYLZScNZD9UHcGOS-OCKTLnGy6SzY7AK1EWqKLMFs7fRkJQaNDg> <xmx:RFaLYNZ_LoiKEeRT0EdGJzP9dGsNryB3iL1PGSQlGfQtcGKgrDG21w> <xmx:RVaLYNqym8glWY7WDyvjPiaN2DLjf27xOaDOX3DULo_IQVl8R-p_uA>
Received: from [192.168.30.202] (c-73-113-169-61.hsd1.tn.comcast.net [73.113.169.61]) by mail.messagingengine.com (Postfix) with ESMTPA for <terminology@ietf.org>; Thu, 29 Apr 2021 20:58:44 -0400 (EDT)
To: terminology@ietf.org
References: <161918836800.7390.6996403788262551415@ietfa.amsl.com> <2563B42A-20A4-4A9F-B9CA-518A72A0A095@eggert.org> <5ecee462-e42b-ef6f-3841-4a33facf0e29@digitaldissidents.org> <a7628390-7f29-1d05-8509-ae008458894a@network-heretics.com> <3A01021B-3654-4DB3-8036-CA7FB961386A@akamai.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <09220069-8c3d-560a-4d56-b9272a7957f2@network-heretics.com>
Date: Thu, 29 Apr 2021 20:58:43 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <3A01021B-3654-4DB3-8036-CA7FB961386A@akamai.com>
Content-Type: multipart/alternative; boundary="------------79A34E9C0FB4C990EC782D4B"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/cfJTTHe06o0OJkpx7jmwhnZU8KQ>
Subject: Re: [Terminology] [Gendispatch] WG Review: Effective Terminology in IETF Documents (term)
X-BeenThere: terminology@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Effective Terminology in IETF Documents <terminology.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/terminology>, <mailto:terminology-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/terminology/>
List-Post: <mailto:terminology@ietf.org>
List-Help: <mailto:terminology-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/terminology>, <mailto:terminology-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Apr 2021 00:58:52 -0000

On 4/29/21 3:58 PM, Salz, Rich wrote:

>      > it is probably better to describe the actual situation, namely that the majority of the tech industry and other standards bodies have reached consensus on the topic, and the IETF is still making up its mind.
>
>>     IMO this is a bit unfair for multiple reasons.
> I would like to know why you think this is an unfair characterization.  Heck, even NIST has come out with a specification on this topic,https://nvlpubs.nist.gov/nistpubs/ir/2021/NIST.IR.8366.pdf  , "Guidance for NIST Staff on Using Inclusive Language in Documentary Standards"

I think it's making an argument not on its merits, but by appeal to 
fashion or herd mentality.    It also presumes that the framing of the 
topic is beyond question, when as far as I can tell it's extremely 
biased in such a way as to presume a particular answer.    There's more 
but I think I'll leave it at that.

Keith

v2.23.0 | Report a Bug | By Email