Re: why exactly is HRPC for, was Diversity and offensive terminology in RFCs

Mark Rousell <mark.rousell@signal100.com> Fri, 21 September 2018 02:25 UTC

Return-Path: <mark.rousell@signal100.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 8EDBD130DFF for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 19:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, URIBL_BLOCKED=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 x8AUpWeBwvIH for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 19:25:52 -0700 (PDT)
Received: from mail.signal100.net (5751e297.skybroadband.com [87.81.226.151]) by ietfa.amsl.com (Postfix) with ESMTP id A1CAB130EB4 for <ietf@ietf.org>; Thu, 20 Sep 2018 19:25:51 -0700 (PDT)
Received: from [192.168.1.5] ([87.81.226.151]) by mail.signal100.net with MailEnable ESMTP; Fri, 21 Sep 2018 03:10:47 +0100
Subject: Re: why exactly is HRPC for, was Diversity and offensive terminology in RFCs
To: ietf@ietf.org
References: <20180920233440.238CA20051DDE5@ary.qy>
From: Mark Rousell <mark.rousell@signal100.com>
Message-ID: <5BA45326.8070707@signal100.com>
Date: Fri, 21 Sep 2018 03:10:46 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20180920233440.238CA20051DDE5@ary.qy>
Content-Type: multipart/alternative; boundary="------------040008020509000404090103"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mS6beE-ken_Edn44hQvx8R7BLdU>
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: Fri, 21 Sep 2018 02:25:59 -0000

On 21/09/2018 00:34, John Levine wrote:
> In article <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org> you write:
>> In the discussion that followed it was remarked that in RFCs terms like
>> Master/Slave, blacklist/whitelist, man-in-middle, and other terminology
>> that is offensive to some people and groups is quite common.
> If this is really the best that HRPC can do, I would suggest that it's
> time for the IRTF to consider whether to shut it down.
>
> [...]
> Instead, we get this stuff.  Even if you think that the language in
> our RFCs is problematic, which for the most part I don't, I am
> confident that no RFC has ever enslaved anyone, nor put anyone on a
> secret list that kept them from working (the actual meaning of
> blacklist for people who know their history.)
>
> There are real human rights problems that HRPC could engage with, but
> don't.  They need to make up their mind whether they're serious.

Well said.


-- 
Mark Rousell