Re: Diversity and offensive terminology in RFCs

Paul Wouters <paul@nohats.ca> Fri, 21 September 2018 15:20 UTC

Return-Path: <paul@nohats.ca>
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 B7C3E12777C for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 08:20:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 Mzd3kvlSyzMq for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 08:20:25 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8679130E69 for <ietf@ietf.org>; Fri, 21 Sep 2018 08:20:24 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 42Gy2s1pK1zF8M; Fri, 21 Sep 2018 17:20:21 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1537543221; bh=fvJibP9lp1H2RtwzdRnoul5B/cURV1ZhGcc2M61sL5U=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=PXRspId1HrgB6KaC2l0yYeVcgceexRyv/VEgzIlOZMx6WOjbeJvUqxrbgzkKvhG8D GnHJNEOHegrFcG1j3uEEjUyx2higJzJoHhGBsntYcWF0PUvgma6r6p7vI8ygBwKwaS 6CDsI3Bf+TGx05BsKo7pwlA0w7/f1pqPSX2mxW/Y=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id tFcXfMSQ-WbG; Fri, 21 Sep 2018 17:20:19 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 21 Sep 2018 17:20:18 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id CAFA82EEDB3; Fri, 21 Sep 2018 11:20:17 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca CAFA82EEDB3
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id BD2A2424DCCA; Fri, 21 Sep 2018 11:20:17 -0400 (EDT)
Date: Fri, 21 Sep 2018 11:20:17 -0400
From: Paul Wouters <paul@nohats.ca>
To: Anton Ivanov <anton.ivanov@kot-begemot.co.uk>
cc: ietf@ietf.org
Subject: Re: Diversity and offensive terminology in RFCs
In-Reply-To: <a6f254b2-c626-7d5e-3a06-df0950058ceb@kot-begemot.co.uk>
Message-ID: <alpine.LRH.2.21.1809211046380.1100@bofh.nohats.ca>
References: <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org> <FF2D6C92-F0C9-4FFB-BDF0-CB64D331415E@cooperw.in> <ae392f21-ba18-3e52-0c06-10e15d9b577d@digitaldissidents.org> <a6f254b2-c626-7d5e-3a06-df0950058ceb@kot-begemot.co.uk>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ocwJvFgViJV3GnyjKPAoTsyTzj0>
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, 21 Sep 2018 15:20:31 -0000

On Fri, 21 Sep 2018, Anton Ivanov wrote:

> Err... that is social "science" without a single number on it.

I hope Niels can add "quoting arbitrary words to imply they are not real" to
the list of questionable things not to write in an RFC or community list.

> At the very least quote an article with a statistically significant survey of 
> engineers who have been horribly offended by the use of "master/slave" 
> terminology. I would be interested to see one.

That is not the bar we are looking for. I think we are looking at replacing
words that have unnecessary bad connotations for a (small or big)
group of people, where doing so would not be to the detriment of the
technical specification (beyond an initial easy learning curve)

I don't think the onus is now on proving what a poor job language has
done to for example women. And you asking for more statistics seems like
putting up an unneccessary barrier to improve in an area where we have
nothing to lose if we improve it.

I am sure NASA is even better at longlived discussions and stalemates
than we are, and even they updated their History Program Office style
guide in 2006 to say "references referring to the space program should be
non-gender specific.". And even now, people (and especially journalists)
still refer to "manned flight". And that still partialy contributes to
women astronauts being asked about makeup[1] in 2015.

Paul
https://www.sapiens.org/column/wanderers/outer-space-and-gendered-language/