IETF Logo Mail Archive

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

reynolds@cogitage.pairsite.com Fri, 30 April 2021 01:00 UTC

Return-Path: <reynolds@cogitage.pairsite.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 3CFDC3A1A9E for <terminology@ietfa.amsl.com>; Thu, 29 Apr 2021 18:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level:
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham 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 ZLpnaOy0hzkP for <terminology@ietfa.amsl.com>; Thu, 29 Apr 2021 18:00:10 -0700 (PDT)
Received: from www2.webmail.pair.com (www2.webmail.pair.com [66.39.3.96]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA18F3A1A9D for <terminology@ietf.org>; Thu, 29 Apr 2021 18:00:09 -0700 (PDT)
Received: from rc.webmail.pair.com (localhost [127.0.0.1]) by www2.webmail.pair.com (Postfix) with ESMTP id CDA651A0D88 for <terminology@ietf.org>; Thu, 29 Apr 2021 21:00:08 -0400 (EDT)
MIME-Version: 1.0
Date: Thu, 29 Apr 2021 21:00:08 -0400
From: reynolds@cogitage.pairsite.com
To: terminology@ietf.org
In-Reply-To: <7d5e3acd-c7a0-d9e2-31c6-de9ed8fc6bd0@network-heretics.com>
References: <CAFfrZstRpSrbc5X6OhPsAiiER1srh3aHEuS1sLYsghUJz4PO5g@mail.gmail.com> <7ab5d973-7c8e-cdaa-823b-d22395447455@network-heretics.com> <57eaa15c-9230-68f7-063e-4a5558106dd3@gmail.com> <7d5e3acd-c7a0-d9e2-31c6-de9ed8fc6bd0@network-heretics.com>
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <46fc982794dd800e3a37e260f2be520e@cogitage.pairsite.com>
X-Sender: reynolds@cogitage.pairsite.com
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/d3taxiJ00IGG2bBI6Q_IqAJ6RRQ>
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: Fri, 30 Apr 2021 01:00:11 -0000

Though relying on eternal content to serve also as internal oontent 
would require all the apparatus of constantly checking for 
modifications.

On 29.04.2021 20:50, Keith Moore wrote:
> On 4/29/21 4:50 PM, Brian E Carpenter wrote:
> 
>> Yes. The IESG could suggest to the RFC Editor team to add an 
>> informative
>> reference to the NIST document to the style guide, and remind the IETF
>> that Internet-Drafts should aim to adhere to the RFC style guide,
>> and we're done.
> 
> I think I'd be ok, maybe even happy, with that result.   As long as
> the reference were informative.
> 
> Presumably the RFC Editor would also be able to add other references
> that they deemed appropriate and useful for RFCs.
> 
> Keith

v2.23.0 | Report a Bug | By Email