Re: Diversity and offensive terminology in RFCs
Nico Williams <nico@cryptonector.com> Fri, 21 September 2018 16:10 UTC
Return-Path: <nico@cryptonector.com>
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 04C49130E45 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 09:10:48 -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=cryptonector.com
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 DHQQ8pMhOBbY for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 09:10:46 -0700 (PDT)
Received: from pdx1-sub0-mail-a9.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 828E712777C for <ietf@ietf.org>; Fri, 21 Sep 2018 09:10:46 -0700 (PDT)
Received: from pdx1-sub0-mail-a9.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a9.g.dreamhost.com (Postfix) with ESMTP id DEC4E80B75; Fri, 21 Sep 2018 09:10:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=nepJs/im46o5Ur 71spfv30WLyDw=; b=ErJ3ccoG9vyf6C+PSLbtoBTl/E8VlH/h/yf7+VDEqz4EqM 0Q0dF9BNH4QYuCaj5myM2KRvpeLXujNegaTjwbTC3bg04OIwEfMhu55CVcs293M3 z81k+Twock8b2iGdPU2OpbFfdpK9cX9haddSKF5duA3sQsVPC0iPF/sPxUcE0=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a9.g.dreamhost.com (Postfix) with ESMTPSA id 5A05280B86; Fri, 21 Sep 2018 09:10:44 -0700 (PDT)
Date: Fri, 21 Sep 2018 11:10:42 -0500
X-DH-BACKEND: pdx1-sub0-mail-a9
X-DH-BACKEND: pdx1-sub0-mail-a9
From: Nico Williams <nico@cryptonector.com>
To: Dave Cridland <dave@cridland.net>
Cc: lists@digitaldissidents.org, "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: Diversity and offensive terminology in RFCs
Message-ID: <20180921161040.GA2164@localhost>
References: <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org> <CAKHUCzxL8xgn2D2W9G=Qk=AXzyw4mmcqPii6GKBSiByRyxbq+Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAKHUCzxL8xgn2D2W9G=Qk=AXzyw4mmcqPii6GKBSiByRyxbq+Q@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NLfBoVBmCFRdei2DCAAS59n7cYI>
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:10:48 -0000
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). > "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. > "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? > "Man-in-the-middle" I'm clearly too stupid to understand why this might be > offensive, but equally I have no idea what term of art would suffice > instead. In crypto literature it is often Mallory who gets in the middle, so she gets misgendered when called an MITM. But WITM wouldn't do either, would it? Nico --
- Diversity and offensive terminology in RFCs Niels ten Oever
- Re: Diversity and offensive terminology in RFCs Riccardo Bernardini
- Re: Diversity and offensive terminology in RFCs Stewart Bryant
- Re: Diversity and offensive terminology in RFCs Petr Špaček
- Re: Diversity and offensive terminology in RFCs Niels ten Oever
- Re: Diversity and offensive terminology in RFCs Dave Cridland
- Re: Diversity and offensive terminology in RFCs Loa Andersson
- Re: Diversity and offensive terminology in RFCs Mukund Sivaraman
- SV: Diversity and offensive terminology in RFCs Anne-Marie Eklund-Löwinder
- RE: Diversity and offensive terminology in RFCs Roberta Maglione (robmgl)
- Re: Diversity and offensive terminology in RFCs Ole Troan
- Re: Diversity and offensive terminology in RFCs Michal Krsek
- Re: Diversity and offensive terminology in RFCs Tony Finch
- Re: Diversity and offensive terminology in RFCs Job Snijders
- Re: Diversity and offensive terminology in RFCs Anton Ivanov
- Re: Diversity and offensive terminology in RFCs Anton Ivanov
- RE: Diversity and offensive terminology in RFCs Adrian Farrel
- Re: SV: Diversity and offensive terminology in RF… Jaap Akkerhuis
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Andrew Sullivan
- Re: Diversity and offensive terminology in RFCs Kathleen Moriarty
- Re: Diversity and offensive terminology in RFCs lloyd.wood
- Re: Diversity and offensive terminology in RFCs Carsten Bormann
- Re: SV: Diversity and offensive terminology in RF… lloyd.wood
- Re: Diversity and offensive terminology in RFCs Paul Wouters
- Re: Diversity and offensive terminology in RFCs Paul Wouters
- Re: Diversity and offensive terminology in RFCs lloyd.wood
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Stephan Wenger
- Re: Diversity and offensive terminology in RFCs Mark Nottingham
- Re: Diversity and offensive terminology in RFCs Stephen Farrell
- RE: Diversity and offensive terminology in RFCs John E Drake
- Re: Diversity and offensive terminology in RFCs Melinda Shore
- Re: Diversity and offensive terminology in RFCs Dick Franks
- Re: Diversity and offensive terminology in RFCs ned+ietf
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Melinda Shore
- Re: Diversity and offensive terminology in RFCs Melinda Shore
- Re: Diversity and offensive terminology in RFCs Paul Hoffman
- Re: SV: Diversity and offensive terminology in RF… Evan Hunt
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- ""Man-in-the-middle""? <was, Re: SV: Diversity an… Charlie Perkins
- Re: Diversity and offensive terminology in RFCs Evan Hunt
- Re: Diversity and offensive terminology in RFCs Melinda Shore
- Re: Diversity and offensive terminology in RFCs Evan Hunt
- Re: SV: Diversity and offensive terminology in RF… Michael StJohns
- Re: ""Man-in-the-middle""? <was, Re: SV: Diversit… Dave Aronson
- Re: SV: Diversity and offensive terminology in RF… Heather Flanagan
- Re: Diversity and offensive terminology in RFCs Mark Nottingham
- Re: Diversity and offensive terminology in RFCs Heather Flanagan
- Re: Diversity and offensive terminology in RFCs Evan Hunt
- Re: Diversity and offensive terminology in RFCs Carsten Bormann
- Re: Diversity and offensive terminology in RFCs Ted Lemon
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Evan Hunt
- Re: Diversity and offensive terminology in RFCs Carsten Bormann
- Re: Diversity and offensive terminology in RFCs John C Klensin
- Re: Diversity and offensive terminology in RFCs Carsten Bormann
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: SV: Diversity and offensive terminology in RF… Anton Ivanov
- Re: Diversity and offensive terminology in RFCs Yoav Nir
- Re: Diversity and offensive terminology in RFCs Kyle Rose
- Re: Diversity and offensive terminology in RFCs Brian E Carpenter
- Re: Diversity and offensive terminology in RFCs Carsten Bormann
- Re: Diversity and offensive terminology in RFCs Dave Cridland
- Re: Diversity and offensive terminology in RFCs Ted Lemon
- Re: why exactly is HRPC for, was Diversity and of… John Levine
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Ted Lemon
- Re: Diversity and offensive terminology in RFCs Brian E Carpenter
- Re: Diversity and offensive terminology in RFCs Mark Rousell
- Re: why exactly is HRPC for, was Diversity and of… Mark Rousell
- Re: why exactly is HRPC for, was Diversity and of… Melinda Shore
- Re: Diversity and offensive terminology in RFCs Alia Atlas
- Re: why exactly is HRPC for, was Diversity and of… Allison Mankin
- Re: Diversity and offensive terminology in RFCs Mark Rousell
- Re: Diversity and offensive terminology in RFCs Mark Rousell
- Re: Diversity and offensive terminology in RFCs Mark Rousell
- Re: Diversity and offensive terminology in RFCs Phillip Hallam-Baker
- Re: Diversity and offensive terminology in RFCs Lloyd Wood
- Re: Diversity and offensive terminology in RFCs Lloyd Wood
- On-path attackers (Was: Re: Diversity and offensi… Jari Arkko
- Re: why exactly is HRPC for, was Diversity and of… Eliot Lear
- Re: why exactly is HRPC for, was Diversity and of… Niels ten Oever
- Re: why exactly is HRPC for, was Diversity and of… Lloyd Wood
- Re: Diversity and offensive terminology in RFCs Eliot Lear
- Re: On-path attackers (Was: Re: Diversity and off… Kathleen Moriarty
- Re: Diversity and offensive terminology in RFCs Alissa Cooper
- Re: why exactly is HRPC for, was Diversity and of… Paul Wouters
- Re: why exactly is HRPC for, was Diversity and of… Ted Lemon
- Re: On-path attackers (Was: Re: Diversity and off… Donald Eastlake
- Re: why exactly is HRPC for, was Diversity and of… Lloyd Wood
- Re: Diversity and offensive terminology in RFCs Niels ten Oever
- Re: On-path attackers (Was: Re: Diversity and off… Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Ted Lemon
- Re: Diversity and offensive terminology in RFCs Anton Ivanov
- Re: On-path attackers (Was: Re: Diversity and off… Ted Lemon
- Re: why exactly is HRPC for, was Diversity and of… John R Levine
- Re: Diversity and offensive terminology in RFCs Paul Wouters
- Re: Diversity and offensive terminology in RFCs Eliot Lear
- Re: Diversity and offensive terminology in RFCs Phillip Hallam-Baker
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Nico Williams
- Re: why exactly is HRPC for, was Diversity and of… Avri
- Re: Diversity and offensive terminology in RFCs Spencer Dawkins at IETF
- Re: Diversity and offensive terminology in RFCs Dave Cridland
- Re: why exactly is HRPC for, was Diversity and of… John Levine
- Re: why exactly is HRPC for, was Diversity and of… Spencer Dawkins at IETF
- Re: why exactly is HRPC for, was Diversity and of… Allison Mankin
- Tell me if I should send this Re: why exactly is … Mallory Knodel
- Mallory-in-the-middle attacks (Re: SV: Diversity … Nico Williams
- Re: Diversity and offensive terminology in RFCs Nico Williams
- Re: On-path attackers (Was: Re: Diversity and off… Brian E Carpenter
- Re: Diversity and offensive terminology in RFCs Glenn Deen
- Re: Mallory-in-the-middle attacks (Re: SV: Divers… Nico Williams
- Re: Tell me if I should send this Re: why exactly… lloyd.wood
- Re: Mallory-in-the-middle attacks (Re: SV: Divers… Mallory Knodel
- Re: why exactly is HRPC for, was Diversity and of… Mallory Knodel
- Re: Diversity and offensive terminology in RFCs Abdussalam Baryun
- Re: why exactly is HRPC for, was Diversity and of… S Moonesamy
- Re: why exactly is HRPC for, was Diversity and of… Mallory Knodel