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

Joseph Lorenzo Hall <joe@cdt.org> Thu, 28 March 2019 14:26 UTC

Return-Path: <jhall@cdt.org>
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 55A451204A0 for <hrpc@ietfa.amsl.com>; Thu, 28 Mar 2019 07:26:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cdt.org
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 gN58Lptw5iuY for <hrpc@ietfa.amsl.com>; Thu, 28 Mar 2019 07:26:18 -0700 (PDT)
Received: from mail-oi1-x236.google.com (mail-oi1-x236.google.com [IPv6:2607:f8b0:4864:20::236]) (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 74A59120494 for <hrpc@irtf.org>; Thu, 28 Mar 2019 07:26:18 -0700 (PDT)
Received: by mail-oi1-x236.google.com with SMTP id t206so15872666oib.3 for <hrpc@irtf.org>; Thu, 28 Mar 2019 07:26:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CsNXBD3rHM7ElMC76m2uS1Om8+dUiyljIxbG5jsIPqc=; b=cQK35va/IIhBOCJBx2OtCxJLnAgbTo3WgqpkULgE9J3CaysQ3vSOwyguPvojijcrdQ 9NYbGNRJsH6D3rVEUYBCx7swTQ1jdKyCGlNpIUcVIDYWyEEufpWloInSpAaEvmvNSCet ltii/s+5ehHuZn9oAnt5YjWEVv3/P0TtjQ/uc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CsNXBD3rHM7ElMC76m2uS1Om8+dUiyljIxbG5jsIPqc=; b=K1uL2BhLLmVl3uqXzUTjln8nETgTnXMqKY55cUH7dLguobdt1WxcG+GzKPzEYU0wjA dIH07gt21UAH4gX2kybeuSDiS4DzS6BQSeR40gufuxT+UCpJwrGHwAm1AhmM8Plw5JZn +Fvz5C4Szrynt0nZwt8HMPFwf1XD9ARuh8uCLqPZy8nJhI40iCW3+zOGXltAr8ydjaA5 bDvfTMA5BBdXuoj55awCFGcHJX+dQlTh5JLZHbc7d/cxvePmh/zj/JnXBOLDr6zoshCI PnHQvQcJXNdE6EF5fTqwC3yyDSLFQPnFjHt5G70ygmNJc4aSDN9jN+dQyBRDvvudpYNa 5eDA==
X-Gm-Message-State: APjAAAXT7soizsDE5cnwT30Afo7ZVMIUJuHAKH4C7mTj1Ry+63kHTq4b Yk+M/wHbHKfk4em7ePl6IjUvElv1/cEwW5rVLd8EBZtRKK2Ct0X3
X-Google-Smtp-Source: APXvYqwcNssefBpvG3SOhP8mwVsgUCkhr2NQ0tQ3gCij5Yo8LP0I65w9PnREsJHKcbZa6Q9kDB7iANn3jyH6KBLRjP0=
X-Received: by 2002:aca:378a:: with SMTP id e132mr155029oia.171.1553783177400; Thu, 28 Mar 2019 07:26:17 -0700 (PDT)
MIME-Version: 1.0
References: <e91dd252-6fcc-41c5-9077-b3934ddba7ea@avris-iPad>
In-Reply-To: <e91dd252-6fcc-41c5-9077-b3934ddba7ea@avris-iPad>
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Thu, 28 Mar 2019 10:26:05 -0400
Message-ID: <CABtrr-U76xGXjiKW+DgpVkGU27B2Gb7YpZW-vBOSq-_R2XZRng@mail.gmail.com>
To: Avri <avri@apc.org>
Cc: Hrpc <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="00000000000058ed8f05852856aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/axrM7rxzSuS1-IymACJGQ0Um0b4>
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 14:26:23 -0000

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
   -
      - Abstract:
      -
         - "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.
         - Intro:
      -
         - 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."
         - Section 2:
      -
         - 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?
         - 4. Methodology:
      -
         - 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]."
         - Section 5, Lit review:
      -
         - 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]."
         - Section 6, cases and examples:
      -
         - 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]."
         - Section 7: Discussion: Establishing the relation
      -
         - 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."
            - Section 8:
      -
         - 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> 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
> 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, 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/