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

"John Levine" <johnl@taugh.com> Fri, 21 September 2018 16:52 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 C3A45130DFA for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 09:52:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, URIBL_BLOCKED=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 6CXgG1rISgeF for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 09:52:40 -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 F42131277CC for <ietf@ietf.org>; Fri, 21 Sep 2018 09:52:39 -0700 (PDT)
Received: (qmail 42797 invoked from network); 21 Sep 2018 16:52:39 -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; 21 Sep 2018 16:52:38 -0000
Received: by ary.qy (Postfix, from userid 501) id B960D2005265B4; Fri, 21 Sep 2018 12:52:38 -0400 (EDT)
Date: Fri, 21 Sep 2018 12:52:38 -0400
Message-Id: <20180921165238.B960D2005265B4@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Cc: avri@doria.org
Subject: Re: why exactly is HRPC for, was Diversity and offensive terminology in RFCs
In-Reply-To: <32d96826-38ff-4b40-a6c5-f979ac9dbfda@avris-iPad>
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/yxdIObEAm-DZs3lKa8JmHo4QHZw>
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 16:52:42 -0000

In article <32d96826-38ff-4b40-a6c5-f979ac9dbfda@avris-iPad> you write:
>It would be a pity to have this research group, which I thought was just beginning to find its stride and getting into the tough
>discussions, censored for its occasionable disagreeableness or touchy subjects. 

Thanks for your note, but if you reread the message you're responding
to, you'll see that you've gotten the problem exactly backwards.
The issue isn't that HRPC gets into tough discussions or touchy
subjects.  It's that it doesn't.  It has consistently looked only at a
narrow subset of rights issues, and completely ignored the rest of
them.  This myopic focus leads to results that I would say are at best
unfortunate.

Also, even though the HRPC is indeed an RG and not a WG, this
discussion started with a pretty clear request that the IETF change
the way it does business.  We have processes for that.  For starters,
where's the I-D about what the problem is and what to change?

R's,
John



>> On Sep 21, 2018 at 10:49,  <John R Levine (mailto:johnl@taugh.com)>  wrote:
>>   >  I strongly agree, and would go further. 
>> >  
>> >  As I see it, the HRPC suffers fundamental problems from both 
>> >  participation and its charter. 
>>
>> Thanks. I was going to write something like that but you said it better. 
>>
>> There are inherent tensions among different human rights. Free speech is 
>> great, but it enables trolling, phishing, and swatting. Censorship is 
>> bad, but most of us would prefer to censor phishes to our parents and 
>> tweets of porn photos with our daughters' faces pasted in. The 
>> traditional assertion is that the response to bad speech is more speech, 
>> but that was from an era when printing presses were expensive, and there 
>> weren't million-bot armies of screaming trolls. It is possible to think 
>> productively about this tension, as Dave Clark did in his terrific plenary 
>> talk at IETF 98, but unfortunately, he is an outlier. 
>>
>> I have spent over a decade arguing with people who imagine themselves to 
>> be human rights advocates and are unwilling to consider the implications 
>> of their narrow focus on speech and anonymity. (This month in the ICANN 
>> WHOIS debate, a well known professor in Georgia is spluttering that every 
>> security researcher who says that they use WHOIS data to shut down malware 
>> and catch crooks is lying.) I am not interested in joining HRPC because, 
>> like Eliot, I see no evidence of willingness to engagem with the real 
>> range of human rights issues. 
>>
>> In the IETF, yesterday on the regext list, "Human Rights Review of 
>> draft-ietf-regext-verificationcode" contains a long complaint that 
>> security features could be used to discriminate against people. Well, 
>> yes, that's what they're for. 
>>
>> https://www.ietf.org/mail-archive/web/regext/current/msg01768.html 
>>
>> In anything like its current form HRPC is harmful to the IETF because it 
>> gratuitously undermines our security efforts.