Re: AUTH48 and "Guidance for NIST Staff on Using Inclusive Language in Documentary Standards"

S Moonesamy <sm+ietf@elandsys.com> Sun, 08 June 2025 21:45 UTC

Return-Path: <sm@elandsys.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 AA9B3326EC37; Sun, 8 Jun 2025 14:45:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
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 bQYTO02dZRDS; Sun, 8 Jun 2025 14:45:18 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mail2.ietf.org (Postfix) with ESMTP id BF485326EC34; Sun, 8 Jun 2025 14:45:18 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.124.188]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 558LijKE013286 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 Jun 2025 14:45:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1749419116; x=1749505516; i=@elandsys.com; bh=lKvCAoQksxiCutKKtkoURwyetVCxfX+i5Qi2htTTGtg=; h=Date:To:From:Subject:In-Reply-To:References; b=Dfx+tmeUQ7mZhGIt7MPrHQgcN/pIMuLGgoa2W74edf3JZ+JFx6QKJFPBWd4yD041v /59ebfoZB/4I27XjNu22oLoq+LFdEZZDP+lQd78PPZ5VvfZZUF8UhLpxxA4ndrr3Nj 50/FAhbq9AdVNNWSCATRZ5GE4CFGS1qfIZPygX6Q=
Message-Id: <6.2.5.6.2.20250608131812.0ac6dba8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 08 Jun 2025 14:42:32 -0700
To: Jay Daley <exec-director@ietf.org>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: AUTH48 and "Guidance for NIST Staff on Using Inclusive Language in Documentary Standards"
In-Reply-To: <2490CD28-A5C5-4819-8806-E8D6CF81BEE9@ietf.org>
References: <CAMEWqGtvD8ATWhgYjeVwmBjW7ZUtcVccSKLqdin=7W_UL7Dm7A@mail. gmail.com> <6.2.5.6.2.20250604152828.0dd1eec0@elandnews.com> <63700684BE1124344C81DAE2@PSB> <6.2.5.6.2.20250605003009.0e1b0728@elandnews.com> <CFF09C22-60C7-4932-A987-F2784B56F2F5@juniper.net> <2490CD28-A5C5-4819-8806-E8D6CF81BEE9@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: EERM7WSGCYVOOPNZBFOTJ2XT322LJ6XM
X-Message-ID-Hash: EERM7WSGCYVOOPNZBFOTJ2XT322LJ6XM
X-MailFrom: sm@elandsys.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
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/bGGV4yrNLHnJjXdw1-y0Z3lvBYY>
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>

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".
>
>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".

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.

According to NIST PR 1502.01, "The withdrawn publication and cover 
page will remain at the same DOI, unless it is determined that the 
publication should be removed from distribution."  The document which 
you cited could be removed from distribution or amended if the 
publisher wishes to do that.

As for what is "plain and precise", that is influenced by the needs 
of the organization, e.g. the organization aims to fulfill the needs 
of a country.  From what I understand, the issue here is about what 
are the appropriate words to use in an IETF RFC.  It is awkward to 
tell someone who has been writing in English for several years how to 
write in English.  It can also cause some debate, e.g. please see the 
thread at 
https://mailarchive.ietf.org/arch/msg/rfc-interest/iUbkutdNpXYgua8kejbsa63ZMv

Regards,
S. Moonesamy