Re: Diversity and offensive terminology in RFCs

Paul Wouters <paul@nohats.ca> Thu, 20 September 2018 14:12 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 343A0130DEB for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 07:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] 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 cMw1-o8CZIxd for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 07:12:22 -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 62E9C130EA3 for <ietf@ietf.org>; Thu, 20 Sep 2018 07:12:20 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 42GJZp1j12zCws for <ietf@ietf.org>; Thu, 20 Sep 2018 16:12:18 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1537452738; bh=uztDjreR6vrrKxoyud2xLXlJ/xDT0OHqKAJ8hFwICfs=; h=Date:From:To:Subject:In-Reply-To:References; b=e0ddTNBMRut5JSsIhb+OC0ujKWiEjXu5TX67arAO/XezP+Nw/8peVcQgMU6z1kjLL KkBhx4Ccrnlrlq4UB1bkzZoqUDAxm9RMSUAJWF0Nbl9GmVZI/Zx1OQenOYnIVzBj+g 7sp4UO7TeqzpRMqOb5cSkXonRIQDxT4342exhe7w=
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 EYe5fhBojPJR for <ietf@ietf.org>; Thu, 20 Sep 2018 16:12:16 +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 for <ietf@ietf.org>; Thu, 20 Sep 2018 16:12:16 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 540B15602F8; Thu, 20 Sep 2018 10:12:15 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 540B15602F8
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 4860B424DCE7 for <ietf@ietf.org>; Thu, 20 Sep 2018 10:12:15 -0400 (EDT)
Date: Thu, 20 Sep 2018 10:12:15 -0400
From: Paul Wouters <paul@nohats.ca>
To: ietf@ietf.org
Subject: Re: Diversity and offensive terminology in RFCs
In-Reply-To: <927618083.13546501.1537450716082@mail.yahoo.com>
Message-ID: <alpine.LRH.2.21.1809201007540.12509@bofh.nohats.ca>
References: <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org> <927618083.13546501.1537450716082@mail.yahoo.com>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lnUDTGOB0ktGTQVX_0epi0C4EfU>
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: Thu, 20 Sep 2018 14:12:24 -0000

On Thu, 20 Sep 2018, lloyd.wood=40yahoo.co.uk@dmarc.ietf.org wrote:

> python has absolutely no problem favouring and promoting whitespace, which is racist as.
> whitespace is so important it gets to come first in the queue on the line. because it's white.

Since I use white text on a black screen, it is misnamed anyway! It's
blackspace for me!

We should call it blancspace obviously.

I also remember they had excellent coffee at IETF 95 Buenos Aires
at a place called Negro and it felt like a weird name to me until I
learned some more Spanish :P


Joking aside, Niels does bring a valid point, and it would be nice if we
got some guidelines for avoiding these existing known words, and prevent
us from creating new problematic ones.