Re: AUTH48 and "Guidance for NIST Staff on Using Inclusive Language in Documentary Standards"
Michael De Roover <ietf@nixmagic.com> Mon, 09 June 2025 07:04 UTC
Return-Path: <ietf@nixmagic.com>
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 ED664328AA69; Mon, 9 Jun 2025 00:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham 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 GJqauANyQ_rm; Mon, 9 Jun 2025 00:04:59 -0700 (PDT)
Received: from nixmagic.com (e1.nixmagic.com [116.203.235.171]) by mail2.ietf.org (Postfix) with ESMTP id 2F4F1328AA61; Mon, 9 Jun 2025 00:04:58 -0700 (PDT)
Received: from smtpclient.apple (iphone.lan [192.168.10.29]) by nixmagic.com (Postfix) with ESMTPA id 2424811288A; Mon, 9 Jun 2025 07:04:58 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Michael De Roover <ietf@nixmagic.com>
Mime-Version: 1.0 (1.0)
Subject: Re: AUTH48 and "Guidance for NIST Staff on Using Inclusive Language in Documentary Standards"
Date: Mon, 09 Jun 2025 09:04:57 +0200
Message-Id: <674885D8-260B-44FD-A23D-796B170C6D6E@nixmagic.com>
References: <6.2.5.6.2.20250608131812.0ac6dba8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20250608131812.0ac6dba8@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>, Jay Daley <exec-director@ietf.org>
X-Mailer: iPhone Mail (19H384)
Message-ID-Hash: FIEI3ZSHYR5T27TV4OTRI67QWXVK5UBH
X-Message-ID-Hash: FIEI3ZSHYR5T27TV4OTRI67QWXVK5UBH
X-MailFrom: ietf@nixmagic.com
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
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/h2Uw22_XjWWRnkKH4A2IgFGL5Y8>
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>
On 8 Jun 2025, at 23:45, S Moonesamy <sm+ietf@elandsys.com> wrote: > > Hi Jay, > At 01:21 PM 05-06-2025, Jay Daley wrote: >> People may not be aware that while the guidance has been withdrawn, the table of examples included in the document has not: >> >> https://www.nist.gov/nist-research-library/nist-technical-series-publications-author-instructions#table1 >> >> That table is under a section titled "Plain Language" and is explained as "The table below displays how some sentences could be edited (or not) to incorporate plain and precise language.". e.g. replacing "whitelist" with "allowlist". I’ve seen this same thing happening in the IETF 5 years ago. It was not a good time to be here. These terms are so easily politicized, that they impede progress by creating even more unnecessary conflict. That is the exact opposite of efficiency. >> This framing of "plain and precise" could be considered clearer and less contentious (and therefore more likely to be adopted by authors) than the framing of "inclusive". Even if they do, the reason being entirely nontechnical feels wrong. National politics does not belong in an international standards organization. > A national standard fulfills the needs of a country. A non-national standard has a wider scope. An organization seeking to devise non-national standards usually brings together people affiliated with businesses from different countries. This is where the organization has to tackle problems such as language. The organization which was known as "IETF" used the English language for historical reasons. It attracted authors from different countries over the years. Some of the people reading their works might not speak English in their every day life. That does not necessarily mean that they do not know how to read or write in English. Seconded. Being Belgian, I would — quite frankly — rather see less American involvement of this sort at this point in time. We’ve been here before and I do not want to go back there again. Unilateral involvement of any one nation stops at its own borders. That’s as applicable for this little croissant I call home, as it is for everyone else. If we still want this organization to remain internationally neutral, that would require bilateral cooperation from everyone involved. Or to put it more bluntly: don’t tell the world what to do. Met vriendelijke groet, Michael De Roover Mail: ietf@nixmagic.com Web: michael@de.roover.eu.org
- AUTH48 and "Guidance for NIST Staff on Using Incl… Q Misell
- RE: AUTH48 and "Guidance for NIST Staff on Using … Adrian Farrel
- Re: AUTH48 and "Guidance for NIST Staff on Using … Brian E Carpenter
- Re: AUTH48 and "Guidance for NIST Staff on Using … Bob Hinden
- Re: AUTH48 and "Guidance for NIST Staff on Using … Brian Carpenter
- Re: AUTH48 and "Guidance for NIST Staff on Using … BRUNGARD, DEBORAH A
- RE: [Terminology] AUTH48 and "Guidance for NIST S… Julien Maisonneuve (Nokia)
- Re: [Terminology] AUTH48 and "Guidance for NIST S… Jim Fenton
- Re: AUTH48 and "Guidance for NIST Staff on Using … Nick Hilliard
- Re: [Terminology] AUTH48 and "Guidance for NIST S… Salz, Rich
- 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 … 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 … 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
- 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 … John Scudder