Re: AUTH48 and "Guidance for NIST Staff on Using Inclusive Language in Documentary Standards"
Nick Hilliard <nick@foobar.org> Wed, 04 June 2025 11:48 UTC
Return-Path: <nick@foobar.org>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 630BF30AB03C; Wed, 4 Jun 2025 04:48:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -5.572
X-Spam-Level:
X-Spam-Status: No, score=-5.572 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-1.374, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id batf8ij5P5Bj; Wed, 4 Jun 2025 04:48:17 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [46.182.8.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D09F530AB02F; Wed, 4 Jun 2025 04:48:17 -0700 (PDT)
Received: from crumpet.local (vpn.ibn.ie [46.182.8.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.netability.ie (Postfix) with ESMTPSA id 2E0B4B061F; Wed, 04 Jun 2025 12:48:16 +0100 (IST)
Subject: Re: AUTH48 and "Guidance for NIST Staff on Using Inclusive Language in Documentary Standards"
To: Q Misell <q=40as207960.net@dmarc.ietf.org>
References: <CAMEWqGtvD8ATWhgYjeVwmBjW7ZUtcVccSKLqdin=7W_UL7Dm7A@mail.gmail.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <b47ea6ab-9135-414e-da48-8ac0dca1e3e0@foobar.org>
Date: Wed, 04 Jun 2025 12:48:14 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.65
MIME-Version: 1.0
In-Reply-To: <CAMEWqGtvD8ATWhgYjeVwmBjW7ZUtcVccSKLqdin=7W_UL7Dm7A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Message-ID-Hash: PTO25IRYLML2S4ZZ3ETSNGFRMM4BXZ4S
X-Message-ID-Hash: PTO25IRYLML2S4ZZ3ETSNGFRMM4BXZ4S
X-MailFrom: nick@foobar.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: ietf@ietf.org, terminology@ietf.org, The IESG <iesg@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BlU_FW0PeIGaZjv404J0b6FrG9E>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>
Q Misell wrote on 04/06/2025 11:26: > As a starting point, I suggest we > adopt the joint inclusive language guidance of the ISO and the IEC [1]; > as these are both well respected international standards organisations, > this maintains the stated goal of adopting NIST 8366 - in that the > language used in the IETF is standardised across industry [2]. is there much of a difference between the content of NIST 8366 and the ISO/IEC guidance document? If not, then go for it. If there are differences, then is there any possibility you would have a top-level summary? Also, thanks for pushing ahead with this ID, particularly in the circumstances. Nick
- RE: AUTH48 and "Guidance for NIST Staff on Using … Adrian Farrel
- AUTH48 and "Guidance for NIST Staff on Using Incl… Q Misell
- Re: AUTH48 and "Guidance for NIST Staff on Using … Brian Carpenter
- RE: [Terminology] AUTH48 and "Guidance for NIST S… Julien Maisonneuve (Nokia)
- Re: AUTH48 and "Guidance for NIST Staff on Using … Nick Hilliard
- Re: [Terminology] AUTH48 and "Guidance for NIST S… Salz, Rich
- Re: AUTH48 and "Guidance for NIST Staff on Using … Brian E Carpenter
- Re: AUTH48 and "Guidance for NIST Staff on Using … BRUNGARD, DEBORAH A
- Re: [Terminology] AUTH48 and "Guidance for NIST S… Jim Fenton
- Re: AUTH48 and "Guidance for NIST Staff on Using … Bob Hinden
- Re: [Terminology] AUTH48 and "Guidance for NIST S… Jean Mahoney
- Re: AUTH48 and "Guidance for NIST Staff on Using … S Moonesamy
- Re: AUTH48 and "Guidance for NIST Staff on Using … John C Klensin
- Re: AUTH48 and "Guidance for NIST Staff on Using … S Moonesamy
- Re: AUTH48 and "Guidance for NIST Staff on Using … John Scudder
- Re: AUTH48 and "Guidance for NIST Staff on Using … Jay Daley
- Re: AUTH48 and "Guidance for NIST Staff on Using … John Scudder
- Re: AUTH48 and "Guidance for NIST Staff on Using … S Moonesamy
- Re: AUTH48 and "Guidance for NIST Staff on Using … Benson Muite
- Re: AUTH48 and "Guidance for NIST Staff on Using … S Moonesamy
- Re: AUTH48 and "Guidance for NIST Staff on Using … S Moonesamy
- Re: AUTH48 and "Guidance for NIST Staff on Using … Benson Muite
- Re: AUTH48 and "Guidance for NIST Staff on Using … Michael De Roover
- Re: AUTH48 and "Guidance for NIST Staff on Using … Benson Muite
- Re: AUTH48 and "Guidance for NIST Staff on Using … Michael De Roover
- Re: AUTH48 and "Guidance for NIST Staff on Using … S Moonesamy
- Re: AUTH48 and "Guidance for NIST Staff on Using … S Moonesamy