Re: Diversity and offensive terminology in RFCs

Dave Cridland <dave@cridland.net> Fri, 21 September 2018 16:45 UTC

Return-Path: <dave@cridland.net>
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 BFF69130E10 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 09:45:56 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
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 U_E9-kClo0Yr for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 09:45:54 -0700 (PDT)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 095561277CC for <ietf@ietf.org>; Fri, 21 Sep 2018 09:45:53 -0700 (PDT)
Received: by mail-lj1-x22f.google.com with SMTP id v26-v6so12237398ljj.3 for <ietf@ietf.org>; Fri, 21 Sep 2018 09:45:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3/IBRa97fPX5LEaaSjo1xcie8E63KkmufpkACzg34NY=; b=SAjzKvhTWoJpJJlutoa9qoNNoYH7lzmCViw/I61MPJ1ofmC2kfAvWygxncOU3tB7z5 ryHc53spisMc2wisKwSyDrTbu0yCTaUj151PQzXcBXZEAqArwIPh0WL7DwkQD8mSn+tK OhU/iY4UaNpKWz6wXDEsKf2sM8Ao4/IkJ2dO0=
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=3/IBRa97fPX5LEaaSjo1xcie8E63KkmufpkACzg34NY=; b=kT1lIfx+kTIOTfSIEQ1fus7pHpc5SrACZOnvoFp1f2jNeDHvM0sJLKW+bTDUO3KuLy TTSC7/ZkVUux7oMCuNhkxkOP9J/OfOASm+JGDTjkKNJLn1d5gi/Oy7Syh3puTjfOoxvl rvQQHLhsHLC/UzZWGw9OIMN0b9XGfHxJC2ow4SEcdqTRo8zfc6LYNnNPC2VrKrcCbOds L439jOijboj3t8spo8OLYPxsGLYWO7Gp75JXzEaPTq6Q4iLnBsRr5pjEzHEjcVJeXrWz K0wTx0eWhE8wcaDIxIBncpOY6NPoDhwk8os5lHW0GS9GCCi9aNZYb/T7FLj96QkTAIio IINw==
X-Gm-Message-State: ABuFfogBx9AsBBNmuWKLhjnzY3u36Atz9UYtFCmmJlGvzl2VT/52/fuD Qi6y4uMEqMm2mJtocvA5/z/KfqEheF7LdsI4FXviEYWOa+Y=
X-Google-Smtp-Source: ACcGV60tybnAD4mt3cS/WS9nz5s+HOEGRbeDay0wqIS6YPkxc5zhuHNeaynE/1MIcc9GjRFwbHYtAV6/uC3JpmHXbsU=
X-Received: by 2002:a2e:4794:: with SMTP id u142-v6mr1046476lja.57.1537548350912; Fri, 21 Sep 2018 09:45:50 -0700 (PDT)
MIME-Version: 1.0
References: <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org> <CAKHUCzxL8xgn2D2W9G=Qk=AXzyw4mmcqPii6GKBSiByRyxbq+Q@mail.gmail.com> <20180921161040.GA2164@localhost>
In-Reply-To: <20180921161040.GA2164@localhost>
From: Dave Cridland <dave@cridland.net>
Date: Fri, 21 Sep 2018 17:45:39 +0100
Message-ID: <CAKHUCzxLVkpT4DVvs_FjOvxp=E-y06w25cN968tBTdrtD24QSg@mail.gmail.com>
Subject: Re: Diversity and offensive terminology in RFCs
To: Nico Williams <nico@cryptonector.com>
Cc: lists@digitaldissidents.org, "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004812170576645ff2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lKLeSmiKjrF57pDx3mbFzwWzjeM>
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 16:45:57 -0000

On Fri, 21 Sep 2018 at 17:10, Nico Williams <nico@cryptonector.com> wrote:

> On Thu, Sep 20, 2018 at 12:51:18PM +0100, Dave Cridland wrote:
> > Back when I was even more clueless than I am today, and actually ran DNS
> > servers, we used the terms "primary" and "secondary" as a matter of
> course.
> > Secondaries copied the data from primaries.
> >
> > So far, so good.
> >
> > Then we added a third nameserver, and of course that must be the
> tertiary,
> > used only when *both* the primary and secondary had failed.
> >
> > When I realised my stupidity, I avoided the terms "primary" and
> "secondary"
> > in the workplace, and instead used the terms "master" and "slave", which
> > were less easily confused - or rather, made me less easily confused by
> > them. The fact that "master/slave" was well understood within engineering
> > helped enormously.
>
> I use master/replica or primary/replica (in case anyone takes offense at
> "master" even in a context in which "slave" does not appear).
>
>
"master" and "replica" seem fine to me.


> > "Blacklist" and "whitelist" are well-known terms, but they can be avoided
> > with small effort to provide synonyms which are more easily understood -
>
> Do these terms have racial etymologies, or is a racial tinge being
> inferred where there has been none?
>
> Consider that English is my third language.  Why would I know the answer
> to this question?  A brief search seems to indicate that their origins
> are not racial, but perhaps I'm wrong.  E.g.,
>
> http://garysaid.com/are-the-terms-whitelist-and-blacklist-racist/
>
> Note that using other colors could still give rise to objections.
>
>
Yeah, the etymology is not racist. Most cultures - possibly all cultures -
associate white with light and goodness, and black with darkness and evil.

Other connotations are different, mind - black is associated with death,
authority, and so on in Europe, whereas white gets death in Asia (and, I
think, Australia).


> > "Blocklist" and "Permitlist" are trivial examples here. But if someone
> says
> > "There is a whitelist", then I also know the default is to deny. So we'll
> > need to be a bit more explicit about the default state, perhaps. In other
> > words, I worry about changing these terms, but the possibility for
> > confusion is low if we do.
>
> Blacklisting is a bad idea in most cases anyways.  A whitelist in a
> world without a blacklist shouldn't have racial tinge imputed, right?
>
>
While there's no etymological basis for whitelist and blacklist being
racist, I can understand why it's not a connotation we want to use if
possible.

Dave.