IETF Logo Mail Archive

Re: [Terminology] Guidance for NIST Staff on Using Inclusive Language in Documentary Standards (NISTIR 8366)

"Rodney W. Grimes" <ietf@gndrsh.dnsmgr.net> Sat, 01 May 2021 16:07 UTC

Return-Path: <ietf@gndrsh.dnsmgr.net>
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 38BB03A1FBE; Sat, 1 May 2021 09:07:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.4, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
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 1Pn7DbyzrkXJ; Sat, 1 May 2021 09:07:53 -0700 (PDT)
Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AA183A1FC0; Sat, 1 May 2021 09:07:52 -0700 (PDT)
Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 141G7pLu021952; Sat, 1 May 2021 09:07:51 -0700 (PDT) (envelope-from ietf@gndrsh.dnsmgr.net)
Received: (from ietf@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 141G7nqr021951; Sat, 1 May 2021 09:07:49 -0700 (PDT) (envelope-from ietf)
From: "Rodney W. Grimes" <ietf@gndrsh.dnsmgr.net>
Message-Id: <202105011607.141G7nqr021951@gndrsh.dnsmgr.net>
In-Reply-To: <B78DCC10-E53B-4995-A3A8-B3BE9E0557A1@akamai.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Date: Sat, 01 May 2021 09:07:49 -0700
CC: John Levine <johnl@taugh.com>, "terminology@ietf.org" <terminology@ietf.org>, "npdoty@ischool.berkeley.edu" <npdoty@ischool.berkeley.edu>
X-Mailer: ELM [version 2.4ME+ PL121h (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/QGPa9FSWU-gu2iwdRm8otKB3UYg>
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:07:54 -0000

> >   I think this document is better than anything we are likely to come up with on our own,
>     and it would align our practices with other SDOs, so I encourage us to adopt it and
>     turn our attention to other issues of IETF culture.
> 
> Totally agree.  Glad to see emerging consensus for this.  Lars, how do we make that happen, procedurely?

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.

-- 
Rod Grimes                                                 rgrimes@freebsd.org

v2.23.0 | Report a Bug | By Email