Re: [hrpc] I-D Action: draft-irtf-hrpc-political-05.txt

Niels ten Oever <mail@nielstenoever.net> Fri, 20 September 2019 12:46 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 44B7E120098 for <hrpc@ietfa.amsl.com>; Fri, 20 Sep 2019 05:46: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, RCVD_IN_DNSWL_NONE=-0.0001, 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 yb_hix5Ek0l4 for <hrpc@ietfa.amsl.com>; Fri, 20 Sep 2019 05:46:53 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4379212003F for <hrpc@irtf.org>; Fri, 20 Sep 2019 05:46:52 -0700 (PDT)
Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <mail@nielstenoever.net>) id 1iBIIl-0004EY-Rm for hrpc@irtf.org; Fri, 20 Sep 2019 14:46:50 +0200
To: hrpc@irtf.org
References: <156882005427.4606.6393818361687491816@ietfa.amsl.com> <bf565c7f-3c49-c113-66dd-c00508e5fd03@cs.tcd.ie>
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: <a7391931-5e06-7289-613e-646f66f8fe7b@nielstenoever.net>
Date: Fri, 20 Sep 2019 14:46:18 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <bf565c7f-3c49-c113-66dd-c00508e5fd03@cs.tcd.ie>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="oOvsOZa6wvL2sOAfFqTkd0E5MYYaN9GxY"
X-Authenticated-As-Hash: f1842a279235a42f6aa2a2a81130733515c5a4ec
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: 13680c0b130c155475ecde42c45f1d6c
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/8ssJTLCFCwUsPJSlUx08K8znJQo>
Subject: Re: [hrpc] I-D Action: draft-irtf-hrpc-political-05.txt
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: Fri, 20 Sep 2019 12:46:57 -0000

Thanks for this detailed review Stephen.

Because there was some quiet on the list (which might indicate some level of agreement (either with -05 and/or Stephen's comments, but I'll leave that to others to decide), I wrote a detailed response underneath and made changes in version -06.

On 9/19/19 10:46 PM, Stephen Farrell wrote:
> 
> Hiya,
> 
> I had a read of -05. I didn't read (but just skimmed) all
> the other comments before doing that so apologies if my
> comments repeat (or utterly contradict:-) others that've
> been sent to the list already.
> 
> Cheers,
> S.
> 
> General:
> 
> - Overall, I don't think this is ready. I do think it could be with
>   some more work, maybe another rev or two. Or it might take longer,
>   not sure.
> 

Working on next rev :)

> - If the authors didn't want to try aim for RG consensus on all of
>   the text, then I think that'd make it easier to get an RFC
>   published. I'd be ok with that, though I still think it'd need
>   another rev or two (but the changes might be easier/less).
> 

I'll leave that decision to the RG chairs. I am happy with either. But I do see this as a product of the discussions in hrpc, so publishing it outside of that would not do justice to the document and the people that contributed to it imho.

> - I'd argue to entirely re-do or delete section 5. I see why it's
>   included but I think in the end it didn't work out to be useful in
>   the same document as section 4.
> 

I removed section 5, but kept two para's and added them to the intro.

> Detailed comments:
> 
> - "undisputed" in the abstract is likely to be disputed:-) By
>   readers, I mean. s/undisputed/seems evident to the authors/ or
> something might be better.
> 

I do think it _is_ undisputed that the standards creation process is political and that they can be used for political means, right? But to make it go down easier:

s/undisputed/generally agreed 

> - intro: the Callon quote could do with a reference so readers can go
>   find more context if they want. The first sentence of that quote
> could mean lots of different things and I've no idea what exactly was
> meant - I'd ditch that sentence or maybe the entire quote.
> 

Callon is one of the parents of Science and Technology Studies, but I do agree that outside of the discipline, this quote might seem open for a lot of different interpretations. I removed it, with pain in my heart, and replaced it with two more specific quotes from the literature on standards.

> - intro: "affordances" - I've heard that term a number of times, but
>   I don't think I really understand it. Also - how are users
> "shaped"? I think you could have said that "people are affected by"

