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

"John Levine" <johnl@taugh.com> Thu, 20 September 2018 23:34 UTC

Return-Path: <johnl@iecc.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 1A04112DD85 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 16:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level:
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001] autolearn=no 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 3vGJ6m-IxrsC for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 16:34:42 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 700DA124D68 for <ietf@ietf.org>; Thu, 20 Sep 2018 16:34:42 -0700 (PDT)
Received: (qmail 15170 invoked from network); 20 Sep 2018 23:34:40 -0000
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 20 Sep 2018 23:34:40 -0000
Received: by ary.qy (Postfix, from userid 501) id 238CA20051DDE5; Thu, 20 Sep 2018 19:34:39 -0400 (EDT)
Date: Thu, 20 Sep 2018 19:34:39 -0400
Message-Id: <20180920233440.238CA20051DDE5@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: why exactly is HRPC for, was Diversity and offensive terminology in RFCs
In-Reply-To: <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HmWGGqGpnISRBrH3MO13kKjX3ac>
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 23:34:44 -0000

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.

When I've gone to HRPC sessions, I have heard endless papers about
more or less plausible threats to freedom of expression or to
anonymous speech (which is not the same thing.)  More than once I have
stood up at HRPC sessions and noted that the Universal Declaration of
Human Rights has thirty articles, and none of the discussion deals
with more than two of them.  The chairs have assured me that they are
equally interested in the other rights, but the evidence of that is
pretty thin.

What about article 12, protection agaisnt attacks on honor and
repuation?  What is HRPC doing about trolling and other online
attacks?

Or article 17, nobody shall be arbitrariy deprived of his property?
What is HRPC doing to keep our protocols from being used to enable
phishing and other online theft?

Or article 23, the right to rest and leisure?  What is HRPC doing to
keep our protocols from being used to put people on a 24 hour
electronic leash?

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.

R's,
John