Re: [Terminology] TERM & NISTIR 8366

Phillip Hallam-Baker <phill@hallambaker.com> Wed, 05 May 2021 00:14 UTC

Return-Path: <hallam@gmail.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 B0EBC3A1B60 for <terminology@ietfa.amsl.com>; Tue, 4 May 2021 17:14:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 A81hkDvSH-LB for <terminology@ietfa.amsl.com>; Tue, 4 May 2021 17:14:41 -0700 (PDT)
Received: from mail-yb1-f181.google.com (mail-yb1-f181.google.com [209.85.219.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 180EF3A1B5D for <terminology@ietf.org>; Tue, 4 May 2021 17:14:40 -0700 (PDT)
Received: by mail-yb1-f181.google.com with SMTP id g38so376877ybi.12 for <terminology@ietf.org>; Tue, 04 May 2021 17:14:40 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=f2rCZ83ygxVZZEhtbyWhc7DJ+Y6C6YDKnH1neSGyJjo=; b=WGUWDAaGGqTXO+2Aejx0D550+raeWiz6n3N0xKrV4svMZGRG3hkvKNS0sdpnq3QRD3 rfZ6Jt1j+iINNkwviIuuuL8KjErflbIa0y7CNmetop9UzU/Zf5rdH3ZgZbXa8QHcC58h Kqx8KoaR/6HlLIH71nvavV0PNMdmRvNq5X105w2uqmHxfn020R8DC9l7PpL2cXfqvngx twEU4mWAjxGnq6d6q797QTGBm6dNFc7Q/8iBV++vA8vk4FRi/GcS72GKgG0YcxoGjugm WjGUGYxUpodiyuubkAp60dzCoCsyzoy6DQLbpfGskRO6QqYWfiXf2c1akdQqxjBR0/Yj wMbQ==
X-Gm-Message-State: AOAM531cnBjKXMiSQyXmXrcaP+zWpaiu4Y1Vpwdsdvvdk6dsdnwcd7bg fqg8BvGCojGVgt96txVvM1Pskrkfo0O/iV2J2rg=
X-Google-Smtp-Source: ABdhPJwVlEC6ujZd3I12D7NT3zvU2M3no87GzjFZzDlbsq40Zp1w/Fb6yVCBjDa8B0xSuLw2sUl967fL0fM8w9TBzBQ=
X-Received: by 2002:a5b:e87:: with SMTP id z7mr15134170ybr.302.1620173679884; Tue, 04 May 2021 17:14:39 -0700 (PDT)
MIME-Version: 1.0
References: <0D099A46-15A9-4427-A587-262897D9A722@eggert.org>
In-Reply-To: <0D099A46-15A9-4427-A587-262897D9A722@eggert.org>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 04 May 2021 20:14:25 -0400
Message-ID: <CAMm+Lwg6eHsoS5=fu0wrGxft0rX2Gt9mEZS9bXsfuZ-0udp-Og@mail.gmail.com>
To: Lars Eggert <lars@eggert.org>
Cc: "terminology@ietf.org" <terminology@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a9fee705c18a14d4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/bjvGi30chKhQ7EerABUOcJeuanE>
Subject: Re: [Terminology] TERM & 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: Wed, 05 May 2021 00:14:46 -0000

The more I think about this, the better it looks. The only caveat is that a
future administration might be regressive.

While this ties us to the US govt on this, we use English as our working
language and produce English documents. The US is the second largest
English speaking country and the most diverse.

IETF has limited resources to commit to this, the US state dept has an
entire protocol department.



On Mon, May 3, 2021 at 6:15 AM Lars Eggert <lars@eggert.org> wrote:

> Hi,
>
> thank you all for the feedback over the last few days.
>
> It seems like we have broad consensus to refer to NISTIR 8366 (
> https://doi.org/10.6028/NIST.IR.8366) to provide guidance to IETF
> contributors on using inclusive terminology, in lieu of documenting our own
> guidance.
>
> I'm therefore planning to do the following:
>
> (1) abandon the chartering of the proposed TERM WG
>
> (2) suggest to the IESG to recommend NISTIR 8366 as guidance
>     to contributors to the IETF
>
> (3) suggest to the RFC Editor to recommend NISTIR 8366 as guidance
>     to authors of I-Ds and RFCs
>
> Thanks,
> Lars Eggert
> IETF Chair
>
> --
> Terminology mailing list
> Terminology@ietf.org
> https://www.ietf.org/mailman/listinfo/terminology
>