Suggestion accepted and changed.

> the technology, left it at that and been clearer.  (I see you define
> that in section 2, so I do get it now that I've gotten that far.
> Still might be better to avoid the forward reference if possible.)
>> - intro: does the document really "seek to answer" the question or
>   rather try to explore the question? The latter seems more
> tractable.
>

Accepted and changed.

 
> - intro: "The design of the Internet through protocols and
>   standards..." That seems to ignore the "running code" aspect which
> is critical to understanding how the Internet has arisen and evolves.
> 

It doesn't say 'exclusively through', but I appreciate the point. I changed it into:

The design of the Internet, and its codification through protocols and standards, is a technical issue with great political and economic impacts, as is described in {{RFC0613}} and {{RFC3271}}. 

> - The URL for [BramamI] doesn't work for me - my browser times out on
>   that. 

Fixed BramanI and Braman two, unfortunately Texas A&M does not offer TLS for this URI

(And why http and not https? :-) 


> As below, it'd be better to
> say a bit more about i18n here - it's fairly obvious but no harm
> expanding the bullet beyond one word.
> 

Am afraid this would deviate from the main point, since these are just illustrations. Previously the bullets were comma's, but Ted and Paul objected against that because with the references it impacted the readability.

But it indeed seems weird to have one word bullets, so I added one sentence summaries.

> - intro: The reference to RFC101 (better that than RFC0101 btw:-) is
>   unclear to me. There are many occurrences of the word access in
> that RFC so what's meant by the bullet point here? It's not clear to
> me.
> 

'how people are able to access the network, and who has control {{RFC0101}};'

> - intro: same point about rfc49 - that has two mentions of "security"
>   neither of which seem that relevant to this draft, so maybe say
> what/why that reference is for. (And there may be a better one, if
> what you've done is try find the earliest reference, that might not
> be the best thing.)


Added better reference and added privacy, as well as a description:

* privacy and security {{BramanIII}}; 

> 
> - intro: same points for the other early RFC references and I guess
>   [BramanII].
> 
> - intro: "This has been clearly shown in the work done by Sandra
>   Braman..." - what "this" do you mean has been shown? It's not clear
> to this reader.
> 

Changed into: 

Sandra Braman has foregrounded these political consideration in historical RFC in her extensively analysis of these documents {{BramanII}}.


> - section 3: Suggest s/Answering/Exploring/
> 

Accepted and changed

> - section 4: RFC1087 says "The Internet is a national facility..." so
>   I wonder if it's really so obvious a basis for the argument here.
> The problem is that 1087 kinda says "be ethical or we'll tell the
> Feds" and there aren't really equivalent Feds for today's Internet,
> so the sentence here could be a bit misleading.  Maybe better to
> qualify the reference here with something like "... even if the
> Internet in 1989 was largely a US thing, similar problems and
> requirements for ethical behaviour ought still apply." Not sure.
> 

Hmmm. This sentence does not say that the Internet is still the same, right? Just that is has been extensively discussed in earlier days?

But I've changed the sentence into:

Ethics and the Internet was already a topic of an RFC by the IAB in 1989 {{RFC1087}}, when the Internet was still looking entirely different.

> - 4.1: I note the references here are from 1991 and 1992 - isn't
>   there a more recent expression of this position that could be
> quoted? It left me wondering if the referenced authors might have
> changed their positions since (I've no idea if they have or not, just
> wondering, as my own ideas now are not what they were then:-)
> 

This is a relatively classical expression of this position, that is why I went with the classical definition of it (and the author expressing it). 

> - 4.2: This one is closest to my own position, but I wouldn't go
>   along with "requires" which is far too strong - for me it's more
> like this position "implies that protocols could be evaluated for..."
> 

Changed.


> - 4.3: Even if the Internet is too complex, that doesn't imply
>   anything for any one protocol. 

It means that the interrelation between protocols in hard to predict.

The rest of the 4.3 text also seems
> unclear to me. I'd say a rewrite of this section would be good.
> 

