Re: SV: Diversity and offensive terminology in RFCs

Michael StJohns <mstjohns@comcast.net> Thu, 20 September 2018 17:52 UTC

Return-Path: <mstjohns@comcast.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 01C69130E13 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 10:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.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 VJen4ZJJZJGq for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 10:52:47 -0700 (PDT)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (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 021AC130DF4 for <ietf@ietf.org>; Thu, 20 Sep 2018 10:52:46 -0700 (PDT)
Received: from resomta-ch2-15v.sys.comcast.net ([69.252.207.111]) by resqmta-ch2-10v.sys.comcast.net with ESMTP id 32R2g7UwPXEHY3389grry7; Thu, 20 Sep 2018 17:52:45 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1537465965; bh=MmXbphe2L5+bAvIio6rbgZ5BSK0fpLE1dlCbm8tZbuo=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=dP1l24PuRE8zKFG3dYTs3IzwmPhzbWt2zgwG06X/R+wA17jbhtVXMoq9qShQdh4HE i81DI99R+qqW8DwJSqf8ZMjxZDLn13SBS/BFtWMc65Dh7VwvP45VHNx16vwNey/32X tEH1QhkKCU0Z3owfI/KrXaDDzjB4w3zLOOP/YN4tkn3FZ6YUWl8N5LzSsQqo9OJyot dg7quQdP4QeGvtQFvA0pdseqEhyPWzlx+Yyov6tmzvoNKXpnpyP3GWer/FThdZFeWb ddc+rG0DZRPzsAU+8RYd7MtsSGG4auRYYzKmZzDD/bFBkJapQp0wGL4Ub59sLguTMd oegm2pz5s1TnQ==
Received: from [IPv6:2601:152:4400:4013:a843:b42a:b947:f097] ([IPv6:2601:152:4400:4013:a843:b42a:b947:f097]) by resomta-ch2-15v.sys.comcast.net with ESMTPSA id 3389gIfbLaWyQ3389gRLoW; Thu, 20 Sep 2018 17:52:45 +0000
Subject: Re: SV: Diversity and offensive terminology in RFCs
To: ietf@ietf.org
References: <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org> <CAKHUCzxL8xgn2D2W9G=Qk=AXzyw4mmcqPii6GKBSiByRyxbq+Q@mail.gmail.com> <c755471a7f744fdd958759c6c5001147@exchange02.office.nic.se> <20180920170939.GA68853@isc.org>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <968547d5-7e96-5c31-69a3-20456baccf1a@comcast.net>
Date: Thu, 20 Sep 2018 13:52:44 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <20180920170939.GA68853@isc.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-CMAE-Envelope: MS4wfFmbEu9p1LINAyAQq/xpNBUMlynaFiQAtdk0Ee8K9gyGB0U0Let6xb7wM7WwqsKmkYlnMFMYHVOoaUKS0y9DFuu4rzKj41OfArcQsPYOMTAlchUCwavh Yf7eAgtuzNBk+JRgzOiPbsssr8rvNBz/9YHlFKBMXWAAnURAe6VPDtV0cgpe5nTq2viW5nxbyqJi87x5G9BojURF/s/zsN9i35tuRJbza8qoA7lvXmbt9TkG 81OHpGHOR3nSM4YET9az0sFmoW9/+pUXmSM91qe3XOU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZYq058qN-r9z7ZsmQ85emJXGBok>
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 17:52:49 -0000

On 9/20/2018 1:09 PM, Evan Hunt wrote:
> I think the issue with "man-in-the-middle" isn't that it's offensive,
> per se, but that the unnecessary use of gendered terminology tends to
> reinforce mental biases.  In my lifetime in the US, we've largely shifted
> from "fireman" and "mailman" and "stewardess" to "firefighter" and "mail
> carrier" and "flight attendant" for similar reasons.  "Man-in-the-middle"
> carries with it a subtle, unnecessary suggestion that the clever indivdual
> between Alice and Bob is probably named Carl not Carol.

Generically, there are some differences between the swap to non-gendered 
nouns and terms like man-in-the-middle.  The former reflects the 
reasonable desire to allow people to choose what they'll be called or 
how they're referred to - there are other examples that are obvious.   
But "man-in-the-middle" is just a term of art - one that's succinct and 
in our context unmistakable.

I'm concerned we're again off in the weeds here.  English has a lot of 
words with overloaded meanings and multiple definitions and others that 
do not. For example - whitelist and blacklist have pretty much singular 
meanings related to acceptance or rejection, while master has a 
bunch.    OED says blacklist goes back to at least 1619.  See a 
discussion on this about 10 years ago at 
http://garysaid.com/are-the-terms-whitelist-and-blacklist-racist/

Lastly, words can have cultural overlays that are not obvious. 
Continuing from Adrian's bundle of sticks, a similar word is a synonym 
for a cigarette and another similar word expression is a synonym for 
being tired.  The latter definition appearing around 1450 according to 
dictionary.com.

For better or for worse, we have our jargon (and invent it at dizzying 
rates with every RFC), we borrow jargon from related fields, and we base 
the remainder of text on established English (please don't use twerk in 
your RFC's!).    Let's not see shadows that have not yet overtaken us.   
And please - let's not require Heather and the RFC folks to become our 
word conscience.

If you feel strongly about this AND you're authoring a draft or RFC - by 
all means, wordsmith to your hearts content.  Please use words that lead 
to only one meaning in context where those words are necessary and try 
not to invent new ones.

Later, Mike