Re: [Gendispatch] draft charter text: terminology-related WG

Dan Harkins <dharkins@lounge.org> Sun, 14 February 2021 00:23 UTC

Return-Path: <dharkins@lounge.org>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38C9A3A11DB for <gendispatch@ietfa.amsl.com>; Sat, 13 Feb 2021 16:23:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001] 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 BJzufJ0iyIkl for <gendispatch@ietfa.amsl.com>; Sat, 13 Feb 2021 16:23:45 -0800 (PST)
Received: from www.goatley.com (www.goatley.com [198.137.202.94]) (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 556753A11B7 for <gendispatch@ietf.org>; Sat, 13 Feb 2021 16:23:45 -0800 (PST)
Received: from trixy.bergandi.net (cpe-76-176-14-122.san.res.rr.com [76.176.14.122]) by wwwlocal.goatley.com (PMDF V6.8 #2433) with ESMTP id <0QOH0AYCXT3LA6@wwwlocal.goatley.com> for gendispatch@ietf.org; Sat, 13 Feb 2021 18:23:45 -0600 (CST)
Received: from blockhead.local ([69.12.173.8]) by trixy.bergandi.net (PMDF V6.7-x01 #2433) with ESMTPSA id <0QOH00H3GT1RMX@trixy.bergandi.net> for gendispatch@ietf.org; Sat, 13 Feb 2021 16:22:40 -0800 (PST)
Received: from 69-12-173-8.static.dsltransport.net ([69.12.173.8] EXTERNAL) (EHLO blockhead.local) with TLS/SSL by trixy.bergandi.net ([10.0.42.18]) (PreciseMail V3.3); Sat, 13 Feb 2021 16:22:40 -0800
Date: Sat, 13 Feb 2021 16:23:43 -0800
From: Dan Harkins <dharkins@lounge.org>
In-reply-to: <fabe2570-d138-8f35-f14a-a564a00ea7ba@gont.com.ar>
To: gendispatch@ietf.org
Message-id: <c425e778-429f-eedb-b730-8b6f03dfaa0d@lounge.org>
MIME-version: 1.0
Content-type: text/plain; charset="utf-8"; format="flowed"
Content-language: en-US
Content-transfer-encoding: 8bit
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
X-PMAS-SPF: SPF check skipped for authenticated session (recv=trixy.bergandi.net, send-ip=69.12.173.8)
X-PMAS-External-Auth: 69-12-173-8.static.dsltransport.net [69.12.173.8] (EHLO blockhead.local)
References: <A531C377-33A4-4138-BE28-788FF5FE267E@sn3rd.com> <CABcZeBPxQrzQZZ2ec+cvpovdkJaXcQ4f8Ged7Om1QPg7UrZ_Ew@mail.gmail.com> <C7451272-56CF-49C7-ABAA-7B8849AAE8DB@cisco.com> <31dc343f-8e73-6afd-1fca-c68fb5b47bd0@lounge.org> <fabe2570-d138-8f35-f14a-a564a00ea7ba@gont.com.ar>
X-PMAS-Software: PreciseMail V3.3 [210212b] (trixy.bergandi.net)
X-PMAS-Allowed: system rule (rule allow header:X-PMAS-External noexists)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/BGmvo14XOqdb-AgGrDyK6TaJbBg>
Subject: Re: [Gendispatch] draft charter text: terminology-related WG
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Feb 2021 00:23:48 -0000

On 2/13/21 10:38 AM, Fernando Gont wrote:
> On 13/2/21 15:27, Dan Harkins wrote:
> [...]
>>
>>    step 1: stop using the words "master" and "slave"
>>    step 2: ???
>>    step 3: more diverse and inclusive IETF
>>
>> So anyone who can explain step 2 in sufficient detail to get from 
>> step 1 to
>> step 3 would probably be an authority on the matter.
>
> Shouldn't the first question be "where do you want to get?". And, if 
> the answer is "more diverse and inclusive IETF", then the group should 
> study what's the high-order bit to get there?

   That seems to already be the answer. Have you heard anyone argue 
otherwise?

> This seems like arguing the other way around: "Tell me how inclusive 
> language helps diversity and inclusiveness such that we can pursue it".

   No, what I'm doing is asking people who are arguing that language can be
"exclusive" to show their reasoning. What is the result of using "exclusive"
language in an RFC? Well, an IETF that is not diverse and inclusive. I just
want to see how that works.

   We have specifically targeted the words "master" and "slave". How does
replacing those words with others affect diversity and inclusion at the 
IETF?

   regards,

   Dan.

-- 
"The object of life is not to be on the side of the majority, but to
escape finding oneself in the ranks of the insane." -- Marcus Aurelius