Added text and sought to increase readability.

> - 4.4: "The network..." do you mean the Internet or one of the
>   networks that make up the Internet here? Or do you mean any network
> of networks? I assume you mean any network of networks, like the
> Internet but I'm not sure.
> 

Fixed that by making it all 'network of networks'

> - 4.4: This seems to finish early or something. The end of the
>   section talks about social and technical but never says political
> so I'm unsure what a proponent of this position might believe vs. the
> other positions in section 4.
> 
> - 4.5 (1): I've no clue what the emotional bias of a medium such as
>   audio might be, or am I missing the point?
> 

What is meant here that a newspaper instills a very different perception than radio does. But to decrease misunderstanding I removed the second part of that sentence.

> - 4.5 (2): "speed of their information" is an odd phrase, and I'm not
>   sure what's meant.
> 

I think we can safely assume high bandwith and low latency is what is meant here.

> - 4.5: IMO the raven process was an attempt to be technical and
>   apolitical, at least as understood by some participants.  It's
> likely incorrect to give the impression that everybody thinks that
> the raven process was "largely political." (I do agree that many
> people think that.) 
> Similarly, while I agree that what "engendered"
> 7258 was Snowdonia, I do not agree that 7258 requires any
> justification that is non-technical (i.e. IMO 2804 and 7258 and 1984
> can all be sufficiently justified on purely technical grounds).
> Again, I think the change to make here is to say that someone
> espousing the position of 4.5 might agree with the current text, but
> that those statements about 2804 and 7258 are not universally
> accepted.

OK, I propose the following:

The Raven process in which the IETF refused to standardize wiretapping -- which resulted in {{RFC2804}} -- was an instance where an international governance body took a position that was perceived by many as political, although driven by a technical argument. 

> 
> - 4.5: Neither 2804 nor 7258 are protocol specifications.  For me
>   that significantly weakens the overall argument proposed in 4.5.
> Surely soeomne who espouses this position could provide at least one
> actual protocol example?  Presumably something that refers to 2804 or
> 7258 might suffice, but without that, there's a hole in the argument.
> (Not that I agree with the argument in 4.5, but I feel better
> disagreeing with something that isn't holed beneath the water line:-)
> 

Added:

The Raven process in which the IETF refused to standardize wiretapping -- which resulted in {{RFC2804}} -- was an instance where an international governance body took a position that was perceived by many as political, although driven by a technical argument. The process that led to {{RFC7258}} is similar: the Snowden disclosures, which occurred in the political space, engendered the IETF to act. While {{RFC2804}} was a statement about how a protocol for wiretapping would _not_ be developed, {{RFC7258}} was a statement that contributed to the development of protocols such as {{RFC7858}}, {{RFC8226}}, and {{RFC8404}}. The impact of political tensions on protocol development is summarized in {{Abbate}} who says: "protocols are politics by other means," emphasizing the interests that are at play in the process of designing standards.


> - 4.5: "consumer class" seems wrong to me. I don't believe there's
>   what I'd call a "consumer class" for NTP for example. I'm not clear
> from the phraseology as to whether the authors are asserting that
> espousing 4.5 means agreeing with Winner here or not. In any case, I
> think Winner is wrong here, for some protocols.

Removed 'consumer class', to avoid discussions about class, groups, and consumerism. I would offer the following:

Those who had the power to introduce a new technology also had the power to largely frame the uses of the technology "with new practices, relationships, and identities supplanting the old, --- and those who had the wherewithal to implement new technologies often molded society to match the needs of emerging technologies and organizations." {{Winner}}.

> 
> - section 5: "the different existing positions" - that's a claim that
>   secction 4 has the full set. My bet is that I could easily find an
> IETFer who espouses none of the above. s/the/some/ is better. Or you
> could say those are the postions that were considered in this work.
> 

Removed

> - section 5: s/were created/are created/ and "formal" isn't quite
>   right - TLS1.3 is getting closer to formal since bits of it were
> formally verified but it is not formally specified in one well-known
> sense of the term. s/formal// would be my suggestion. (I guess you
> just mean "written down" by this use of "formal" which seems
> unnecessary to me.)
> 

