Re: [Terminology] Guidance for NIST Staff on Using Inclusive Language in Documentary Standards (NISTIR 8366)
Keith Moore <moore@network-heretics.com> Fri, 30 April 2021 10:50 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 D46273A0FDE for <terminology@ietfa.amsl.com>; Fri, 30 Apr 2021 03:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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 OZV2tHmRzmjh for <terminology@ietfa.amsl.com>; Fri, 30 Apr 2021 03:49:57 -0700 (PDT)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 463BA3A0FE2 for <terminology@ietf.org>; Fri, 30 Apr 2021 03:49:56 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 8863911C1 for <terminology@ietf.org>; Fri, 30 Apr 2021 06:49:55 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 30 Apr 2021 06:49:55 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding: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=kNDIcgQdvIsQPS+7PCXqD+pqB5ph7ndQFdULTej1+ uo=; b=nACQRZd8wKdPUorWDlmq28EDi+wIMzCwFlLHpYjM+nH9PMFNRRu/SIWPs C2oic4JMtB21CmjmY1jcyY55mCt1zw3/REhUZyf1StWUrTha/+cgFemgM2vxkbGA 56pSrfmJBxPFx6hyigMSerR2VILKQG3a5o68n4xqro2aFDIb5HT1iLYDO8shvWwL CqB2rjrI2U60obUqtxwgISWzHpPa9Dv1L+xoGqhdo2h0mgtyXa8fWLqKclAbskAj aPU04T8q/80kR8ByCLLCdJ2rRGQwgjHhBwuN5HEWkfwJo6CA8eA3dsUckUxXmZjO PnqPVXawHMhXoFJ0HmjwrO3xvw3gA==
X-ME-Sender: <xms:0uCLYHMzvgkExrljDTmBt_pS1QG3S0UthGA1C3V4z9DH7yOBlaJhDQ> <xme:0uCLYB9WL3j6nQZ4ByyDq77wXyyAPcNYHVmFdrRUdjp7J5r6rOxtnMOEuIbUs_jUS 2-aHzEOBSKknA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddviedgfeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtje ertddtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthif ohhrkhdqhhgvrhgvthhitghsrdgtohhmqeenucggtffrrghtthgvrhhnpeekvdeggfelue elkeeuhfffheeghffhkeeuvdduudeihfehudefffdtgfdtkeffgfenucfkphepvdefrddu vdegrddutddrudejtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:0uCLYGTde_F7lqotdJgWJH-p2rWNE5Ptkybcyag-cHftTr8wdkaJwQ> <xmx:0uCLYLuHuC8n0gxPUGcsHu4OM9knhZkaFz5343wixTeUzoB00bqphQ> <xmx:0uCLYPeQK6IbE1HmlmDvW9nZxW2xYXZ5iSgcn-sHgk5PE-MdSesUsg> <xmx:0-CLYC8T8PEn9VbnzpqaMPyUtQrzdf_FMYHXRx3DbVs-jE3Qvp6ACw>
Received: from [192.168.1.121] (23-124-10-170.lightspeed.knvltn.sbcglobal.net [23.124.10.170]) by mail.messagingengine.com (Postfix) with ESMTPA for <terminology@ietf.org>; Fri, 30 Apr 2021 06:49:54 -0400 (EDT)
To: terminology@ietf.org
References: <c9f82250-8df4-6c5b-f71d-2559448fa06d@digitaldissidents.org> <66B2F126-4B4E-4536-920A-DD14FCDE8CB3@yahoo.co.uk>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <3628f7a2-f9d6-f21c-9d66-1c37dea54f02@network-heretics.com>
Date: Fri, 30 Apr 2021 06:49:53 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <66B2F126-4B4E-4536-920A-DD14FCDE8CB3@yahoo.co.uk>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/J0wvbcoQJQHw501gEt9Vyp_kXJY>
Subject: Re: [Terminology] Guidance for NIST Staff on Using Inclusive Language in Documentary Standards (NISTIR 8366)
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 10:50:02 -0000
On 4/30/21 5:07 AM, Lloyd W wrote: > Version control belongs with the RFC Editor function, where the RFC Editor can reference the NIST document and provide a level of indirection and any added guidance. +1
- [Terminology] Guidance for NIST Staff on Using In… Nick Doty
- Re: [Terminology] Guidance for NIST Staff on Usin… Keith Moore
- Re: [Terminology] Guidance for NIST Staff on Usin… Brian E Carpenter
- Re: [Terminology] Guidance for NIST Staff on Usin… Christian Huitema
- Re: [Terminology] Guidance for NIST Staff on Usin… John Levine
- Re: [Terminology] Guidance for NIST Staff on Usin… Andrew Campling
- Re: [Terminology] Guidance for NIST Staff on Usin… Keith Moore
- Re: [Terminology] Guidance for NIST Staff on Usin… reynolds
- Re: [Terminology] Guidance for NIST Staff on Usin… Bron Gondwana
- Re: [Terminology] Guidance for NIST Staff on Usin… Niels ten Oever
- Re: [Terminology] Guidance for NIST Staff on Usin… Eliot Lear
- Re: [Terminology] Guidance for NIST Staff on Usin… Lloyd W
- Re: [Terminology] Guidance for NIST Staff on Usin… Keith Moore
- Re: [Terminology] Guidance for NIST Staff on Usin… Joel M. Halpern
- Re: [Terminology] Guidance for NIST Staff on Usin… John Levine
- Re: [Terminology] Guidance for NIST Staff on Usin… Bob Hinden
- Re: [Terminology] Guidance for NIST Staff on Usin… Salz, Rich
- Re: [Terminology] Guidance for NIST Staff on Usin… Rodney W. Grimes
- Re: [Terminology] Guidance for NIST Staff on Usin… Salz, Rich
- Re: [Terminology] Guidance for NIST Staff on Usin… reynolds
- Re: [Terminology] Guidance for NIST Staff on Usin… Lloyd W
- Re: [Terminology] Guidance for NIST Staff on Usin… Eliot Lear
- Re: [Terminology] Guidance for NIST Staff on Usin… Phillip Hallam-Baker
- Re: [Terminology] Guidance for NIST Staff on Usin… Jari Arkko