IETF Logo Mail Archive

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

Bron Gondwana <brong@fastmailteam.com> Fri, 30 April 2021 04:39 UTC

Return-Path: <brong@fastmailteam.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 A9F9A3A0FE2 for <terminology@ietfa.amsl.com>; Thu, 29 Apr 2021 21:39:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.819
X-Spam-Level:
X-Spam-Status: No, score=-2.819 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=ViAG/uvf; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=c5n+5hc4
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 YZxP2rGdOqnp for <terminology@ietfa.amsl.com>; Thu, 29 Apr 2021 21:39:23 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2A2C3A0FDE for <terminology@ietf.org>; Thu, 29 Apr 2021 21:39:22 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 703895C00B1 for <terminology@ietf.org>; Fri, 30 Apr 2021 00:39:19 -0400 (EDT)
Received: from imap41 ([10.202.2.91]) by compute2.internal (MEProxy); Fri, 30 Apr 2021 00:39:19 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm2; bh=4LPEewD FBfjBizzivY9UqjpR98Ew2ZwoQNfPxl31RhM=; b=ViAG/uvfovmOqh4bqal062d +KJjqlt9UTpdua5osQh+wq2Ius1R/y0AFq1YSTGCbOLcQ3dntbIaDjqd2JI9Ke+9 VyBvBoXYJ0CE2he+2ffY5A0X1l9DQXS4VPcEqzWu8I5f9XcorSWSumabZ50jXmnQ MRcNxCeY/fp8zBL8J4pY5rNy4ASV2puL0cGg6lfKhCJuKe1uV0BVxOVU3/9GPWyF A4UAtXRQ6fuj9KaqhNCIQ6VrnmW059uMepy8rLG1SOIR6vcBrfW++THbtO+rLwmU KI65iFKoPd1elUTB+R95V7AOVxaK7e1oZjhaP5CjZW12WuuQRyDGsKR6UnmI9vg= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=4LPEew DFBfjBizzivY9UqjpR98Ew2ZwoQNfPxl31RhM=; b=c5n+5hc4D6KoNdkdsqeMhr uDq3XTcRfq8All0UGriMZ26az3Vpj60FsBr2DvNEw+WtKkgOQMY7H3xrl/zyFBhZ UUmtDzVT0FQFrQwrvVsZm0tyqb1FjAvTXjGcLgiYOuArn2q9dbx/SKAb+aF8aI1A 2+cRIN9r4UX1fONgq7pRrVOatadvy9/+Vkq/9zuAqoYnqeFPX11op60sqleFlYqN HHJnUE41Z68NmBbGziWp9TimF1lH/1g1p4oY///4FJmIlyLCgv335AKgQBBpQamq zei5s171Dkwg1D9cfdeIzBLJzW4nrqQL5T3UP6bZdxBLXWzyyB/B2Zh9HsUzn1LQ ==
X-ME-Sender: <xms:9omLYA4jzLZKwPX6hXl52AQgbGwW30TdoT4sAgp8Cgk9wgbWh6Nkzw> <xme:9omLYB6dR_lhkQhoi4eGG6FKeKvh1lyUizP8lkRK3EGNIOQfT1Hu6jQx8pFa6ASci nj38EB-eWE>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddvhedgkeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerreejnecuhfhrohhmpedfuehrohhnucfiohhnugifrghnrgdfuceosghrohhnghes fhgrshhtmhgrihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpeffvdekfeegle eiueettddtffehveevffefkeduvddttdekiefgjeduvdfhvdduleenucffohhmrghinhep ihgvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:9omLYPcxr02h8cjnoUiaGPz5eRRHhwlc7VFBNr_mOR30PZ0FtjeveA> <xmx:9omLYFKcEwH8tFuQ37u1cXE9Q4D2FJsXQdvW_Bie2NlIHDbK3Qt-Ow> <xmx:9omLYEL_poe6Tk7L5pVqHiaIifWe2Vxc1o9TsJvXynbAToJAYWzg-Q> <xmx:94mLYJWhbKnW0bxHWMpJCKQZS7mU0hzq_AuZwAFxwuDWIj_vFeW_vQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id BF234260005F; Fri, 30 Apr 2021 00:39:18 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-417-gd9086194d0-fm-20210426.001-gd9086194
Mime-Version: 1.0
Message-Id: <e666205a-2959-45a7-aaed-7f255349515a@dogfood.fastmail.com>
In-Reply-To: <46fc982794dd800e3a37e260f2be520e@cogitage.pairsite.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> <46fc982794dd800e3a37e260f2be520e@cogitage.pairsite.com>
Date: Fri, 30 Apr 2021 14:38:58 +1000
From: Bron Gondwana <brong@fastmailteam.com>
To: terminology@ietf.org
Content-Type: multipart/alternative; boundary="bde89421b70b4e78ac4155453f1229a5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/vYdrVWVOsWmsweDaZP8ygfqNU6o>
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 04:39:29 -0000

Relying on external content is always going to be a thing, given that we're adapting to a changing world with this work.

If there's anything approaching consensus on "reference NIST and be done with it" then I'm all in favour of dropping my draft and getting my focus back to helping my working groups progress their work!  I'd be well happy for the TERM working group to never form and for us to take our energy elsewhere.

Cheers,

Bron.

On Fri, Apr 30, 2021, at 11:00, reynolds@cogitage.pairsite.com <mailto:reynolds%40cogitage.pairsite.com> wrote:
> 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
> 
> -- 
> Terminology mailing list
> Terminology@ietf.org <mailto:Terminology%40ietf.org>
> https://www.ietf.org/mailman/listinfo/terminology
> 

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com

v2.23.0 | Report a Bug | By Email