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

"Giovane C. M. Moura" <giovane.moura@sidn.nl> Mon, 27 June 2016 06:57 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 F343D12B065 for <hrpc@ietfa.amsl.com>; Sun, 26 Jun 2016 23:57:28 -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 gQMLAqMciQ8Z for <hrpc@ietfa.amsl.com>; Sun, 26 Jun 2016 23:57:26 -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 891F112B061 for <hrpc@irtf.org>; Sun, 26 Jun 2016 23:57:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn-nl; c=relaxed/relaxed; h=subject:references:from:to:cc:message-id:date:user-agent:mime-version:in-reply-to:content-type:content-transfer-encoding:x-originating-ip:x-clientproxiedby; bh=/cY8+k+G630iecshIvWpaO7XIKZsNlCRbTVfnNo45UQ=; b=u9hYaHMWcTNOFbHhjoyVD3WuRUtRKZq24kUd9D/IHkI/8mUQPub4Ib/iik3RpsXxbHfzkGlrL/kBGF0HbF245W7a1CJBDV3oV0TkfNeFrfeGFc38gZ5piCuxUzMT/uPo81izlq7zTLQJJbzVFYbXDVbn/wqvBdrp1C7k9HAGa989rhN49b+tcD7O1gHxj8eEd04p19lPHXSRIjnbNyKPtG4OOjyT2iIaei+SMgVmZMRL41S6x/2uegMK2NtrjDI6JhoQeu2ZzzCFfHTuV5MbAWj5DV0bkNL0JTkKBOzYO8FHigUzVvNuw/+6WatjtczvavwCPxlhSDnIoLpAo95V6g==
Received: from ka-mbx01.SIDN.local ([192.168.2.177]) by arn2-kamx.sidn.nl with ESMTP id u5R6vM6s006124-u5R6vM6u006124 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=CAFAIL); Mon, 27 Jun 2016 08:57:22 +0200
Received: from [94.198.159.132] (94.198.159.132) by ka-mbx01.SIDN.local (192.168.2.177) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Mon, 27 Jun 2016 08:56:05 +0200
References: <574ED2DC.30305@article19.org> <57517F7E.20506@sidn.nl> <5756A6F0.7010609@article19.org>
From: "Giovane C. M. Moura" <giovane.moura@sidn.nl>
To: hrpc@irtf.org
Message-ID: <9d2c3cb1-3f77-80e3-5740-8a74e9e32945@sidn.nl>
Date: Mon, 27 Jun 2016 08:57:09 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.1.0
MIME-Version: 1.0
In-Reply-To: <5756A6F0.7010609@article19.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [94.198.159.132]
X-ClientProxiedBy: ka-hubcasn02.SIDN.local (192.168.2.172) To ka-mbx01.SIDN.local (192.168.2.177)
X-FEAS-SPF: 2 / 2, ip=94.198.159.132, 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.132 as permitted sender) smtp.mailfrom=giovane.moura@sidn.nl
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/ZPvhLL0pj2vJxkVFKW3qM-stsoE>
Cc: a.l.vanwynsberghe@utwente.nl
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: Mon, 27 Jun 2016 06:57:29 -0000

Sorry Niels, I only had a chance to look at this now.

Please find my response inline.

> Not all questions are applicable to all protocols, but do you think none
> of the questions were relevant for you?

I went through all of questions now and here is my feedback.

First, I found it to be a good exercise that, most of all, helped me to
think it through our protocol design, helping me to re-evaluate it,
working as a eye opener to some properties.

As I experienced on a previous protocols and ethics implications
exercise[1], engineers unintentionally put their "values" (in
value-sensitive design terminology) in our protocols as if they were
just a given. Your draft help me to question those.

Since our draft is about intra-networking signaling[2], some questions
were not directly relevant. I enumerate them here. While I think all the
questions are important and have a different role, they may not apply to
all drafts in a same way. So I classified them with regards our own
draft only:

   * Relevant: 5.3.2.1.(1,2,3,4,6,7,8) , 14 (it's not dependable since
it is fall-back opportunistic),16,17,19,

   * More less relevant: 12 (there was a heated discussion on the
language issue in Buenos Aires, and if I am not mistaken, one of the
conclusions was that (i) is very hard to have it in protocol design and
(ii) maybe we should start at the application layer first, since it  is
the layer that directly interact with the users) , 15 (we employ fields
and data specified by another draft by other authors)

   * Not relevant: 5 (since its machine to machine signaling), 9 10
11,13, 18, (since it does not handle end-user data),20 (same reasons),

>>> 	- Changes you will make to your draft
>>> 	- Perhaps even a considerations paragraph that could be added to your
>>> draft.

I'll have to talk to my co-authors first (I am the last author on the
draft), but one easy change is to discuss the security considerations in
the light of human rights implications.


Other comments: on 5.3.2.1.9, first sentence " .. especially section
6.1.1 ?" . The link to 6.1.1. points to the same draft, but it should be
to RFC6973 I believe.

[1] http://doc.utwente.nl/87095/
[2] https://tools.ietf.org/html/draft-francois-dots-ipv6-signal-option-00


Thanks,

/giovane

>> 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...
>>
> 
> I think infrastructure and deeper layer protocol play a large role in
> inhibiting or stimulating an enabeling envrionment for human rights.
> 
> If this is not clearly communicated in the draft, we should change that.
> 
> 
>> 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]).
>>
> 
> And BGPSEC, etc, etc. Completely agree.
> 
>> Could you please share your thoughts on this  so I can carry on here
>> with the analysis?
>>
> 
> Hope this helps. Also feel free to have this conversation on the list, I
> think we (and others) can learn a lot from it.
> 
> Thanks so much for doing this.
> 
> Niels
> 
>> Thanks a lot,
>>
>> /giovane
>>
>>
>> [1] http://doc.utwente.nl/87095/
>>
>> [2] https://tools.ietf.org/html/draft-francois-ipv6-dots-signal-option-00
>>
>> [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.
>>>
>>>
>