Re: [hrpc] draft-irtf-hrpc-association-02

Niels ten Oever <mail@nielstenoever.net> Thu, 28 March 2019 12:19 UTC

Return-Path: <mail@nielstenoever.net>
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 70FD9120496 for <hrpc@ietfa.amsl.com>; Thu, 28 Mar 2019 05:19:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 vmjrb4e-fp4h for <hrpc@ietfa.amsl.com>; Thu, 28 Mar 2019 05:19:21 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B547C12042E for <hrpc@irtf.org>; Thu, 28 Mar 2019 05:19:16 -0700 (PDT)
Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <mail@nielstenoever.net>) id 1h9U01-0001tQ-7o for hrpc@irtf.org; Thu, 28 Mar 2019 13:19:14 +0100
To: hrpc@irtf.org
References: <e91dd252-6fcc-41c5-9077-b3934ddba7ea@avris-iPad>
From: Niels ten Oever <mail@nielstenoever.net>
Openpgp: preference=signencrypt
Autocrypt: addr=mail@nielstenoever.net; prefer-encrypt=mutual; keydata= mQINBFgpcR0BEACnfvNwTMlN+pyZT0AFYhWqxG3N4AoPIeNfbxLQH7dk8ZL7Ls05xtORfnu9 ovoaRrZpDufkMviUFidNYePbQNdgf63vWVgwpQR7utluwWraetcmZOu6tayJuyBK2b6d2Z23 MJAQxfa2/GMlN3QkvobaoyKtgbc8rOCgNla7WwkgtiVJ89xbAUHXPFpKWZluVRjaFh4p5C5r 7E5OvUiEGLQ5Cn2ir2PGIyIVqjB+hLTyaI6dIGCz2jtL0RATjmsmYUX7UkU/pz8MPPC2BJ5P KU9pdXMRBhAStxcph8vCo2ze9xSi3+1/5A2ULVtvO4s0hZ+exbTfMxMg3H5CCRFEEJXlQEXa Cd0ZHvqcv5xq8n9w/Ccd0CqYWATIwyP8Jlzd+BY3QGTWnWlgoAbs3Guh/pFYhEFNuuAF5Jk1 k5OlNGsRE/LQJmbT5SE7AtLJLbWewcHlEyIH+K6J8uVa4ExLXmRy+eRkFaxjGy3fLlUpy1Ee 1kU7VsQ/TZ8g8ujsMzxqsdB6y0TD/kVlWaDqPL6F+b+pm3lAuCBGWM1YZROTG58R6pD7sNVm i0ift4dIttAsg+2KoShm9A8kQ3tACXZDgNPC0l7VOqnVayjnF0RmjGeiX7PjOcLQCZ9a5wAH 5mrXMaKvfszqAVkP9HSrk1QVZOipF6vEimL43Czy7Rp1aUaUwwARAQABtChOaWVscyB0ZW4g T2V2ZXIgPG1haWxAbmllbHN0ZW5vZXZlci5uZXQ+iQJZBBMBCABDAhsjBQkJZgGABwsJCAcD AgEGFQgCCQoLBBYCAwECHgECF4AWIQQkWAtwXEr9ipSIZDoO2D86RorIswUCWyJaFgIZAQAK CRAO2D86RorIs8I2D/wNc4kT+dRC3Y9lSygeVWuxNj21z/QlbNvfXx9NicgBx4uCjsCm0ZhS 6qnp0uHYZYr8rdIzrL3GazyEuG9uvNzZBvIHm92UY1x0NH0TOVbGwJCWKULStvg9S+DjmNgp x8XM9amCtuXZyCiESeoOVRUanzD1JIidJtKgDfxvC63kqYoXl3azP0ra2nZbpktMm2fW5YdN D6kp6otjBH/jtpLay1CpVDS2Ehl3rLXJVUu96hlBnQB8q+64qyhTZ23HnbU+ib5Zb3OFgYoB KHjukJ4tV4x9rQprCQeirKX627vcNniDPnMp/nr9Qww6iVidX2vsG/22cx8MqLfs4B9tOVCJ Ft9D7MOwxOWgKnaYvrPZBOEmnuGq7btQe1tQZukL1Z83jKkV/e43k1gJaRt4Nl3/6YYCAlnn aQwRmySxznojsEl+X41UaJ6QFcoCphucOHoO9MeVzuNzgOgodXXEvlA8OJAqxRbE5AqB0leJ z1PfyrF1lsy8ETPRGKUKPBVed1vpZCQBfd/5RksOYBGhyfQ8p0w0hGs8SG6Xl6UtorJ+baLZ ZtnYbakfroxQBsF4bD/0P4fZ8wvTUDNLT8WN/9KFoTXrKn2pTLD+V9iw6nQAH4LSPw0G8XsL ce3Ihkf/2bvorGCUO7YXG4u6FPzEHsa/ZNfWHA5kbpGfwe2OVYNeI7kCDQRYKXEdARAAxYOE 3/AFmEfQ0SVVFujYFhZKX+BGXolYytC2a1soZogVYTIIlypxkRtN+ljteFAY3xX/El7cx5Fx j+uXvLKAm9xQRI/DCug7/NGULMk9bDK5bzSGw817cyiL5Kb+0RkWj2Y5ArOAK6XPGBZWZTHw yIawsSCN9AhDXZQWVRqkR1QXcq3IYKl+OHWMO7+1VfixCSakNf7T/Kiq46rQEPW8Eghk6CVO BR8xUCBbyk5aRW4VSGO6pUD3H21ur+5fTLsVyan1NHhxNNiXfnEJKr+JI5dXSkj7WqA5n8IT aNdFSAttkdT56wAQpxE2h8zaOmBaFUWQ4D8SdXDVymP5QMtLG+ItMMiNV6kXgsRFugAKM5yZ tPP9gIX+ic8QO5iuct37bRXJU/rmrH54Ab0kyAeeRE7oSsfTZPKvgtUh7VLAUEw/wy6TORJH E8JMaX0yYT6h4PGRS3mNM4bka8hjdfcrexI0zSqFOl2I22zQlG3YqSzIvVh98W67hxfAIaCV aTfJLFPEru3drxNwi6ogdkRmcLGKqqTgeYItrvITyFvzqbrcO2exp0KKEK3cDIZypqHHUf4+ uPlDtuExehLsNOMpjP8qhZpFtyLeDS07qunbvstcyvR30wOJ3DyAbHGzq739UyDcO9Jt5jwO DyVwk3MK5Em4pJ0+IAJx+F6gta0Bk2MAEQEAAYkCJQQYAQgADwUCWClxHQIbDAUJCWYBgAAK CRAO2D86RorIs0ykD/4t151SZG9MbeKRVKbs9Ecjady9bO0L3oBos4rhqY12ha8smFlsUzvb gB4CtkBuXQlq+plOBWv+rFEThOzy3bezgEDjlxycoO1W2wJD6E7Fo9fkHT6UOm9fQBkuKRqK 83OGnfM02qP1Ky8d7EoZz+nTSMf/DJgWw1YRKrXkMHBwKD83lCENsmePWE5AjMqk8cojPv9O y1wWy6fHjwx3r+wQSokBNfxgQyAFonmgBbhlic/pZUYRSIcldyUlaomrjFfr4egzmNE7aWDv LwOUYKevBIeJJcqTyfAn3TtJbPCEHOC2+lP6EcmPFyhQdiia+RqOClumqbWOPeQ2VM8j7NWv KKmBNBB5OJ/rmHogbNU+wWPJ723qMBoOp1jIwFNkQhx01W6v55VMwLr+IuBKY1ggJ2BhwQiG pWv4tMc5oB/qVh3my1VO65ErcJ3S9blpwJdDj5/YDOU7BKEmpRUP+xkaryNzH2x7FzrOOHzJ BX6jeYZabGvnTicQlBAzfGpblFqV3YN6EhCF2AHmGLTZ/DrjGYToIsW8cXlEMqN4u8ODEUY0 OhbnytnopKJKk99bwMoCqDkfQvT3LKDWtZj9NzFndfuoKXsVpwAitrG0mau0/16DKDyVWdtJ 9DYmtE40zO6g70VVxUj+dKt2hbJTy/KQTb7Ijhw7wZrGp/P7nhbVyA==
Message-ID: <0555df8d-5a4b-e78c-774a-b9665e1c5ca4@nielstenoever.net>
Date: Thu, 28 Mar 2019 13:19:10 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <e91dd252-6fcc-41c5-9077-b3934ddba7ea@avris-iPad>
Content-Type: text/plain; charset="windows-1252"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Authenticated-As-Hash: f1842a279235a42f6aa2a2a81130733515c5a4ec
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: 3a52d1843adabd8eff9dab316373a257
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/1G-OMBoC14GyJzek-znGblMwQEs>
Subject: Re: [hrpc] draft-irtf-hrpc-association-02
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "mail@nielstenoever.net" <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: Thu, 28 Mar 2019 12:19:34 -0000

