Re: Diversity and offensive terminology in RFCs

Loa Andersson <loa@pi.nu> Thu, 20 September 2018 11:52 UTC

Return-Path: <loa@pi.nu>
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 D1C18130F06 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 04:52:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 8-3XmzoBfxVg for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 04:52:21 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17CA1130ED8 for <ietf@ietf.org>; Thu, 20 Sep 2018 04:52:20 -0700 (PDT)
Received: from [192.168.1.20] (unknown [119.94.164.184]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id EC61A180121E for <ietf@ietf.org>; Thu, 20 Sep 2018 13:52:17 +0200 (CEST)
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> <d3b29086-9096-2087-7448-a9673a69f7f5@digitaldissidents.org>
From: Loa Andersson <loa@pi.nu>
Message-ID: <c79c49e8-e6d4-895b-7479-f963150ed23a@pi.nu>
Date: Thu, 20 Sep 2018 19:52:12 +0800
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: <d3b29086-9096-2087-7448-a9673a69f7f5@digitaldissidents.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jN3KnJ-DeIKvdiU2kfbHS6hPOlk>
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 11:52:31 -0000

Niels,

You could make anything work, but it would probably cause a lot
of pain and confusion.

In a master/slave situation the master tells the salve what to do,
and there is no way to discuss it. leader/follower does not bring the
same type of understanding over, I've worked for a lot of good leaders
(and some bad ones :) ), but part of what a good leader do, is to be
prepared to take the discussion e.g. when the follower don't want to
follow.

I'd say if we had a master/slave situation among humans it would be a
bad thing, if we have it among networking nodes, I don't particularly
care about the terminology.

/Loa

On 2018-09-20 19:41, Niels ten Oever wrote:
> On 09/20/2018 01:25 PM, Stewart Bryant wrote:
>> The term master/slave is used when it is technically required that the instruction is executed without equivocation.
> 
> Would leader/follower (as implemented by Django) not work just as well?
> It seems to work for them for quite a while already.
> 
> Best,
> 
> Niels
> 

-- 


Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert
Bronze Dragon Consulting             phone: +46 739 81 21 64