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

Niels ten Oever <mail@nielstenoever.net> Thu, 28 March 2019 17:36 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 BDA65120333 for <hrpc@ietfa.amsl.com>; Thu, 28 Mar 2019 10:36:57 -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 G5XJsfK8UTN4 for <hrpc@ietfa.amsl.com>; Thu, 28 Mar 2019 10:36:49 -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 10BA81202BC for <hrpc@irtf.org>; Thu, 28 Mar 2019 10:36:46 -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 1h9YxG-0006dX-Di for hrpc@irtf.org; Thu, 28 Mar 2019 18:36:45 +0100
To: hrpc@irtf.org
References: <e91dd252-6fcc-41c5-9077-b3934ddba7ea@avris-iPad> <CABtrr-U76xGXjiKW+DgpVkGU27B2Gb7YpZW-vBOSq-_R2XZRng@mail.gmail.com>
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: <27c2964d-e533-9ea3-bacf-763afe9111ee@nielstenoever.net>
Date: Thu, 28 Mar 2019 18:36:40 +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: <CABtrr-U76xGXjiKW+DgpVkGU27B2Gb7YpZW-vBOSq-_R2XZRng@mail.gmail.com>
Content-Type: multipart/mixed; boundary="------------13599EF1AE1BEBD757DA5696"
Content-Language: en-US
X-Authenticated-As-Hash: f1842a279235a42f6aa2a2a81130733515c5a4ec
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: 0f11aa2cf4c1a90be288da0592f0e54a
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/S54O20IZMUrIwHefncoW4_OcE4w>
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 17:36:58 -0000

Thanks for all the great reviews and comments. It is great to see a lot of new energy on this draft.

As mentioned, Gisela and I feel like we are not the best persons to integrate the proposed changes, so we would like to take a step back a lead authors and hope that others will step forward to take the lead to take this RG document further.

