Re: A contribution to ongoing terminology work

Carsten Bormann <cabo@tzi.org> Fri, 02 April 2021 20:25 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BAD23A224A for <ietf@ietfa.amsl.com>; Fri, 2 Apr 2021 13:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level:
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 PixpzPeHQsH7 for <ietf@ietfa.amsl.com>; Fri, 2 Apr 2021 13:25:04 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F5F03A2247 for <ietf@ietf.org>; Fri, 2 Apr 2021 13:25:04 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FBs3y1NZcz1049; Fri, 2 Apr 2021 22:25:02 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: A contribution to ongoing terminology work
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <YGd2NZ5GH6Iv6TTE@straasha.imrryr.org>
Date: Fri, 02 Apr 2021 22:25:01 +0200
X-Mao-Original-Outgoing-Id: 639087901.606361-1913eb1e047e565f525405b1291e2d93
Content-Transfer-Encoding: quoted-printable
Message-Id: <7FC9CB85-0402-48F1-8091-7E8CF582ACDD@tzi.org>
References: <859352252.4167919.1617264911078.ref@mail.yahoo.com> <859352252.4167919.1617264911078@mail.yahoo.com> <85575541-C896-4530-B028-C0DF9BA3EA8B@ietf.org> <411426886.24320.1617306016731@appsuite-gw2.open-xchange.com> <20210401195735.GA3828@localhost> <20210402032059.GD79563@kduck.mit.edu> <YGd2NZ5GH6Iv6TTE@straasha.imrryr.org>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Rtv4XAZpDinPnACef9qA3URflbA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Apr 2021 20:25:08 -0000

On 2021-04-02, at 21:53, Viktor Dukhovni <ietf-dane@dukhovni.org> wrote:
> 
> proposed language policing

Hi Viktor,

I have a heck of respect for survivors of thought controlling dictatorships, so I’m not asking this lightly:

What the <> are you talking about?

Thank you.

(I have copied the proposed charter of the proposed WG below, for your perusal.
Skip the first two paragraphs, which are just background (*).  I can’t find a proposal for establishing a supreme soviet of terminology, and I trust that we won’t let the WG generate such a proposal in its Informational RFC.)

Grüße, Carsten

(*) Can we have headings in charters?  
So we separate background chatter from the actual charter?

https://datatracker.ietf.org/doc/charter-ietf-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. IETF documents, including 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 maximizes the
benefits the IETF derives from its core principles, such as its open process and
volunteer core.

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 the use of inclusive terminology in the technical
work produced by IETF participants. The RFC will express general principles for
assessing when language is inclusive or exclusive. The principles should match
the expectations from a diverse set of IETF participants. The WG will identify
and recommend an external, independently-updated resource containing examples of
potentially problematic terms and potential alternatives to IETF participants,
in order to align its efforts with broader activities by the technology
industry.

The TERM working group is a focused group aiming to produce a single
deliverable. It is designed to complement other efforts at fostering inclusivity
in the IETF and will liaise with appropriate external groups, such as other SDOs
or industry initiatives, to coordinate.