Removed

> - section 5: "100% royalty-free"? What? I'm misundertanding something
>   here. We had years of RSA and ECC being encumbered to the detriment
> of the Internet IMO, but 100% seems just wrong or else must be a
> badly stated statement of something else?
> 

Removed

> - 5.1: "enhance competition" may be true sometimes but is a) not
>   always true (I'll try assert NTP again as an example) and b) is far
> down my list of why to do work in the IETF, but is presented as if we
> all think this is the most important thing ever.
> 

Removed

> - 5.1: the discussion of "de facto" seems broken to me. Consider RFC
>   3986 vs. whatwg for a real example that doesn't seem to fit your
> description. (And I barf again at the mention of competition law for
> such things as URL syntax:-)
> 
Removed

> - 5.1: mention of ISO, BIS... etc with no references or URLs seems
>   wrong. (I've no idea what ABNT is for example, but I guess it's not
> what first shows up in my search [1].)
> 
>    [1] https://acronyms.thefreedictionary.com/ABNT

Removed

> 
> - 5.4: Are the authors agreeing with [Nadvi] or not? I think you
>   ought be clear. I'm not sure I'd agree that applies to the IETF
> though, as IETF participants don't, in general, seem to me to be
> well-decscribed as "transnational stakeholders" even though some or
> many of them may be. I don't feel like one of those anyway;-)

I've added that these are not exclusively transnational corporations.

> 
> - 5.4: The big [RogersEden] quote goes against IETF lore. I forget
>   where we have that written down in an RFC but I think we do. (Where
> "that" is "don't just end up with the union of the input proposals
> but instead try find the right outcome" or something like that.

Removed


> 
> - Section 5 generally: I was left thinking "huh, what was the point
>   of that section" when I finished reading that. I think you could
> mostly delete the entire section and be ok.
> 

Done

> - Section 6: I'd be happier if statements such as your opener did not
>   depend on buying books. Haven't Russel or Abate ever written these
> arguments down in something openly accessible?  

Nopes, they did not publish their papers in open access journals. I do have a problem with that, but I am afraid that is beyond my power to fix. 

> (And BramanII is
> still a broken link.) 

Fixed

> I don't think you've made the case via text or
> accessible references that this opening conclusion statement is
> correct. (I may agree with it, but I don't think you can justify it
> based on this.)
> 
> - Section 6: "undisputed" again - I dispute that that's the right
>   term.

s/undisputed/generally agreed
> 
> - Section 6: I do not accept the [Russell] quote as being correct but
>   haven't bought his/her book. I don't think you ought present that
> quote as being an accepted statement.

Made that more clear.

> 
> - Section 6: I dispute that the implementation of protocols "is"
>   political. I wrote some code last night for an I-D. That was not a
> politcal act (I assert).
> 

Would adding 'often' help?

While understanding that 'standards emerge from contested contexts, they immediately function as a means of control within the political and economic order' {{Russell}}, protocols and standards as abstract isolated artefacts might not be political, but their design, development, deployment, and implementation often is.


> - Section 6: I dispute that "protocols can never be understood"
>   without some inherently political framing. (If that's what you
> meant.) I can teach kids about TLS and they can understand the
> protocol without all the political add-ons. As it happens I do think
> they better understand what TLS is and how it's used, if I include
> some bits of that, but I don't believe it's needed for them to
> understand the protocol itself.
> 

I propose:

'Therefore we might need to give a qualified answer to the research question, in the sense that protocols can only be understood in part outside of their actual shaping, use, and applied function, which is political.'


> - Section 6: I dunno if I agree about the future research.

Would you care to elaborate? Happy to sketch other paths forward. 

Thanks again and happy to discuss.

Best,

Niels

PS If other people think their point(s) is a/are showstopper(s) and should be addressed, feel free to re-up your comments or message me off-list so I can address them in a following version.


> 
> 
> _______________________________________________
> 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