If there are no others who want to work as co-authors, perhaps the reviewers (and RG participants and others) could propose alternate text either in attached markdown document, or as pull requests on github ( https://github.com/IRTF-HRPC/drafts/blob/master/draft-association.md )?

Thanks in advance,

Niels and Gisela

On 3/28/19 3:26 PM, Joseph Lorenzo Hall wrote:
> I'm just going to share my own comments now, without having de-duped across Avri. Happy to clarify and let me know if I'm being brain-dead anywhere:
> 
>   *
>     https://tools.ietf.org/html/draft-irtf-hrpc-association-02
>   *
>       o
>         Abstract:
>       o
>           +
>             "causal”? That’s a pretty surprising claim to be making here… maybe I’m missing something?
>           +
>             It feels like the first sentence should be last, or that a final sentence should be added specific to association, or the entire abstract redrafted to focus more clearly on the specific right -- association -- the document addresses. 
>       o
>         Intro:
>       o
>           +
>             Could be edited to be a bit more concrete, and make the very good points it does make more clearly.
>           +
>             Define "epistemic community"
>           +
>             Typo: "As the Internet grows, decisions made about its architecture are become more important"
>           +
>             I would probably change “established” here to “described”: "[RFC8280] established the relationship between human rights and Internet protocols." 
>       o
>         Section 2:
>       o
>           +
>             might be good to have colons (“:”) after each term to distinguish the term from the definition?
>           +
>             can’t distributed systems have their behavior coordinated by other things than message passing? (e.g., a global clock).
>           +
>             The Infrastructure definition could benefit from being more concrete… I would think modifying a more standard definition first — e.g., "the basic physical and organizational structures and facilities (e.g. buildings, roads, power supplies) needed for the operation of a society or enterprise.”) — and then extending it would be better.
>           +
>             Internet seems to be a cluster of definitions… is the reader supposed to pick one, consider them all, or? 
>       o
>         4. Methodology:
>       o
>           +
>             Again, I would say “describe” instead of “establish” in "an initial effort to establish the relationship between human rights and the Internet architecture"
>           +
>             again with the “causal”: “it ultimately established either causal or deterministic relationships between aforementioned concepts through a series of case studies."
>           +
>             this is uncited… I’m not sure this document can claim anything further about 8280-like work without referencing something to show how individuals using 8280 have confirmed research in 8280: "further validated through confirmatory research in the form of Human Rights Protocol Reviews"
>           +
>             This definitely needs elaboration within the document! I know what these words mean methodologically-speaking, but I’ve never seen them composed like this and that may just be me being not familiar with this strain of research (despite being a qualitative methods geek): “we therefore aim to test the causal relationship through a case-selection method, where we have adopted a purposive sampling approach, aimed at the typicality and paradigmatic nature of the cases [SeawrightGerring] to help us achieve an attempt at an an ethnography of infrastructure [Star]." 
>       o
>         Section 5, Lit review:
>       o
>           +
>             I’d like to believe this but it’s not immediately obvious that the reference here supports the assertion made in this sentence: "The IETF itself, defined as a 'open global community' of network designers, operators, vendors, and researchers is also protected by freedom of assembly and association [RFC3233]." 
>       o
>         Section 6, cases and examples:
>       o
>           +
>             I really really like the clarity of the analysis in 6.1.1 in the third paragraph where each of the elements of free association are examined in that case… I see that other sections try to do this but aren’t nearly as clear and lucid as this first case. It would be great to try and tighten up the other cases analyses here.
>           +
>             wondering if the list at the end of each subsubsection might better be comma-delimited rather than dash-delimited.
>           +
>             6.1.2: hmmm, WebRTC is basically a two-party protocol, while PERC is the multi-party conference mixing version… so maybe “multi-party” should be modified here: "Multi-party video conferencing protocols like WebRTC [RFC6176][RFC7118]..."
>           +
>             6.2, certainly people share “proprietary” information via peer-to-peer tools and services… I think the point here is that peers don’t themselves encumber downstream recipients with additional terms that would make it hard to share further (but that the object being shared may have other proprietary interests such as copyright…). Not sure if we need to do anything here it was just a subtlety that might be confusing to some readers.
>           +
>             6.2.2: this should be modified to reflect the new GIT WG and drafts? "There have been two efforts to standardize the workflow vis a vis these third party services, but these haven't come to fruition: [Wugh] [GithubIETF]." 
>       o
>         Section 7: Discussion: Establishing the relation
>       o
>           +
>             can we find a different way to say “juridically”?
>           +
>             s/These preliminary finding suggest/These preliminary findings suggest/
>           +
>             I really like this section, although I think it is a bit overclaiming in that it seems to imply an exhaustive case set that would allow us to say things more definitively. E.g., I think this is a bit stronger than the draft can support in its current form: "The case studies show that the Internet infrastructure, the combination of architecture and protocols, facilitates freedom of association and assembly, by allowing groups of people to converse, collaborate, exchange, and build and maintain identities in both structural and occasional manners.” I guess we could try and think of more cases or just qualify this text a bit more that "these cases heavily support the assertion that…"
>           +
>               #
>                 The conclusion words this better, IMO (i.e., “some protocols”): “we established the relation between some protocols and the right tofreedom of assembly and association." 
>       o
>         Section 8:
>       o
>           +
>             I think this section is good, but I think it could benefit from a summary of what the cases showed to lend support that despite the *capacity* of the Internet to support association, it’s complicated and can be very fractured and increasingly proprietary. 
> 
> 
> On Thu, Mar 28, 2019 at 7:03 AM Avri <avri@apc.org <mailto:avri@apc.org>> 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.
> 
>     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.
> 
>     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.
> 
>     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.  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. 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. 
> 
>     “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.
> 
>     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.
> 
>     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.  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.  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.
> 
>     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.
> 
>     Note: I have not called them out, but the draft needs a spelling and grammatical scrubbing..
> 
>     Thanks for continued efforts on this draft.
> 
>     Avri
>     _______________________________________________
>     hrpc mailing list
>     hrpc@irtf.org <mailto:hrpc@irtf.org>
>     https://www.irtf.org/mailman/listinfo/hrpc
> 
> 
> 
> -- 
> Joseph Lorenzo Hall
> Chief Technologist, Center for Democracy & Technology [https://www.cdt.org]
> 1401 K ST NW STE 200, Washington DC 20005-3497
> e: joe@cdt.org <mailto:joe@cdt.org>, p: 202.407.8825, pgp: https://josephhall.org/gpg-key
> Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871
> 
> Don't miss out! CDT's Tech Prom is April 10, 2019, at The
> Anthem. Please join us: https://cdt.org/annual-dinner/
> 
> _______________________________________________
> 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