Re: Diversity and offensive terminology in RFCs

Andrew Sullivan <ajs@anvilwalrusden.com> Thu, 20 September 2018 13:32 UTC

Return-Path: <ajs@anvilwalrusden.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 E96CF130DE8 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 06:32:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=bSnkMDnw; dkim=pass (1024-bit key) header.d=yitter.info header.b=i31gXWx/
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 ewjMn5ifQVDi for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 06:32:00 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEB0B130DEA for <ietf@ietf.org>; Thu, 20 Sep 2018 06:32:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 2F357BD156 for <ietf@ietf.org>; Thu, 20 Sep 2018 13:32:00 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1537450320; bh=VfXnHh3+9D6ATFFrIZ/Mccqspz9yz/cU95duigPUJfQ=; h=Date:From:To:Subject:References:In-Reply-To:From; b=bSnkMDnwdHv4qB7TiwIwu9k7ZoHmAnJs59hXo6Xdw8jgVuXFHcxfbUL/22BHxtuZ9 h4xqQ84HlfDdrUpDPU8w+ke/JUlgYW3eXSExGsrOHFSCNJCTNe+rAnpvfdOUBWQNnK O7hU/PZWwGdR6RoZdGbrR8p93ekwfV3gwA4+pv6c=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F8ZWHta_OhGU for <ietf@ietf.org>; Thu, 20 Sep 2018 13:31:59 +0000 (UTC)
Date: Thu, 20 Sep 2018 09:31:58 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1537450319; bh=VfXnHh3+9D6ATFFrIZ/Mccqspz9yz/cU95duigPUJfQ=; h=Date:From:To:Subject:References:In-Reply-To:From; b=i31gXWx/d44nODP0hCMRzNGL2ANQgA0rlbLOzWbPp6RT51jlKAtJp7kdrmxla9uhB BR6lY8kxgv5vwHsJBGSDVk+DKghK4RmYOzaQMQTTIq0NkXewUvzuKSbK9KRLtN/1fE DcUAFQxnreEVGpb1oY0Fqo+/t9dDIcObqM3xY6vU=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Diversity and offensive terminology in RFCs
Message-ID: <20180920133158.cam5yhyhtcssampk@mx4.yitter.info>
References: <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org> <CABSMSPXxg-UTZzXREcbYQiQgzAwXP4uUGPtN+jWrYomZRQxL-Q@mail.gmail.com> <CFA08128-7D9E-4CA8-B6FD-F3D9A37DD18F@gmail.com> <d3b29086-9096-2087-7448-a9673a69f7f5@digitaldissidents.org> <c963b558-786c-82c9-41ac-c2ad132ab7b6@kot-begemot.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <c963b558-786c-82c9-41ac-c2ad132ab7b6@kot-begemot.co.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/add1oLmIjIDQWZ8vUIjK_AJoHg0>
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 13:32:03 -0000

On Thu, Sep 20, 2018 at 02:11:03PM +0100, Anton Ivanov wrote:
> A follower is following the leader because it has agreed to be lead. As
> correctly noted by Stewart, in a master/slave hardware (or software)
> configuration nobody asks the slave about its opinion on things.

Well, ok, but in (e.g.) the DNS, the slave actually is in the position
to refuse the zone transfer on the grounds that it is malformed.  This
happens sometimes, so in fact in at least one prominent use of these
terms in the IETF the absolute power of the "master" is not true.  I
am aware of other examples, too, so if the justification is the
absolute slavishness (if you'll pardon the word) of the putative
slaves, I think the description isn't quite correct anyway.

For whatever it's worth, I have no opinion about whether this bit of
language needs to change, though I do somewhat prefer the
"primary/secondary" usage.  Note that these terms denote a logical
relationship, not a temporal or existential one, so there can be
multiple primaries (in some cases) and multiple secondaries
(frequently).  It does seem to me that, if one wishes to communicate
with others, it's often a good idea to avoid causing them offense.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com