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

Bron Gondwana <brong@fastmailteam.com> Fri, 12 February 2021 01:43 UTC

Return-Path: <brong@fastmailteam.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 867B73A1045 for <gendispatch@ietfa.amsl.com>; Thu, 11 Feb 2021 17:43:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level:
X-Spam-Status: No, score=-2.119 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_MSPIKE_H3=-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=gHEGBR9S; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=YUxUeP/U
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 iceQ9clouvMt for <gendispatch@ietfa.amsl.com>; Thu, 11 Feb 2021 17:43:23 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02A3D3A1047 for <gendispatch@ietf.org>; Thu, 11 Feb 2021 17:43:23 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 31E7E5C00CA for <gendispatch@ietf.org>; Thu, 11 Feb 2021 20:43:22 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Thu, 11 Feb 2021 20:43:22 -0500
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=fm1; bh=N2Z0DNf X67t+FaX23KKShxqqCzJIs11WYUPBdeamFYE=; b=gHEGBR9SNIRQBaiiCmoqgO6 iX6265qKSicoaLZxbwbtZLBsaMifm+OLccvM6kkwEw4piDw4wNPL6BADHkjNqt+4 E8ss+vmVjX3j11OvBN24/JzL9SY35FOxwtJ+VkCRjhdsCMGr5as5ldGxnvtKWNJy lbirD9sCHj+7/cFgwPDpV9XFFD985xCWaNLegQn3dhIDjk7VXnI+7MP+FjvF38uZ NGYhVlArPDa3WAuCGvmmsto47ZaP21almcXIDw2Ufqlp03nQtdbpAsEVqr1asJbp UIJWDQ4bepQjoH4Sl1Y/uI8bcvfu39h778f85pb+235e0Aw6v8Yzn67OoIH+iMw= =
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=N2Z0DN fX67t+FaX23KKShxqqCzJIs11WYUPBdeamFYE=; b=YUxUeP/Ul/WLneTbcHNbVq VTmSvjr4x8taLmXGvwnK1oiPOtPkYKMTADP2eLB4kYJ6AYI0mLwcO/fX0MzjIMS3 CwQRJmfjyWZULVj5wNWtiVIYKbuukdbO6TfEmNC4BCa6/BRqPMAbcOF1/g/01kZf 4ZdHVw0VZ05vkzpzQOojLAhaccKcSL/1eKa9Ru3Ktw0xar3oU5sw60TWDwhVqWj6 xfQY1C6j3DPTmnflaXqhLhzzOKnaDzL0npSCFspAgqGrqd19jSPSQ2jME0KwOscX FRQlI8PQnFU+ACJCkw2CUEv2JEnWMpEzVJT7ueSB9LIa3+iADOrL+fRsiCaoevrg ==
X-ME-Sender: <xms:Od0lYDBbqEhpseAgEEQ1aTzv8ig5w4EhlaRgfheTMviSSx1Ew_WbAg> <xme:Od0lYJgP0ill_pUVd8zZKjXObPFNWT1hfaWgQufHbIcCm0lE1rwf8IM-fW6bEfs51 EPhlBMjOZs>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledriedtgdeflecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreerjeenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehf rghsthhmrghilhhtvggrmhdrtghomheqnecuggftrfgrthhtvghrnheptdehteegfeevte duffevteehfffghefhvdevkeeuhfehueetudehgfegieekjeetnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgrih hlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:Od0lYOmL869Pj286bZIXWo78vJQx8Qdr3DrBkDbgK1Z3wzGc6h2u3Q> <xmx:Od0lYFxUFQiO_l7wlrMkPI7XVGap8fXV0-C1w151f9lJ0ojEMtEAYQ> <xmx:Od0lYIRX82OFfWE1GgswfSQLt3E5QdN0Ecc14J4MvBDSeX81AIgCNw> <xmx:Ot0lYPf7lniVL7fiwTGfWaGwaAYfCWQEAca81YUV4NLigxUl5FZqMA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 2FFD3360062; Thu, 11 Feb 2021 20:43:21 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-141-gf094924a34-fm-20210210.001-gf094924a
Mime-Version: 1.0
Message-Id: <566a9702-5ce9-448d-93b0-05a787978adc@beta.fastmail.com>
In-Reply-To: <A531C377-33A4-4138-BE28-788FF5FE267E@sn3rd.com>
References: <A531C377-33A4-4138-BE28-788FF5FE267E@sn3rd.com>
Date: Fri, 12 Feb 2021 12:43:00 +1100
From: Bron Gondwana <brong@fastmailteam.com>
To: gendispatch@ietf.org
Content-Type: multipart/alternative; boundary="195becab557f429aa9089c793409ef9d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/deuGYyu6D779vrHKcw4tPfc6DUo>
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: Fri, 12 Feb 2021 01:43:25 -0000

On Fri, Feb 12, 2021, at 07:39, Sean Turner wrote:
> Hi!,
> 
> Here is some proposed charter text to address the terminology-related WG.
> 

Thanks, this looks really good.  I gave some feedback on an earlier version of this, and it looks like every edit has improved it.

> 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.

This is fantastic.  It's grounded in the underlying purpose of the IETF, and it's clear about why this work is being undertaken.

> 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. 

I hadn't suggested naming specific terms, but seeing them there I think that having the examples improves this charter, because specific cases are always more useful than generic, all encompassing phrases ("certain terms") in isolation.

> 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 was holding out for ETERM (not to be confused with the enlightenment terminal manager) :p

Cheers,

Bron.

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