Re: Diversity and offensive terminology in RFCs

Michal Krsek <michal@krsek.cz> Thu, 20 September 2018 12:48 UTC

Return-Path: <michal@krsek.cz>
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 D39D0130EA3 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 05:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=krsek-cz.20150623.gappssmtp.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 6Y12AzpGSxu3 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 05:48:03 -0700 (PDT)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (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 C51FF130DE2 for <ietf@ietf.org>; Thu, 20 Sep 2018 05:48:02 -0700 (PDT)
Received: by mail-ed1-x52c.google.com with SMTP id a20-v6so7749232edd.4 for <ietf@ietf.org>; Thu, 20 Sep 2018 05:48:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krsek-cz.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=s5SioI7Y4dMkOAV5rZJOUooI3KzrKXYvsTWvBW3OGdM=; b=JcYwBDlxgzbFIbCSHYeRWIrk8M/LVKqWGQOuXYQz0/as6rdfZBurA151affCM4vwOM 9RuCP80D3lEAzu9xMF/PeJVXLA4Mg92mp1nJuKUe6YuKaFMMDIBOFzP5uEFwgkojnHfb Dn8+I0kT/GuFAxsf/5l+7cnh+h6TEww3nnadORztLd0Kzs0yctH3GacUq6+AhlaRA2t4 2ok3Pt/ueCqcUpOyWCKl/ei2STK+QIyvPCTTwHf+PWWhKVXsR0Ec2iSV7nsYjWFaKpaG 1mn6e1A8QcK3Jz4YVbe8Lgq0zdEYF2K1QOChnNlX8XfGUk5v7lg0GqF6+G56gqT1eHkb GEHQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=s5SioI7Y4dMkOAV5rZJOUooI3KzrKXYvsTWvBW3OGdM=; b=SEx6g9uxSkn4cg0usZZmljEr78wpg/BGcKzi8nbHXfaW2NDfFic1CbsVu2G1BR24Bz 4XtRjcfD0aKSTl7Xq5i3FhBGlCVzMSZBthyyh+Rl/mrUcMzfoNC3gKa75twEoxYfXWww y7bWPxiuZXv7K6RZNyJRxkpU9lvwsheCYycJ2df2PnpAiJfVKyPpzNFFbHODKUXI0N6U eO9RL2h4qJ3yXPR94vrWSk2Xa63KK0OrXv8SBHX1zy6LHjBamzAhYdcRz3cnhR7Dz/+S HWuNbQSJcpqmV4ahvFLH1UVgu9U6BeMi/ZB/9nsUW1IvQb6Ra9Q7UxBNtYl3kKvQaK+E E9tA==
X-Gm-Message-State: APzg51Ae5SeEQ9dnat/vglfdQH0L4t6BrxfZdlhRJb8VikJhq+ZHFwYB bECEgbgLHvquIrmAv/+/WdmrGIgiqfSxS90b
X-Google-Smtp-Source: ANB0Vdav+X6PEn36aXxA21Vf74t61PR6rAJ3HjDBfP6v5fB6k9CZ55gvnX94LJlt3nNTKAj/k1di1g==
X-Received: by 2002:a50:f743:: with SMTP id j3-v6mr4055988edn.203.1537447680837; Thu, 20 Sep 2018 05:48:00 -0700 (PDT)
Received: from Michals-MacBook-Air.local ([152.115.56.9]) by smtp.gmail.com with ESMTPSA id y27-v6sm813379edb.20.2018.09.20.05.47.59 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Sep 2018 05:48:00 -0700 (PDT)
Subject: Re: Diversity and offensive terminology in RFCs
To: ietf@ietf.org
References: <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org> <CABSMSPXxg-UTZzXREcbYQiQgzAwXP4uUGPtN+jWrYomZRQxL-Q@mail.gmail.com> <CFA08128-7D9E-4CA8-B6FD-F3D9A37DD18F@gmail.com> <c4c42ebc-5000-059e-0e91-13584b279f68@nic.cz> <18b0c971e11d458bba421a29d4e5e95b@XCH-RCD-009.cisco.com>
From: Michal Krsek <michal@krsek.cz>
Message-ID: <39402178-5f5b-c58d-2331-1041076efb2b@krsek.cz>
Date: Thu, 20 Sep 2018 14:48:12 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <18b0c971e11d458bba421a29d4e5e95b@XCH-RCD-009.cisco.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yRPq0Fh-iL1F4bhqsd4Eze5G4uk>
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 12:48:06 -0000

Hello,

I understand those words may be inappropriate in some contexts, but they 
are fine in other contexts.

Not touching the IT area, how we teach history?


I'd say - our master/slave act means something else than enslaving 
people, man-in-the-middle is a system not a male person, debugging means 
something else than disinfection and so on.

We do have our jargon for long time and I'm not sure if it is a clever 
idea to start building a Tower of Babel 
https://en.wikipedia.org/wiki/Tower_of_Babel .


                     Michal


On 20/09/2018 14:15, Roberta Maglione (robmgl) wrote:
> I agree with the comments made below: in my opinion there is nothing wrong in using terms like master/slave, white/black lists, man-in the middle, etc.
> In the context of IETF we are using them as part of technical discussions: if you don’t take them out of the context in my opinion there is nothing wrong with these words.
>
> Thanks
> Roberta
>
>
> -----Original Message-----
> From: ietf <ietf-bounces@ietf.org> On Behalf Of Petr Špacek
> Sent: Thursday, September 20, 2018 13:29
> To: ietf@ietf.org
> Subject: Re: Diversity and offensive terminology in RFCs
>
> On 20/09/2018 13:25, Stewart Bryant wrote:
>> The problem with the many proposed alternative versions of Master/Slave that I have seen over the years, is that they fail to express the technical importance of the absolute relationship between the two entities.
>>
>> The term master/slave is used when it is technically required that the instruction is executed without equivocation. Indeed in hardware-land, dithering over what to do (metastability) is so catastrophic that many technical measures need to be taken to avoid it.
>>
>> If all the master-slave flip-flops in the Internet were replaced with do-it-if-I-feel-like-it flip-flops, we would not have an Internet.
>>
>> In RFC-land we are mirroring the long-standing language of the hardware designers, and having a common terminology that transcends all aspects of logic design seems to me to be a net benefit to the internet as a whole.
> Yes, we always need to take context into account!
>
> I fully agree with with Stewart and Riccardo (previous reply) on this.
>