Re: Diversity and offensive terminology in RFCs

Dave Cridland <dave@cridland.net> Thu, 20 September 2018 21:34 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 308CA130E36 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 14:34:27 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 7Z64EgSqNAk5 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 14:34:25 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 8D872127333 for <ietf@ietf.org>; Thu, 20 Sep 2018 14:34:24 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id f1-v6so9727458ljc.9 for <ietf@ietf.org>; Thu, 20 Sep 2018 14:34:24 -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=mpxZPLb9d5HLBgJDDcGnD0c5jLRskMnKIrJig+TTUtI=; b=XQR5RzKYFkloohqEWI+KE1T0oYcpHbrtilW7+uG0SQ1Lucm64RfNn2WWX6Mg8KYqWk 8AVcJpxtUKOWdiNkRle7IOrXg0/C3Z66bi37Xkp1prxXBJu9YqmEjew4H2aCawOk4EAN QdzELwWPrV5FFl8zb83G4AwXgir9W4VAgB8Mk=
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=mpxZPLb9d5HLBgJDDcGnD0c5jLRskMnKIrJig+TTUtI=; b=t/qTw4woYAyS18lwVxZMFTPUj9A1FpwzGpw3kWTFMKb8Uc/zg5DUFJ9vc0zAjSzMAL rH2l5QJQ54KOZskYcoCkvbXdzp1hZOAj+nCskPrvcdO4WHOEP2apxE0lZFrjsGhSy5rY VoIgOMP65nX9CsHH05tnAbBzus1Idx8z/xCurOK02yxxvNmZG6Rj+MRTT2sPJd4WNpKz jEXhNPqTl02h3Ml2l+XEVWurjgKx1wPAZnMDO2Wj6H92zvfIHmKvolcMLh/pOczkRFjq 752NrlWiC58Dd4V5lrYgzEoyFSKdPcpFu6uKO0mGyAGl1iBkST6CVZcv0lnLcqg8UEWJ Da5Q==
X-Gm-Message-State: APzg51BQekX+H7VyXQVN8etNz3k6j2cVpOdnMPGRgtYw/+bPWxDnnv7s FNBubiSsdtXPztZYHJo4TaAEO7DFPWBO1pk7n3qwFZIO0Qo=
X-Google-Smtp-Source: ANB0VdZnZHNgO1ipqJgeCbF9k3F4RgIcDEoDupVTDa/yTnYhjPai4qQVFL6Pf4NJ6ypJm1tUvvgh2ykWzBsLLyXjpf0=
X-Received: by 2002:a2e:9854:: with SMTP id e20-v6mr6054127ljj.143.1537479262473; Thu, 20 Sep 2018 14:34:22 -0700 (PDT)
MIME-Version: 1.0
References: <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org> <CAKHUCzxL8xgn2D2W9G=Qk=AXzyw4mmcqPii6GKBSiByRyxbq+Q@mail.gmail.com> <20180920173352.GB68853@isc.org>
In-Reply-To: <20180920173352.GB68853@isc.org>
From: Dave Cridland <dave@cridland.net>
Date: Thu, 20 Sep 2018 22:34:11 +0100
Message-ID: <CAKHUCzz-gSKUjEqpR6h0z6NhJTus24R+5CtjXHfwObKoCQNAjQ@mail.gmail.com>
Subject: Re: Diversity and offensive terminology in RFCs
To: each@isc.org
Cc: lists@digitaldissidents.org, "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004a2a890576544998"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DPaOiBk32Xm190_lPQejrmjXEH4>
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 21:34:27 -0000

On Thu, 20 Sep 2018 at 18:33, Evan Hunt <each@isc.org> 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.
>
> This suggests that at the time, you may have been under the impression
> that the secondary server would be used only when the primary had failed?
>
>
Yes, that is exactly what I thought at the time, based on the terms.


> For whatever it's worth, I think of it as concentric rings, with "primary"
> referring to the center ring and "secondary" to the next ring out. Data
> originates in the primary ring, and migrates to and through the secondary
> ring, and we name the servers "primary" or "secondary" depending on which
> ring they're in.
>
> I never thought of "master" as having political or racial implications
> (though, of course, as a white American guy, I do excel at overlooking
> such things).  I thought of it as comparable to "master key".  But at some
> point it crossed my mind that nobody ever talks about "slave keys", and if
> the original choice of terminology had been so innocuous, then why don't
> call them "master" and "copy"?  And then I started to see how these terms
> could indeed come across as unwelcoming to people of some backgrounds.
>
> And since "primary/secondary" works fine, I now try to use it, at least in
> professional writing.  In casual conversation, old habits take longer to
> break.
>

My point was that primary/secondary really didn't work for me.

I quite like Tony Finch's suggestion of "master/replica" though, for DNS in
particular.