Hi Avri,

Thanks for the comments, response inline:

On 3/28/19 12:02 PM, Avri wrote:
> Hi,
> 
> Again apologies for the last minute comments.
> 
> Abstract: saying that something establishes  ‘the causal link’ is a very strong claim.  Are we sure we want to make that strong a claim?  Can we really prove a causal link and can we prove that it is ‘the’ causal link. I personally do not see this draft as establishing any causal links, though it does point toward where they might be found.

Could you elaborate why? There is a research question, proposition, a clear understanding of the concepts, and the relation is shown consistently across various cases. So why do you think causality cannot be shown here?

> 
> Introduction: “by investigating the exact impact of Internet protocols on specific human rights,” again a very strong claim.  Can we ever really know the exact impact in some possible causal chain?  An even if we want to position a possible impact, we need more definitive illustrations and argumentation.

I think we describe quite a few cases. What are you missing?

> 
> There is an ambiguity between  allowing a right to prosper meaning a right is enabled, and what looks like a claim to a ‘right to prosper’. This is just a language nit, and I have avoided commenting on those for the most part, but this jumped out at me.
> 

Good point. Changed into:

One one hand, the right to freedom of assembly and association protects collective expression. Likewise, systems and protocols that enable communal interactions between people and servers enable this right given that the Internet itself was originally designed as "a medium of communication for machines that share resources with each other as equals" {{NelsonHedlun}}.



