Re: [Terminology] Guidance for NIST Staff on Using Inclusive Language in Documentary Standards (NISTIR 8366)
"Salz, Rich" <rsalz@akamai.com> Sat, 01 May 2021 16:28 UTC
Return-Path: <rsalz@akamai.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 D23473A2049 for <terminology@ietfa.amsl.com>; Sat, 1 May 2021 09:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.8
X-Spam-Level:
X-Spam-Status: No, score=-2.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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 (2048-bit key) header.d=akamai.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 TATdPuDJXpgi for <terminology@ietfa.amsl.com>; Sat, 1 May 2021 09:28:24 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A16ED3A2048 for <terminology@ietf.org>; Sat, 1 May 2021 09:28:24 -0700 (PDT)
Received: from pps.filterd (m0050093.ppops.net [127.0.0.1]) by m0050093.ppops.net-00190b01. (8.16.0.43/8.16.0.43) with SMTP id 141GQGki031930; Sat, 1 May 2021 17:27:21 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=kN7rYDM7/21okXXP17xVdzrTVLWV89jnVC598syMr+g=; b=VumgUUIEmUB4yzgX3K5wzptA13VfqDHOZC0J05vXgrHxsGRuherePER3u5a9kMtQn2F+ usy1Som2Rz6LxxJJYP7Mo8VWAc8L9Fdce95Sx4xxnP2cMGOqa8x912aHGyYyMmYOgkbx hLGzlO9VkWqOLXA7Rn07G0a8antZAdHO6O9JHKThTYXUKzWvq3gwm5oydjKoraoFKyOx WZ5teFhDB58FO9TVNYaZPaIjnwU+D19chI3ZfeAnMvGCgjPcqdfwF4rd+pCqDwPDqZyT fGQVVCr9nyXlizXYqi5Z+BtbBvs+AqPgv1yEsgzp5+R1JRU1xnYHd6I4SBMWUEE/tsB3 vQ==
Received: from prod-mail-ppoint5 (prod-mail-ppoint5.akamai.com [184.51.33.60] (may be forged)) by m0050093.ppops.net-00190b01. with ESMTP id 3896n5nxh9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 01 May 2021 17:27:21 +0100
Received: from pps.filterd (prod-mail-ppoint5.akamai.com [127.0.0.1]) by prod-mail-ppoint5.akamai.com (8.16.1.2/8.16.1.2) with SMTP id 141GK7Ue019944; Sat, 1 May 2021 09:27:19 -0700
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint5.akamai.com with ESMTP id 3894ybrrpv-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sat, 01 May 2021 09:27:19 -0700
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag3mb6.msg.corp.akamai.com (172.27.123.54) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 1 May 2021 12:27:18 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb5.msg.corp.akamai.com (172.27.123.105) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 1 May 2021 12:27:18 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.012; Sat, 1 May 2021 12:27:18 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: "Rodney W. Grimes" <ietf@gndrsh.dnsmgr.net>
CC: John Levine <johnl@taugh.com>, "terminology@ietf.org" <terminology@ietf.org>, "npdoty@ischool.berkeley.edu" <npdoty@ischool.berkeley.edu>
Thread-Topic: [Terminology] Guidance for NIST Staff on Using Inclusive Language in Documentary Standards (NISTIR 8366)
Thread-Index: AQHXPTCpUoAW1JYTgk64HfR79e0UPqrODMsAgACl+QCAAF4sgP//wmEA
Date: Sat, 01 May 2021 16:27:17 +0000
Message-ID: <C626C4F0-A770-4DDF-A757-E0DB0C63895D@akamai.com>
References: <B78DCC10-E53B-4995-A3A8-B3BE9E0557A1@akamai.com> <202105011607.141G7nqr021951@gndrsh.dnsmgr.net>
In-Reply-To: <202105011607.141G7nqr021951@gndrsh.dnsmgr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.48.21041102
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.118.139]
Content-Type: text/plain; charset="utf-8"
Content-ID: <3EEC9D31F3F7844A9481F49330A8ECFF@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-05-01_13:2021-04-30, 2021-05-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 mlxlogscore=999 phishscore=0 malwarescore=0 mlxscore=0 suspectscore=0 spamscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104060000 definitions=main-2105010116
X-Proofpoint-ORIG-GUID: IDglTklp0DXJBKt1di-IZhzG_q8tTA-J
X-Proofpoint-GUID: IDglTklp0DXJBKt1di-IZhzG_q8tTA-J
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-05-01_13:2021-04-30, 2021-05-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 phishscore=0 lowpriorityscore=0 mlxlogscore=999 spamscore=0 mlxscore=0 adultscore=0 suspectscore=0 bulkscore=0 impostorscore=0 priorityscore=1501 clxscore=1011 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104060000 definitions=main-2105010117
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.60) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint5
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/lRKEZIpJEIXZVnrrBjpRJorYCSc>
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: Sat, 01 May 2021 16:28:29 -0000
> I partially agree. It is good in its content and forum EXCEPT it refers to what we know to be unpublished drafts of the IETF, the fact that it appears to have used such input is bothersome to me. The fact that it published such references in a standards document is beyond me. Did you read the section? It says: Terminology, Power, and Inclusive Language in Internet-Drafts and RFCs is currently an internet draft that does not reflect IETF consensus. This document suggests how editors of Internet-Drafts and RFCs can and should avoid exclusionary language and incorporate alternative, inclusive language in order to improve technical IETF documentation. "does not reflect IETF consensus" It covers other "in progress" efforts to, such as GitHub renaming, ISO report that was submitted but not approved, etc. And the whole thing isn't a standard (like AES, etc). It's a document to provide guidance.
- [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