Re: [Terminology] Guidance for NIST Staff on Using Inclusive Language in Documentary Standards (NISTIR 8366)
Eliot Lear <lear@cisco.com> Fri, 30 April 2021 08:59 UTC
Return-Path: <lear@cisco.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 BBDB03A0147 for <terminology@ietfa.amsl.com>; Fri, 30 Apr 2021 01:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level:
X-Spam-Status: No, score=-9.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 VI-hHd4SmLJ4 for <terminology@ietfa.amsl.com>; Fri, 30 Apr 2021 01:59:41 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AC5D3A0128 for <terminology@ietf.org>; Fri, 30 Apr 2021 01:59:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2047; q=dns/txt; s=iport; t=1619773181; x=1620982781; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=D2H8oEcJOewHV+XduPlrNHCbQHvsfchfl21il6vvMsw=; b=PWmX6Uj7qgsb1u6KIpN9XqYtuKkWdc9JHdwcgUj2dH2uATLxcW8IDVhn Je+C/0tF+5tuiXDbeaeGkSWbrMM2AzXlx7LskwR/eljH4eDxmROr8+Vot PUpFyODGphnhsvdtqVeGNATOb5KCNjWe4q3Wtvllgz125f6vcYNAl/asP A=;
X-Files: signature.asc : 488
X-IPAS-Result: A0BaAADcxYtg/xbLJq1aGgEBAQEBAQEBAQEDAQEBARIBAQEBAgIBAQEBQIFXgXyBJlYBJxIxjUiITiUDnHcEBwEBAQoDAQEdCwwEAQGEDEQCgXwmOBMCBAEBAQMCAwEBAQEBBQEBAQIBBgRxE4VQDYZEAQEBAwEBAWwLBQsLGCMLJzAGExWCXAGCZiEPqEV4gTSBAYRhhQoKBoE6AYFSjARDgguBFScMEIFfUS8+gQSBXAEBhS2CCSIEgXSBNkcQEwFHaXaRU4xfnRiDGoNDgUiYHwUhlE2QUbUBAYQGAgQGBQIWgWsjgVkzGggbFTsqAYI+PhIZDo4rCwsVbQEJh1aFSz8DLzgCBgoBAQMJjQ8BAQ
IronPort-HdrOrdr: A9a23:CkimdKPsj6SPG8BcTkOjsMiAIKoaSvp033AA3SlKOH9oW+afkN 2jm+le6A/shF8qNE0ItNicNMC7IE/02oVy5eAqV4uKfA6jg2ewKZEn0I2K+V3dMgnz7PRU26 slU6UWMrDNJHx7icq/3wWiCdYnx7C8n5yAvuvVw3dzQQwCUcgJhDtRMQqVHlZ7QwNLH/MCZf +hz/BarDmtc2l/VKqGL0QCNtKzxeHjpdbDaR4CCwVP0njrsRqYrJjnDhOfwhASFxRIzLtKyx miryXJooO+rvq81hjQk1X20q0Tst7gxtxfbfb87fQoFg==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.82,262,1613433600"; d="asc'?scan'208";a="33179175"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 30 Apr 2021 08:59:36 +0000
Received: from [10.61.144.34] ([10.61.144.34]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 13U8xaJV005618 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 30 Apr 2021 08:59:36 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <A780D3C9-4E59-4D43-9413-24A6AA29D6C4@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_A50EE0D2-741A-4FE5-A554-5E0C7A8792A7"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Fri, 30 Apr 2021 10:59:34 +0200
In-Reply-To: <20210429212542.BAEAD5FD25D@ary.qy>
Cc: terminology@ietf.org, huitema@huitema.net
To: John Levine <johnl@taugh.com>
References: <20210429212542.BAEAD5FD25D@ary.qy>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
X-Outbound-SMTP-Client: 10.61.144.34, [10.61.144.34]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/6FO5MS9BZNTH3M0MC0ZG5FK34og>
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 08:59:47 -0000
+1. Eliot > On 29 Apr 2021, at 23:25, John Levine <johnl@taugh.com> wrote: > > It appears that Christian Huitema <huitema@huitema.net> said: >>> 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. >>> >>> (Clearly NIST is not international in scope, and the IETF is, but since >>> our shared working language is more or less American English, it seems >>> reasonable.) >> >> +1. One of the best ways to make progress quickly. > > Sounds good to me. > > The IETF has all sorts of problems with our long-standing culture of, ah, lack of consideration. > Terminology is about 1% of the problem so if this lets us get it out of the way so we can think about > working on the other 99%, all the better. > > R's, > John > > -- > Terminology mailing list > Terminology@ietf.org > https://www.ietf.org/mailman/listinfo/terminology
- [Terminology] Guidance for NIST Staff on Using In… Nick Doty
- Re: [Terminology] Guidance for NIST Staff on Usin… Keith Moore
- Re: [Terminology] Guidance for NIST Staff on Usin… Brian E Carpenter
- Re: [Terminology] Guidance for NIST Staff on Usin… Christian Huitema
- Re: [Terminology] Guidance for NIST Staff on Usin… John Levine
- Re: [Terminology] Guidance for NIST Staff on Usin… Andrew Campling
- Re: [Terminology] Guidance for NIST Staff on Usin… Keith Moore
- Re: [Terminology] Guidance for NIST Staff on Usin… reynolds
- Re: [Terminology] Guidance for NIST Staff on Usin… Bron Gondwana
- Re: [Terminology] Guidance for NIST Staff on Usin… Niels ten Oever
- Re: [Terminology] Guidance for NIST Staff on Usin… Eliot Lear
- Re: [Terminology] Guidance for NIST Staff on Usin… Lloyd W
- Re: [Terminology] Guidance for NIST Staff on Usin… Keith Moore
- Re: [Terminology] Guidance for NIST Staff on Usin… Joel M. Halpern
- Re: [Terminology] Guidance for NIST Staff on Usin… John Levine
- Re: [Terminology] Guidance for NIST Staff on Usin… Bob Hinden
- Re: [Terminology] Guidance for NIST Staff on Usin… Salz, Rich
- Re: [Terminology] Guidance for NIST Staff on Usin… Rodney W. Grimes
- Re: [Terminology] Guidance for NIST Staff on Usin… Salz, Rich
- Re: [Terminology] Guidance for NIST Staff on Usin… reynolds
- Re: [Terminology] Guidance for NIST Staff on Usin… Lloyd W
- Re: [Terminology] Guidance for NIST Staff on Usin… Eliot Lear
- Re: [Terminology] Guidance for NIST Staff on Usin… Phillip Hallam-Baker
- Re: [Terminology] Guidance for NIST Staff on Usin… Jari Arkko