> 4. Methodology
> 
> “been further validated through confirmatory research in the form of Human Rights Protocol Reviews.” I think this is the primary reason for the HRPC to do reviews, but I do not beleive we have established a methodology for doing those yet. 

The reviews gathered data that we use for confirmation, for that they do not need to be standardized themselves, it is about the data they produce with furthered the relation.

> At this point some people are doing reviews and delivering them to responses that vary from happy acceptance to irritation to shock and awe. As far as I can tell we have not yet developed a systematic methodology for measuring the impact of the considerations in test reviews.

But that is also not the topic of draft-association, nor needed for the reviews to increase the validity of the claim. 

> Nor are we yet studying the reviews to see how they apply the considerations.  We have not yet established a rigorous method for testing our ethnographically established hypothesis. 

Idem.

> 
> “Even though the present work does not seek to create new guidelines, the conclusions could inform the development of new guidelines such as is done in draft-irtf-hrpc-guidelines.” I think we need a tighter binding between the discussion in this draft and anywhere in the guidelines where a consideration is said to be relevant to freedom of Expression/Assembly.

We did improve the interrelation, as you suggested during last session, do you have an idea how this could be done better?

> 
> Perhaps this is a personal academic prejudice, but while I think ethnography is extremely useful in hypothesis formation, I do not see how it can also serve to test and verify relevance and usefulness. Seems circular process to me. I think we need to find other methods for testing and measuring.
> 

You seem to say here that you reject ethnography as a scientific method to establish relations? Ethnography is the systematic study of groups of people and exactly aimed at understanding relations, so I hope you can provide more background to this, quite strong, claim.

> 6.  Cases and examples 
> 
> Seems like a loose collection of internet features that may or may not have a positive or negative affect on expression & assembly.  

Are you criticizing the method of case selection? Because what you describe seems to be indeed a case study format. 

I do not see the persuasive argument that shows the possibility of a causal chain.  Perhaps I am just not seeing it and others do, I accept.  Even in the two discussion sections, 7 & 8, the draft seems to jump from assertion to assertion without the rigor of argument that makes the conclusions inescapable. 

Could you comment in text? Because I think the discussions are quite tight.

 I do not see the arguments that show why consideration in general or why specific considerations would be significant in enabling or disabling the freedom of association and assembly, though the guidelines does make those sorts of claims.

I don't think this documents makes a statement about considerations at all, neither in the cases, nor in the conclusion. It just shows that there are interrelated concerns in RFC8280 and this document. During last session you asked us to foreground these interrelations, as you did above, and so we did.

But the argument is not about considerations, but about the relation between protocols and architecture and the right to association and assembly,

> 
> Re considerations:  While I understand that the authors do not want to introduce new considerations related to assembly and association - there may not be any new considerations or changes to existing considerations, I still think the draft needs to show a mapping between internet protocols and features and existing considerations.

These are mentioned after every case.

> 
> Note: I have not called them out, but the draft needs a spelling and grammatical scrubbing.

Agreed, will do. But also hope to work on this with the RFC editor. 

> 
> Thanks for continued efforts on this draft.
> 

Thanks for the review and happy to discuss.

Best,

Niels

> Avri
> 
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc
> 

-- 
Niels ten Oever
Researcher and PhD Candidate
DATACTIVE Research Group
University of Amsterdam

PGP fingerprint	   2458 0B70 5C4A FD8A 9488  
                   643A 0ED8 3F3A 468A C8B3