Re: [hrpc] review drafts with guidelines on human rights considerations

"Giovane C. M. Moura" <giovane.moura@sidn.nl> Fri, 24 June 2016 13:37 UTC

Return-Path: <giovane.moura@sidn.nl>
X-Original-To: hrpc@ietfa.amsl.com
Delivered-To: hrpc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6232812DAE2 for <hrpc@ietfa.amsl.com>; Fri, 24 Jun 2016 06:37:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.727
X-Spam-Level:
X-Spam-Status: No, score=-5.727 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sidn.nl
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 js76qC6WbzJx for <hrpc@ietfa.amsl.com>; Fri, 24 Jun 2016 06:37:23 -0700 (PDT)
Received: from arn2-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0267512DAEB for <hrpc@irtf.org>; Fri, 24 Jun 2016 06:37:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn-nl; c=relaxed/relaxed; h=to:from:subject:message-id:date:user-agent:mime-version:content-type:content-transfer-encoding:x-originating-ip:x-clientproxiedby; bh=ML2eihzde4UBKWDypYvoD0v6+TCAdkz55Uv3bbIZj3E=; b=D5pRTuAYykYKUPl0scRXFvBpFz2frj2ST4vUKzIJg2WW3RC14hPXWeR1gLr6WsbMaKA2DEo0uCZ18Lp+Ll+xm4wzzFl+FJ9aaKCTGHEqItx4LIdtv8EI04QkXv8VFm9q6GhGifdCrRanXQ1MDrbgwW6w+E7DSD+pQrB0oHGPa79Yp0yUBYkdHJuLfykcvR0zurlLPX10ls6GeWef/nS2t4wzBAKsnBOShYQL8fxRNRTIhPgPDPL7vNpTfFZR6/XonqtOCFneNdwyLUWt6IkrYo4aIMSlD5V5WCLXX0Ry0r3FjicmNWrla7OI858XM9vxfiUivmTpbKixqWSvNq2ciA==
Received: from ka-mbx01.SIDN.local ([192.168.2.177]) by arn2-kamx.sidn.nl with ESMTP id u5ODawrt024119-u5ODawrv024119 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=CAFAIL) for <hrpc@irtf.org>; Fri, 24 Jun 2016 15:36:58 +0200
Received: from [94.198.159.146] (94.198.159.146) by ka-mbx01.SIDN.local (192.168.2.177) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Fri, 24 Jun 2016 15:35:45 +0200
To: hrpc@irtf.org
From: "Giovane C. M. Moura" <giovane.moura@sidn.nl>
Message-ID: <817430ed-8916-494a-a358-e64035541e2e@sidn.nl>
Date: Fri, 24 Jun 2016 15:36:58 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.1.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [94.198.159.146]
X-ClientProxiedBy: ka-hubcasn01.SIDN.local (192.168.2.171) To ka-mbx01.SIDN.local (192.168.2.177)
X-FEAS-SPF: 2 / 2, ip=94.198.159.146, helo=, mailFrom=giovane.moura@sidn.nl, headerFrom=giovane.moura@sidn.nl
Authentication-Results: arn2-kamx.sidn.nl; spf=pass (sidn.nl: domain of giovane.moura@sidn.nl designates 94.198.159.146 as permitted sender) smtp.mailfrom=giovane.moura@sidn.nl
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/OJKXq7Yq3AwX4j3Yv0Oi32MTzV8>
Subject: Re: [hrpc] review drafts with guidelines on human rights considerations
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "niels@article19.org" <hrpc.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hrpc>, <mailto:hrpc-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hrpc/>
List-Post: <mailto:hrpc@irtf.org>
List-Help: <mailto:hrpc-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hrpc>, <mailto:hrpc-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2016 13:37:27 -0000

Hi,

I was having this conversation in private with Niels and Corinne, and he
asked me to maybe have this discussion on the list. So I'm forward it
here, and will answer his response in a following email.

Best,



Begin message.
From: Giovane Moura
To: Niels ten Oever, Corinne Cath
Date: Fri, 3 Jun 2016.


Dear Niels,

Thanks for reaching out.

I just went through your draft and, wow, congratulations on it, also on
its comprehensiveness and clarity.

Some feedback:

Section 1:

  * I guess it would be nice to have a phrase alerting about the values
that are implicitly embedded into a protocol.

In other words, engineers have their own set of values which they, often
without much thought, bring to their protocols, as it if was just a
given. This may have unintended/unforeseen consequences -- namely human
rights violations.

I've seen this first hand: I had to do a exercise like that for my
dissertation, by going through my school's ethics commission. In the
end, the ethicist (Aimee) and I wrote a case study paper on value
sensitivity design (VSD) and Internet security, and its consequences[1].
I was introducing bias, prejudice, unfairness with my approach, while
proving other values at the same time.

So what I mean is: engineers may unintentionally violate HR and values
while being oblivious to that, and this may be worth mentioning. I do no
know, however, how often this happens on IETF.

Relevance to the draft:

 - My draft can be found at [2], and when I tried to apply the questions
from 5.3 on it, and some of them didn't seem to apply to it.

And that's where I have another question: are those guidelines targeted
to protocols that assume a real human using it? E.g.: e-mail, chat, etc.
I.e.: protocols that are use to transmit data by anyway related to human
communications.

I am asking because our protocol is a control protocol, designed as a
SOS mechanism to be used by one server under attack (DDoS) to signal to
another servers that the attack is happening.

Therefore, it does not carry any metadata/data related to human
communication. If it is not human communication related, does it imply
that it does not violate human rights? I am not so positive on that
either...

For example: BGP is also machine to machine but if *used* poorly, can
and has been used in censorship cases (see Pakistan Youtube case[3]).

Could you please share your thoughts on this  so I can carry on here
with the analysis?

Thanks a lot,

/giovane


[1] http://doc.utwente.nl/87095/

[2]https://www.ietf.org/id/draft-francois-dots-ipv6-signal-option-00.txt

[3]
http://www.cnet.com/news/how-pakistan-knocked-youtube-offline-and-how-to-make-sure-it-never-happens-again/




> I hope this e-mail finds you well. As discussed in Berlin, Corinne and I
> worked hard to addressed all brought up issues in the
> hrpc-research-draft. You mentioned you would be interested in reviewing
> a draft your currently working on in the light of the guidelines for
> human rights considerations.
>
> I would like to kindly ask you to:
>
> 1. Take your draft
>
> 2. Read through the guidelines here:
> https://tools.ietf.org/html/draft-tenoever-hrpc-research-02#section-5.3.2
>
> 3. Make notes about your findings, especially relating the following
points:
> 	- Relevance for your draft
> 	- Changes you will make to your draft
> 	- Perhaps even a considerations paragraph that could be added to your
> draft.
>
> 4. Perhaps write a short evaluation paragraph in which you answer the
> following questions:
> 	- Was this a useful exercise
> 	- What can be improved?
> 		- Examples
> 		- Number of questions
> 		- Granularity of questions
> 		- Did going through the questionnaire feel like 'time well spent'?
> 	
> All your thoughts are very welcome.
>
> Best,
>
> Niels
>
> PS If you preper to talk about this rather than do a write up, am also
> more than happy to schedule a call with you.
>
>