Re: [Gendispatch] draft charter text: terminology-related WG

Eric Rescorla <ekr@rtfm.com> Thu, 11 February 2021 21:57 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 680A13A0C98 for <gendispatch@ietfa.amsl.com>; Thu, 11 Feb 2021 13:57:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=rtfm-com.20150623.gappssmtp.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 E09GzyvxPh4c for <gendispatch@ietfa.amsl.com>; Thu, 11 Feb 2021 13:57:26 -0800 (PST)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 6A5653A0C77 for <gendispatch@ietf.org>; Thu, 11 Feb 2021 13:57:26 -0800 (PST)
Received: by mail-lj1-x22d.google.com with SMTP id a25so9263467ljn.0 for <gendispatch@ietf.org>; Thu, 11 Feb 2021 13:57:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EfZv2CEOo+MpJXl1v3RvJneBWA8fGRGkZQy897W/aag=; b=eISnOlu0SAx7tFTcaTFJPcjP94EGsQCY9kQZeZ0EXTyzmgasIJibS06S9vvV30sOGf G7IumgQMLGPaTeBhXa/+Px9Cuu88GfSlHvEjcUaCpt/lkqxTC6lyVqbArRK6IVxmWv+e Y79QBLZcIj8Zr9H447Gy5z5jGLe22Tu9gDqd3gmgt81MoHQDStyfEWWg/O1ShQp7FaYO 1WijHTbKJRT/kY8fd8OpWJ5xgG2Jxcr9oFW7eodxvW45ch59MC08yJ3CLvuY/lfaiEKx DuiTQgGtamRnkmqyZx7acqwv5Mrn9pcH0uENDv+qq02LkkJAO58lWVwbwOhGhZskOsz+ olfg==
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=EfZv2CEOo+MpJXl1v3RvJneBWA8fGRGkZQy897W/aag=; b=r6F3/L4VqB/otUmJlBhtbvasRwC5G8h475jFAjz0MECIx4vj+0iNeEwvKl0GYOxec0 fkN2PXzBOydPCcmVAanyzhaZ1NPO3YhUrD1Mc7hPYas6ymJVxZWFRxZlmcXayGZfln8i nXqvAp27DGcmS0Is9Kqmxe2ukl08z/+XoBx/ZpEOqJuOX62A1+TLmySDsoPOidLTPH1L e4f19vMKVO177y8DPdFXl4bHlA4IoYYgW6eDmrmPJSzHjwc5no8o/tRFXmz2/T/jCXUk qLh25kD7RN4oKr48ptvv5Puys4snHca/OLuhZWcRFgVVqoAE/MxnwRGLlWvJvPht01bk PD5w==
X-Gm-Message-State: AOAM5317UccPXV5UHaozDnI0L8dlUOP7M6qNWkM4820cXnR90KSL/Ndm tWJcRyshPPG9i4ophrm/0baBx1NNr1fRT3nCHfdTdaAFEwq/vg==
X-Google-Smtp-Source: ABdhPJwiY0LTcliT2SM3o7mswwhUj5jhwKvg36FIScmBd+lK4xS8pcOyvxAb+NgqjA9eSBKbCs/6fP/9zwxrodW6PaI=
X-Received: by 2002:a2e:9cd5:: with SMTP id g21mr6073759ljj.383.1613080644469; Thu, 11 Feb 2021 13:57:24 -0800 (PST)
MIME-Version: 1.0
References: <A531C377-33A4-4138-BE28-788FF5FE267E@sn3rd.com>
In-Reply-To: <A531C377-33A4-4138-BE28-788FF5FE267E@sn3rd.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 11 Feb 2021 13:56:48 -0800
Message-ID: <CABcZeBPxQrzQZZ2ec+cvpovdkJaXcQ4f8Ged7Om1QPg7UrZ_Ew@mail.gmail.com>
To: Sean Turner <sean@sn3rd.com>
Cc: GENDISPATCH List <gendispatch@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ced77905bb169a8d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/EqyH0RGeP1etbMaX2pdh594aE34>
Subject: Re: [Gendispatch] draft charter text: terminology-related WG
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2021 21:57:28 -0000

On Thu, Feb 11, 2021 at 12:39 PM Sean Turner <sean@sn3rd.com> wrote:

> Hi!,
>
> Here is some proposed charter text to address the terminology-related WG.
>
> Cheers,
> spt
>

This looks like a great start. A few small comments below.


Effective Terminology in IETF Documents (TERM)
> ----
>
> The mission of the IETF as specified in BCP 95 is to produce high quality,
> relevant technical documents that influence the way people design, use, and
> manage the Internet. As RFC 7322 explains, "The ultimate goal of the RFC
> publication process is to produce documents that are readable, clear,
> consistent, and reasonably uniform." RFCs and Internet-drafts are most
> effective when they use terminology that is clear, precise, and widely
> accessible to readers from varying backgrounds and cultures.
>
> In the years leading up to the chartering of this working group, there has
> been discussion in the IETF, in other standards organizations, and in the
> technology industry about the use of certain terms (such as “master/slave”
> and “blacklist/whitelist”) in technical documentation and whether those and
> other terms have effects on inclusivity. While opinions vary among IETF
> participants about this topic, there is general agreement that the IETF
> community would benefit from informational recommendations about using
> effective and inclusive terminology in IETF documents.
> The TERM working group is therefore chartered to produce an Informational
> RFC containing recommendations on terminology to use in technical work
> produced by the IETF.
>

I think it might be helpful to scope out a little more what this RFC might
contain. Perhaps:

These recommendations will consist of (1) general principles for judging
when language is inclusive or exclusive (2) a list of specific terms to
avoid and recommendations for alternatives.

-Ekr


> Milestones:
>
> July 2021: Adopt draft providing informational terminology recommendations
>

I almost never say this, but it seems to me that this milestone isn't
aggressive enough. Also, shouldn't we have a "publish" milestone?

-Ekr

-- 
> Gendispatch mailing list
> Gendispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/gendispatch
>