
From nobody Wed May  2 01:00:06 2018
Return-Path: <mail@nielstenoever.net>
X-Original-To: hr-rt@ietfa.amsl.com
Delivered-To: hr-rt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F1C312D878 for <hr-rt@ietfa.amsl.com>; Wed,  2 May 2018 01:00:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 hXauvgGdEDgZ for <hr-rt@ietfa.amsl.com>; Wed,  2 May 2018 01:00:00 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (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 4BD52126C2F for <hr-rt@irtf.org>; Wed,  2 May 2018 00:59:59 -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 1fDmg6-0006uH-JO; Wed, 02 May 2018 09:59:55 +0200
From: Niels ten Oever <mail@nielstenoever.net>
To: Amelia Andersdotter <amelia@article19.org>, Shivan <shivankaul.1993@gmail.com>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, hr-rt@irtf.org, Gordon Lennox <gordon@lennox.paris>
References: <20180407153608.7v4zzra6qy3w3gfz@nic.fr> <CAG3f7Mg0zNbEJKEB5H38swyd3A6qAB5ogTaQ_2BLMP6j=xL2zQ@mail.gmail.com> <0adcac93-cf66-414b-85c2-119eea9f42e3@nielstenoever.net> <2aadec40-1583-e15b-6f66-f15e626382e4@article19.org> <f2647c8e-bb44-07fe-3575-4b4216db32b4@nielstenoever.net> <b5856287-8949-4d1b-73b9-3ef63967a73e@article19.org> <3215126c-a7b4-4399-31b9-c0f867188d61@nielstenoever.net>
Openpgp: preference=signencrypt
Autocrypt: addr=mail@nielstenoever.net; prefer-encrypt=mutual; keydata= xsFNBFgpcR0BEACnfvNwTMlN+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 5mrXMaKvfszqAVkP9HSrk1QVZOipF6vEimL43Czy7Rp1aUaUwwARAQABzSVOaWVscyB0ZW4g T2V2ZXIgPG5pZWxzQGFydGljbGUxOS5vcmc+wsGZBBMBCABDAhsjBQkJZgGABwsJCAcDAgEG FQgCCQoLBBYCAwECHgECF4AWIQQkWAtwXEr9ipSIZDoO2D86RorIswUCWG0tCwIZAQAKCRAO 2D86RorIs3pMD/9W/Tww1uLG0m0jQkBV3TmBOVzS79fVyoj6lEYCNPJigCqOi9wbZSTB2HL6 h4ftSCl4ErGHcIqngRPcNRt7G8/3OoA1h6qRHcqrpS6H4niW1E+rtxIxul+PSsXXZEgDyUSK XXczf4MmRbR6tKGY4hp4KFedSOEL2C0j8htB2um4C8KFyX4gAYMPJoBfZqlrCmXsyLjdjIvN wd7FLLKA6CNVjwYsDgmKiLQm0Np4fz1AW72rnGGktyUT3u0GsbyDmwM6YU80anh647Pc7cyo ie6c21Ajcph1k7BjHAB/EopQzoQVporHFrCNqhpgVXihhlVDGdOD1JSHCgWO4toflJAT6+kP 3uOXeHv6AoLcXKnY/8QWFjwoj9DYtpw4bSsiP++sF3Dg0xaaivvOzU5+IBoSxNTnqj0M7/Fk jergVF60QdwMGukFZDMSjFnX/gvFPbxy4JebvrfzSY5ZJxLjrlswSeVkWTU1DvtfJxJHKTPQ 9dnodrSN3vynJS+u+wRbzQLdSLBgSgGbUVVHu2dyJhXGPwoh/2Gu4gFilV6+dBhcwHwuxlsd 0pdnTdq4wJodT1rDZRgP3QjR+miyFqjahUDMTJlf4BRq6CiWiHb5UfvQvUsPtMLfQafqYCEy 98b4RHnbckPXa+pXRTYz3z9CBuiJTQWTT0CIBVLhyzqQjYrFTM7BTQRYKXEdARAAxYOE3/AF mEfQ0SVVFujYFhZKX+BGXolYytC2a1soZogVYTIIlypxkRtN+ljteFAY3xX/El7cx5Fxj+uX vLKAm9xQRI/DCug7/NGULMk9bDK5bzSGw817cyiL5Kb+0RkWj2Y5ArOAK6XPGBZWZTHwyIaw sSCN9AhDXZQWVRqkR1QXcq3IYKl+OHWMO7+1VfixCSakNf7T/Kiq46rQEPW8Eghk6CVOBR8x UCBbyk5aRW4VSGO6pUD3H21ur+5fTLsVyan1NHhxNNiXfnEJKr+JI5dXSkj7WqA5n8ITaNdF SAttkdT56wAQpxE2h8zaOmBaFUWQ4D8SdXDVymP5QMtLG+ItMMiNV6kXgsRFugAKM5yZtPP9 gIX+ic8QO5iuct37bRXJU/rmrH54Ab0kyAeeRE7oSsfTZPKvgtUh7VLAUEw/wy6TORJHE8JM aX0yYT6h4PGRS3mNM4bka8hjdfcrexI0zSqFOl2I22zQlG3YqSzIvVh98W67hxfAIaCVaTfJ LFPEru3drxNwi6ogdkRmcLGKqqTgeYItrvITyFvzqbrcO2exp0KKEK3cDIZypqHHUf4+uPlD tuExehLsNOMpjP8qhZpFtyLeDS07qunbvstcyvR30wOJ3DyAbHGzq739UyDcO9Jt5jwODyVw k3MK5Em4pJ0+IAJx+F6gta0Bk2MAEQEAAcLBZQQYAQgADwUCWClxHQIbDAUJCWYBgAAKCRAO 2D86RorIs0ykD/4t151SZG9MbeKRVKbs9Ecjady9bO0L3oBos4rhqY12ha8smFlsUzvbgB4C tkBuXQlq+plOBWv+rFEThOzy3bezgEDjlxycoO1W2wJD6E7Fo9fkHT6UOm9fQBkuKRqK83OG nfM02qP1Ky8d7EoZz+nTSMf/DJgWw1YRKrXkMHBwKD83lCENsmePWE5AjMqk8cojPv9Oy1wW y6fHjwx3r+wQSokBNfxgQyAFonmgBbhlic/pZUYRSIcldyUlaomrjFfr4egzmNE7aWDvLwOU YKevBIeJJcqTyfAn3TtJbPCEHOC2+lP6EcmPFyhQdiia+RqOClumqbWOPeQ2VM8j7NWvKKmB NBB5OJ/rmHogbNU+wWPJ723qMBoOp1jIwFNkQhx01W6v55VMwLr+IuBKY1ggJ2BhwQiGpWv4 tMc5oB/qVh3my1VO65ErcJ3S9blpwJdDj5/YDOU7BKEmpRUP+xkaryNzH2x7FzrOOHzJBX6j eYZabGvnTicQlBAzfGpblFqV3YN6EhCF2AHmGLTZ/DrjGYToIsW8cXlEMqN4u8ODEUY0Ohbn ytnopKJKk99bwMoCqDkfQvT3LKDWtZj9NzFndfuoKXsVpwAitrG0mau0/16DKDyVWdtJ9DYm tE40zO6g70VVxUj+dKt2hbJTy/KQTb7Ijhw7wZrGp/P7nhbVyA==
Message-ID: <053a8b99-94b6-6e34-eaad-09769200d574@nielstenoever.net>
Date: Wed, 2 May 2018 09:59:45 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <3215126c-a7b4-4399-31b9-c0f867188d61@nielstenoever.net>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="1TKugopGPxYgBte4tKbJBOycq0SOEsUr3"
X-Authenticated-As-Hash: f1842a279235a42f6aa2a2a81130733515c5a4ec
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: 6808d40ac62ae801629a699503458227
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/Umwt8ggezrHLsoF5BMCwTFQE_OI>
Subject: Re: [HT-rt] [execd@iab.org: Call for Comment: <draft-iab-marnew-report-01> (IAB Workshop on Managing Radio Networks in an Encrypted World (MaRNEW) Report)]
X-BeenThere: hr-rt@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Human Rights Protocol Considerations Review Team <hr-rt.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hr-rt/>
List-Post: <mailto:hr-rt@irtf.org>
List-Help: <mailto:hr-rt-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 08:00:04 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--1TKugopGPxYgBte4tKbJBOycq0SOEsUr3
Content-Type: multipart/mixed; boundary="232ydfrqMMKzglwelWm00ubFWMXQH0YwU";
 protected-headers="v1"
From: Niels ten Oever <mail@nielstenoever.net>
To: Amelia Andersdotter <amelia@article19.org>,
 Shivan <shivankaul.1993@gmail.com>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, hr-rt@irtf.org,
 Gordon Lennox <gordon@lennox.paris>
Message-ID: <053a8b99-94b6-6e34-eaad-09769200d574@nielstenoever.net>
Subject: Re: [HT-rt] [execd@iab.org: Call for Comment:
 <draft-iab-marnew-report-01> (IAB Workshop on Managing Radio Networks in an
 Encrypted World (MaRNEW) Report)]
References: <20180407153608.7v4zzra6qy3w3gfz@nic.fr>
 <CAG3f7Mg0zNbEJKEB5H38swyd3A6qAB5ogTaQ_2BLMP6j=xL2zQ@mail.gmail.com>
 <0adcac93-cf66-414b-85c2-119eea9f42e3@nielstenoever.net>
 <2aadec40-1583-e15b-6f66-f15e626382e4@article19.org>
 <f2647c8e-bb44-07fe-3575-4b4216db32b4@nielstenoever.net>
 <b5856287-8949-4d1b-73b9-3ef63967a73e@article19.org>
 <3215126c-a7b4-4399-31b9-c0f867188d61@nielstenoever.net>
In-Reply-To: <3215126c-a7b4-4399-31b9-c0f867188d61@nielstenoever.net>

--232ydfrqMMKzglwelWm00ubFWMXQH0YwU
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi Shivan and Amelia,

Has this been submitted?

The official deadline was yesterday, but it might still be accepted if
it is submitted today.

Best,

Niels

On 04/11/2018 11:07 AM, Niels ten Oever wrote:
> Hi Amelia,
>=20
> We don't need a specific format, we can simply send an email with the
> review.
>=20
> Cheers,
>=20
> Niels
>=20
> On 04/09/2018 07:23 PM, Amelia Andersdotter wrote:
>> How easiest to draft?
>>
>> i started something here:
>> https://github.com/nllz/IRTF-HRPC/pull/221/files#diff-989e50ba297c8bab=
8fe8fbd3759ac6d2
>>
>>
>> there's some semantics in this (first), and then i started the
>> evaluation by removing those considerations that i thought were either=

>> already addressed, or that would best be addressed elsewhere.
>>
>> i find it ironic that the telcos don't want to share their APIs /with
>> their own customers and users(!)/ out of competition concerns. normall=
y,
>> i'm the customer of by telco, i don't compete with it.
>>
>> but a big problem in the mobile markets could then be that vertically
>> integrated operators can be both mobile OS or mobile app providers /an=
d/
>> Mobile Network Operators at the same time. Oh, if only the telcos had
>> lobbied for a competetitve market regulation(!) how many of their
>> current predicaments (and also end-user human rights concerns) could b=
e
>> solved. but ok.
>>
>> /end whiny transmission
>>
>> amelia
>>
>>
>> On 2018-04-09 13:42, Niels ten Oever wrote:
>>> Hi Amelia,
>>>
>>>
>>> On 04/08/2018 10:19 PM, Amelia Andersdotter wrote:
>>>> I guess the task is to apply the Human Rights Guidelines from RFC 82=
80?
>>>>
>>> Rather the guidelines doc:
>>> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-00
>>>
>>> And feedback any potentially useful changes.
>>>
>>>
>>>> It's a workshop. As I read the draft report GSMA is defending their
>>>> regulatory and commercial interests, and IETF is saying "well, make =
it
>>>> work while stuff is encrypted".
>>>>
>>>> So do we mean to criticize GSMA's self-perceived political/commercia=
l
>>>> interests from a HR perspective?
>>>>
>>> We seek to understand the potential impact for the ability of end-use=
rs
>>> to excercise their human rights, a consequence for that could be to
>>> criticize the proposed architectural reordering.
>>>
>>>> =3D=3D=3D=3D
>>>>
>>>> The workshop appears not to have touch on the upcoming ePrivacy
>>>> regulation in the EU at all, in spite of it having a fairly big impa=
ct
>>>> on many GSMA members. In particular, GSMA has been lobbying /against=
/
>>>> the ePrivacy regulation, in spite of the IETF helpfully solving many=
 of
>>>> their regulatory challenges under the law.
>>> Interesting - this could fall under the privacy part.
>>>
>>>> Telcos are in the place where they want to sell amounts of data. HTT=
PS
>>>> increases the amount of data, making telco consumer potentially
>>> decreases, right?
>>>
>>>> unhappier. Encryption can also slow stuff down, and while some vendo=
rs
>>>> say that that's an issue of the past, it's possible that it isn't in=
 for
>>>> instance the developing world. Probably Facebook Free Basic connecti=
ons
>>>> have data on this.
>>>>
>>>> In some countries, notably the UK, telcos may be under obligation to=

>>>> generally filter connections (ensure they're porn-free). I find that=

>>>> policy disagreeable, but nevertheless it's there. For telcos it's a
>>>> challenge.
>>>>
>>> This has an impact on FoE. I don't think we need to have an opinion o=
n
>>> everything from the get-go, but rather show the (potential) implicati=
ons.
>>>
>>>> In Sweden, before the EU open internet regulation entered into effec=
t,
>>>> several telcos were investigated for traffic prioritisation (which w=
as
>>>> suspected to run contrary to ePrivacy directive obligations not to
>>>> monitor traffic). Ironically, the EU open internet law kind of permi=
tted
>>>> commercially motivated traffic discrimination so those inquiries hav=
e
>>>> since been cancelled. The new ANACOM case in Portugal may change thi=
s
>>>> interpretation of what the open internet regulation says, but I don'=
t
>>>> perceive Portugal to be heading in that direction.
>>>>
>>> Cheers,
>>>
>>> Niels
>>>
>>>> best regards,
>>>>
>>>> Amelia
>>>>
>>>> On 2018-04-08 12:30, Niels ten Oever wrote:
>>>>> Amelia know more about radio networks than I do methinks, but happy=
 to
>>>>> do so if Amelia is not available.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Niels
>>>>>
>>>>> Sent from Blue <http://www.bluemail.me/r?b=3D12687>
>>>>> On Apr 7, 2018, at 22:43, Shivan <shivankaul.1993@gmail.com
>>>>> <mailto:shivankaul.1993@gmail.com>> wrote:
>>>>>
>>>>>     I could take a look, if someone could work with me.
>>>>>
>>>>>     On Sat, Apr 7, 2018, 11:36 AM Stephane Bortzmeyer
>>>>>     <bortzmeyer@nic.fr <mailto:bortzmeyer@nic.fr>> wrote:
>>>>>
>>>>>         Obvious HR consequences. Any volunteer?
>>>>>
>>>>>
>>>>>
>>>>>         ---------- Forwarded message ----------
>>>>>         From:=C2=A0IAB Executive Administrative Manager <execd@iab.=
org
>>>>>         <mailto:execd@iab.org>>
>>>>>         To:=C2=A0IETF Announcement List <ietf-announce@ietf.org
>>>>>         <mailto:ietf-announce@ietf.org>>
>>>>>         Cc:=C2=A0
>>>>>         Bcc:=C2=A0
>>>>>         Date:=C2=A0Tue, 03 Apr 2018 15:08:39 -0700
>>>>>         Subject:=C2=A0Call for Comment: <draft-iab-marnew-report-01=
> (IAB
>>>>>         Workshop on Managing Radio Networks in an Encrypted World
>>>>>         (MaRNEW) Report)
>>>>>         This is an announcement of an IETF-wide Call for Comment on=

>>>>>         draft-iab-marnew-report-01.
>>>>>
>>>>>         The document is being considered for publication as an
>>>>>         Informational RFC
>>>>>         within the IAB stream, and is available for inspection at:
>>>>>         https://datatracker.ietf.org/doc/draft-iab-marnew-report/
>>>>>
>>>>>         The Call for Comment will last until 2018-05-01. Please sen=
d
>>>>>         comments to
>>>>>         architecture-discuss@ietf.org
>>>>>         <mailto:architecture-discuss@ietf.org> and iab@iab.org
>>>>>         <mailto:iab@iab.org>.
>>>>>
>>>>>
>>>>>         Abstract
>>>>>
>>>>>         =C2=A0 =C2=A0The MarNEW workshop aimed to discuss solutions=
 for bandwidth
>>>>>         =C2=A0 =C2=A0optimisation on mobile networks for encrypted =
content, as
>>>>>         current
>>>>>         =C2=A0 =C2=A0solutions rely on unencrypted content which is=
 not
>>>>>         indicative of the
>>>>>         =C2=A0 =C2=A0security needs of today's Internet users.=C2=A0=
 The workshop
>>>>>         gathered IETF
>>>>>         =C2=A0 =C2=A0attendees, IAB members and various organisatio=
ns involved
>>>>>         in the
>>>>>         =C2=A0 =C2=A0telecommunications industry including original=
 equipment
>>>>>         =C2=A0 =C2=A0manufacturers and mobile network operators.
>>>>>
>>>>>         =C2=A0 =C2=A0The group discussed the current Internet encry=
ption trends and
>>>>>         =C2=A0 =C2=A0deployment issues identified within the IETF, =
and the
>>>>>         privacy needs
>>>>>         =C2=A0 =C2=A0of users which should be adhered.=C2=A0 Soluti=
ons designed
>>>>>         around sharing
>>>>>         =C2=A0 =C2=A0data from the network to the endpoints and vic=
e versa were then
>>>>>         =C2=A0 =C2=A0discussed as well as analysing whether the cur=
rent issues
>>>>>         experienced
>>>>>         =C2=A0 =C2=A0on the transport layer are also playing a role=
 here.=C2=A0 Content
>>>>>         =C2=A0 =C2=A0providers and CDNs gave an honest view of thei=
r experiences
>>>>>         delivery
>>>>>         =C2=A0 =C2=A0content with mobile network operators.=C2=A0 F=
inally, technical
>>>>>         responses
>>>>>         =C2=A0 =C2=A0to regulation was discussed to help the regula=
ted
>>>>>         industries relay
>>>>>         =C2=A0 =C2=A0the issues of impossible to implement or bad-f=
or-privacy
>>>>>         technologies
>>>>>         =C2=A0 =C2=A0back to regulators.
>>>>>
>>>>>         =C2=A0 =C2=A0A group of suggested solutions were devised wh=
ich will be
>>>>>         discussed
>>>>>         =C2=A0 =C2=A0in various IETF groups moving forward.
>>>>>         _______________________________________________
>>>>>         HR-rt mailing list
>>>>>         HR-rt@irtf.org <mailto:HR-rt@irtf.org>
>>>>>         https://www.irtf.org/mailman/listinfo/hr-rt
>>>>>
>>>>>     ---------------------------------------------------------------=
---------
>>>>>
>>>>>     HR-rt mailing list
>>>>>     HR-rt@irtf.org
>>>>>     https://www.irtf.org/mailman/listinfo/hr-rt
>>>>>
>>
>=20


--232ydfrqMMKzglwelWm00ubFWMXQH0YwU--

--1TKugopGPxYgBte4tKbJBOycq0SOEsUr3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEJFgLcFxK/YqUiGQ6Dtg/OkaKyLMFAlrpb/EACgkQDtg/OkaK
yLODfA//SkOnEvodO9Kfu3qGv1QDFlCruB7u6OKDzR9zz4TDi+jLkpaoQlvt6SfM
PE8HRLZ+FW98xtd3/l0m2kt6sXudQDtE6hySmPOR7QgMJg24f0XkAYKV93V1HIsR
QxU4E9w3C8KgJqvZ22hzf8XSZG0/4v6Oj9veB9mMMFYn0t8SbTjRX3CNNci7BUqZ
o6StEVABbXkabCxnqxRy1GnMR6ruKIcN4uZ+CXCC1De69RAiEVEUgvBTn83sRaEk
MGxXPpRQtNsJJxVwqhiGQ+I3Vt8ifVDVpIA/+0eA0l6/tI7roMfR9xt1aQRve3ng
VCYTj5bf7TGf1CZJttrvfwbYYSjOTKffJxlynebuR7uFcujYRwhFQeTNoVuoR0eb
LlpqMS/vU8XtbJTH08iRMgB+NUOUI4gtW9jLXoSad4WDeTI16ptfSMp27MxnOGl/
eXG8po6U3JQkJrcl/CmV9t0cYNCUf0hWDTnF4JYS2k+Vr8+8bZL+3ailRHse8GMF
M7E0XwaTMl8xc8mDXcypfGEZGIH9InuMJR4/Ltn2EGEwysjBGdZa0vrNy06xC9Qx
yFnFE0MqyhtlCk1vXErk0g2nRcyoBDHrLjlbr0S3f+e+Kp6mFBgFpUka9D5/LAX9
CqKDylnX+fxmkGd+azNczNlA7+4/2J3CJcnEeP5c/LOrYTxUrcA=
=rd+q
-----END PGP SIGNATURE-----

--1TKugopGPxYgBte4tKbJBOycq0SOEsUr3--


From nobody Wed May  2 01:30:36 2018
Return-Path: <mallory@article19.org>
X-Original-To: hr-rt@ietfa.amsl.com
Delivered-To: hr-rt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ABAC124319 for <hr-rt@ietfa.amsl.com>; Wed,  2 May 2018 01:30:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 mbCn3M2fvr_i for <hr-rt@ietfa.amsl.com>; Wed,  2 May 2018 01:30:32 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (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 239F71242F5 for <hr-rt@irtf.org>; Wed,  2 May 2018 01:30:32 -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 <mallory@article19.org>) id 1fDn9h-0008LS-Bb for hr-rt@irtf.org; Wed, 02 May 2018 10:30:30 +0200
To: hr-rt@irtf.org
References: <583d18fe-c3ad-38f4-c92a-faf04978c59a@nielstenoever.net>
From: Mallory Knodel <mallory@article19.org>
Openpgp: preference=signencrypt
Autocrypt: addr=mallory@article19.org; prefer-encrypt=mutual; keydata= xsBNBEx0TWcBCAC8sirY3nlDnRwY6XWmsvZtM9kmEK6H8no3ZuQ723PKwHOddw1nOykh0in/ /QGRmwtyVzsfLh6/94UUZTn10oo+xGAfw2gf1on5IJTIiphykk732PNnUakVGWwHNKQquTVc kLrydUaFVMb89BAXqExBKlMg2ciEjzbYMCs3I/qZAZ0Wr5nF3RQS8O78elTNAgWTZ98yKTZV DlRoDpnvbfwtIPqnISoSjDEvEUBdpykvS3jHqlR1f6Mx6Xs97S5CORaer/0qTcDm0PAb1Z9l IhMsFl05tNt2FpgS4/RN8NyLasAQNOlScpTJbAfRuyyvRm1N8GLIL1KX+YYeLyqzhdhZABEB AAHNJU1hbGxvcnkgS25vZGVsIDxtYWxsb3J5QG1heWZpcnN0Lm9yZz7CwJgEEwECAEICGwMG CwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAhkBFiEE4+tj4GWjskC82bBxDDKicb08x4AFAlqo 9WUFCRAV234ACgkQDDKicb08x4DklAf+ODKRmP6C2MnBz6vL8N8l3vZJUqoRcYXTn3uTpT05 Wou87ZIZ/P/OV2/uOMKkczLQQydj5S8PxbLTeg+U5f/63hdy99ON+K2b4izg7Qasdl1SqXTH q1pmhbrcbLbVKDJ345fdEg7RuMnv4gd3EaT/yQa99zHy8JHaBKaPEUQAa65HTt2Sy2c6L6BA aMZx1TOZ9/cZ7L1gJyytJbEyvg/JLOatJEI4rewUWU2TMSGJijwjAUBagwDPWyxpz+vXdKsD tqRTpY4xvXaeUQo0QXf0c5j1Gcglzv7ywZcyz1MGD1aLS9/CqeB3I4EMbvH/33LS3jNkfKbV XOTSjmo7l22CNc7ATQRMdE1nAQgA4mpP2LjFuAW2li9FPbDYOMzt0MtThXsnvHyY0fDv8FlU qnKgPrMY80VHntnxwqepFS3ncunVX4ipq+fadta+LHpTnbJSmlphBrc9qGJxqcjwf4yo35Xh OXCJFwnaoAwIX237lXRe4Xh6X4VMuJt8jiZdvgpbk/whvQH2grcq8KjCcy1iuL5pBl8ZwYG/ dphitFhQdqEcnc/krIqG4KQgKiUi3K/GR0OeEmw/cscWD7/CLEo7eHiaGQhSOyDQbM+Iu2o/ 6uMXMUPsYlMMqgmVL68zMacO3PE17jx0rQ8oZ7CpBY8YZWOWrzXrtFT8JO9guuCPsvd4KT6y 97y9LRJlPQARAQABwsB8BBgBAgAmAhsMFiEE4+tj4GWjskC82bBxDDKicb08x4AFAlqo9WYF CRAV238ACgkQDDKicb08x4DU4QgAmlyBlFhfU0jpkbyD3HQ+3CJqWdBT422pVIrj3qNT2ehy fWO66Muidmd4Y279uV3p3TQEJOQvnV7FVAC9+bI7AdBy00BAjHgJ5eSQZxKTXUoeeBAsTZHN /HaHewjYWHMvCuuzir/Wt3A6Cehh8gp9I/Vg+oL3dTldVqqgZLgnA83bT/R8fI/e85LDlpdx KJ0+uy/grg3AbH7LUUrmMIC2iO8mQWYuNlizsUZLFvJhCAU2c5l8B5mv2BoWFhL+l7mmNcdF bwBFXon7Ea1jkCnbWVxtXkPYkcuWuMSTJswn9HhZVJWjUonKqUZKAb9PxRzC9crZ+X14tQT3 iJt2a4ZM4w==
Message-ID: <1a7c1de3-f98b-9357-554b-1843601be176@article19.org>
Date: Wed, 2 May 2018 11:30:26 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <583d18fe-c3ad-38f4-c92a-faf04978c59a@nielstenoever.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: 1f72ff50073f138f9668c095d6f579a1
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/mPf8uB4UNMszf71c7fH-YY0h-zI>
Subject: Re: [HT-rt] drafts for analysis
X-BeenThere: hr-rt@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Human Rights Protocol Considerations Review Team <hr-rt.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hr-rt/>
List-Post: <mailto:hr-rt@irtf.org>
List-Help: <mailto:hr-rt-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 08:30:34 -0000

On 27/04/18 13:29, Niels ten Oever wrote:
> Mallory also had some ideas about analyzing RFCs, and I think Gurshabad
> might have some ideas abt that as well.

This is my draft skeleton for a matrix on suggesting I-Ds or RFCs to
analyse:

 * Content relevance
 ** Does the I-D or RFC relate to areas outlined in RFC 8280?
 ** Are members of the review team already engaged in the working group?
 ** Has the RFC received attention or been controversial?

 * Status
 ** Can comments be submitted before the last call deadline?
 ** Would commentary on an RFC lead to a new I-D?
 ** Would commentary on an RFC be a useful case study in applying the
guidelines?

 * Simplicity
 ** Is the I-D or RFC self-contained enough, eg not too much reliance on
other RFCs to the point where our comments on the specific document at
hand are irrelevant?
 ** Is the I-D or RFC short and straight-forward, eg not overly
complicated or generally too time consuming?

 * Implementation
 ** Is the I-D or RFC likely to be implemented by providers up stream?
 ** Is the I-D or RFC widely supported, eg not generally considered by
the IETF community to be ignored?
 ** Is the RFC, or the RFC that is being revised by an I-D, widely
implemented already?

 * Relationships
 ** Has the I-D or RFC been drafted by individuals or entities engaged
in the research team or HRPC?
 ** Has the I-D or RFC been drafted by individuals or entities with whom
we could partner on, or who would be amenable to improvements?

I believe that we could apply this framework to the suggested analyses
as well as use it to identify potential analyses, both in the future and
retroactively.

-Mallory

--=20
Mallory Knodel
Head of Digital :: article19.org
gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9  B071 0C32 A271 BD3C C780


From nobody Wed May  2 02:20:31 2018
Return-Path: <mallory@article19.org>
X-Original-To: hr-rt@ietfa.amsl.com
Delivered-To: hr-rt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C21212D95D for <hr-rt@ietfa.amsl.com>; Wed,  2 May 2018 02:20:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 s69oh39MIym1 for <hr-rt@ietfa.amsl.com>; Wed,  2 May 2018 02:20:27 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (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 5D4C912D94B for <hr-rt@irtf.org>; Wed,  2 May 2018 02:20:27 -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 <mallory@article19.org>) id 1fDnw1-0007Ve-8N for hr-rt@irtf.org; Wed, 02 May 2018 11:20:25 +0200
To: hr-rt@irtf.org
References: <3bb12313-3e3a-0982-51de-7d12b533ed14@nielstenoever.net>
From: Mallory Knodel <mallory@article19.org>
Openpgp: preference=signencrypt
Autocrypt: addr=mallory@article19.org; prefer-encrypt=mutual; keydata= xsBNBEx0TWcBCAC8sirY3nlDnRwY6XWmsvZtM9kmEK6H8no3ZuQ723PKwHOddw1nOykh0in/ /QGRmwtyVzsfLh6/94UUZTn10oo+xGAfw2gf1on5IJTIiphykk732PNnUakVGWwHNKQquTVc kLrydUaFVMb89BAXqExBKlMg2ciEjzbYMCs3I/qZAZ0Wr5nF3RQS8O78elTNAgWTZ98yKTZV DlRoDpnvbfwtIPqnISoSjDEvEUBdpykvS3jHqlR1f6Mx6Xs97S5CORaer/0qTcDm0PAb1Z9l IhMsFl05tNt2FpgS4/RN8NyLasAQNOlScpTJbAfRuyyvRm1N8GLIL1KX+YYeLyqzhdhZABEB AAHNJU1hbGxvcnkgS25vZGVsIDxtYWxsb3J5QG1heWZpcnN0Lm9yZz7CwJgEEwECAEICGwMG CwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAhkBFiEE4+tj4GWjskC82bBxDDKicb08x4AFAlqo 9WUFCRAV234ACgkQDDKicb08x4DklAf+ODKRmP6C2MnBz6vL8N8l3vZJUqoRcYXTn3uTpT05 Wou87ZIZ/P/OV2/uOMKkczLQQydj5S8PxbLTeg+U5f/63hdy99ON+K2b4izg7Qasdl1SqXTH q1pmhbrcbLbVKDJ345fdEg7RuMnv4gd3EaT/yQa99zHy8JHaBKaPEUQAa65HTt2Sy2c6L6BA aMZx1TOZ9/cZ7L1gJyytJbEyvg/JLOatJEI4rewUWU2TMSGJijwjAUBagwDPWyxpz+vXdKsD tqRTpY4xvXaeUQo0QXf0c5j1Gcglzv7ywZcyz1MGD1aLS9/CqeB3I4EMbvH/33LS3jNkfKbV XOTSjmo7l22CNc7ATQRMdE1nAQgA4mpP2LjFuAW2li9FPbDYOMzt0MtThXsnvHyY0fDv8FlU qnKgPrMY80VHntnxwqepFS3ncunVX4ipq+fadta+LHpTnbJSmlphBrc9qGJxqcjwf4yo35Xh OXCJFwnaoAwIX237lXRe4Xh6X4VMuJt8jiZdvgpbk/whvQH2grcq8KjCcy1iuL5pBl8ZwYG/ dphitFhQdqEcnc/krIqG4KQgKiUi3K/GR0OeEmw/cscWD7/CLEo7eHiaGQhSOyDQbM+Iu2o/ 6uMXMUPsYlMMqgmVL68zMacO3PE17jx0rQ8oZ7CpBY8YZWOWrzXrtFT8JO9guuCPsvd4KT6y 97y9LRJlPQARAQABwsB8BBgBAgAmAhsMFiEE4+tj4GWjskC82bBxDDKicb08x4AFAlqo9WYF CRAV238ACgkQDDKicb08x4DU4QgAmlyBlFhfU0jpkbyD3HQ+3CJqWdBT422pVIrj3qNT2ehy fWO66Muidmd4Y279uV3p3TQEJOQvnV7FVAC9+bI7AdBy00BAjHgJ5eSQZxKTXUoeeBAsTZHN /HaHewjYWHMvCuuzir/Wt3A6Cehh8gp9I/Vg+oL3dTldVqqgZLgnA83bT/R8fI/e85LDlpdx KJ0+uy/grg3AbH7LUUrmMIC2iO8mQWYuNlizsUZLFvJhCAU2c5l8B5mv2BoWFhL+l7mmNcdF bwBFXon7Ea1jkCnbWVxtXkPYkcuWuMSTJswn9HhZVJWjUonKqUZKAb9PxRzC9crZ+X14tQT3 iJt2a4ZM4w==
Message-ID: <791c66cd-ac18-d8c7-abae-0bea5c553372@article19.org>
Date: Wed, 2 May 2018 12:20:22 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <3bb12313-3e3a-0982-51de-7d12b533ed14@nielstenoever.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: dfea3049d3b923820beb462d65569822
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/MMi97uwpkmBqqpss6jQjsFE0Y2w>
Subject: Re: [HT-rt] Design Team Process
X-BeenThere: hr-rt@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Human Rights Protocol Considerations Review Team <hr-rt.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hr-rt/>
List-Post: <mailto:hr-rt@irtf.org>
List-Help: <mailto:hr-rt-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 09:20:29 -0000

On 16/04/18 13:53, Niels ten Oever wrote:
> I hope all is well. There have been a few people that have shown
> interest in doing the guidelines on drafts, but we haven't really worked
> out the process afaik.
> 
> It would be great if we would have:
> - a list of drafts to analyze, maybe in a wiki or on a dedicated git

I think we need a space. Git seems like a good idea. We could create a
Gitlab project space at 0xacab or continue to push documents to your
GitHub project, Niels.

> - a process for assigning of volunteering for drafts for review? I am in
> favor of an assigning process, which doesn't mean someone cannot
> volunteer for smth.

I think assigning things is probably not going to work well. But, if we
can set up "beats", eg content areas that people are covering, then we
can know who to @ when we send suggestions to the list.

> - a process for sending a response (4 days review of draft response, on
> this list, then then the author can submit it with some template text
> such as: "Hello, I am the reviewer of the Human Rights Review Team, I
> have applied the guidelines as initially described in RFC8280 and
> further developed in draft-irtf-hrpc-guidelines to this document. Please
> find my review below, if you have any questions feel free to reach out
> to me at any time."

I like the idea of a template intro that brings visibility to the team.

-Mallory


-- 
Mallory Knodel
Head of Digital :: article19.org
gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9  B071 0C32 A271 BD3C C780


From nobody Wed May  2 10:12:20 2018
Return-Path: <shivankaul.1993@gmail.com>
X-Original-To: hr-rt@ietfa.amsl.com
Delivered-To: hr-rt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F088D124B17 for <hr-rt@ietfa.amsl.com>; Wed,  2 May 2018 10:12:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 nHZaSOza1LdQ for <hr-rt@ietfa.amsl.com>; Wed,  2 May 2018 10:12:13 -0700 (PDT)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (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 9875F126B7E for <hr-rt@irtf.org>; Wed,  2 May 2018 10:12:09 -0700 (PDT)
Received: by mail-lf0-x233.google.com with SMTP id b23-v6so21951782lfg.4 for <hr-rt@irtf.org>; Wed, 02 May 2018 10:12:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=TtF8/WrXYcXH3//tNlrx5j7gK2AGXTgY/XuIepungOY=; b=efOB2lO1s6NWG4UI4OybIzaUhzk1lEJDDSKSw+//W0hjGErNlE2Lxuia53SyiIO3nf XoJ9fghUqywWN3CbnGbyrbvp3x5WDJKFqorYRjJkbeLrwbud/YfpcSUXF9A6ZXW9fD6h kv1YvYMNMqqQ2piqZFia5yu/ltfptlWE0nZyI/vfgByZi/ioB/t0+8MythgBiar1WPJB mvOv/cktNIULX5xsm5sPkEXpJsCHXvU3dAKcS8qS4yswbGtAt40BryC4WXreihyc7/nK ILvDD6L05wPDPT6p3U/3DtLFmrObGyD2HR8fR2IVgGI+oEvUoTY2zlQU/p4WPnZS9dvw TrrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=TtF8/WrXYcXH3//tNlrx5j7gK2AGXTgY/XuIepungOY=; b=toVhaWHtsKEGtHtSCUIpQ1OfK0BhtwxkBUd4/g/cjJ25MQTK+/IaXvCWQvhStxmcoF 9JU76rXwduLtb2YTu9k+HclWBHevz/mDfEfSd1rW1iENSlyrLtDBpBzAhQUOoHQ/5kWb 0m1lqND3I3RcfzDE2cpQ2ZYdYFeOpbvyw2hsv1Zl1zvFHb+BDd7/9CXmuWqHmCufSpzx 7LcaAAMZ4YlESNRAsrQ7HPqlTMue9mjpzJx6YpJWNr1pa3AlUb6bgS7tWuJU0EAuueGS ++APNft8KM7p92e7eWNa9GzNoqCuPuCNPOoIxsi92rHPTC5wKJX2QIdxI4LL1i5zKzb0 f76g==
X-Gm-Message-State: ALQs6tCDwtf6z9b+VjRFnxg7wN1VICHYhFE+4taclKbUPXgi/HLcuBQr hcLaDhx3OzT3GalU4V5Btf+csH/ZsCL2tItfq0iFJw==
X-Google-Smtp-Source: AB8JxZq0aIB0AT1nJJ3iqQYcqWEh25DUMukr8cVWeTpfKxXIFhG3npcD5EOJY5sdeZB0Ddtfn9G2E2qxT9macUCC0cw=
X-Received: by 2002:a2e:9c44:: with SMTP id t4-v6mr1716414ljj.86.1525281127053;  Wed, 02 May 2018 10:12:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.144.3 with HTTP; Wed, 2 May 2018 10:11:26 -0700 (PDT)
From: Shivan <shivankaul.1993@gmail.com>
Date: Wed, 2 May 2018 13:11:26 -0400
Message-ID: <CAG3f7Mgd3yArxLsGdMS6-Ki2GqemtKhTLeHXrD8mqEMnV7CXLg@mail.gmail.com>
To: hr-rt@irtf.org, architecture-discuss@ietf.org, iab@iab.org
Content-Type: multipart/alternative; boundary="000000000000c2c064056b3c2f77"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/byJOPkEXzGlHcYISVEQfk_zkbug>
Subject: [HT-rt]  HR-RT Review of draft-iab-marnew-report-01
X-BeenThere: hr-rt@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Human Rights Protocol Considerations Review Team <hr-rt.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hr-rt/>
List-Post: <mailto:hr-rt@irtf.org>
List-Help: <mailto:hr-rt-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 17:12:17 -0000

--000000000000c2c064056b3c2f77
Content-Type: text/plain; charset="UTF-8"

This is a review done within the framework of the Human Rights Review
Team. It was done by Amelia Andersdotter and Shivan Kaul Sahib. The Human
Rights Review Team aims to implement and improve the guidelines for
human rights considerations provided in RFC8280, and seek to mitigate
potentially adverse human rights impacts that IETF and IRTF documents
might have.

We find the topics addressed during the workshop interesting and look
forward to following future developments.

---

Document: draft-iab-marnew-report-01
<https://datatracker.ietf.org/doc/draft-iab-marnew-report/>
https://datatracker.ietf.org/doc/draft-iab-marnew-report/

Review:

The Human Rights in Protocols Research Group welcomes the draft report from
the MaRNEW workshop. In particular, we welcome the efforts to continue
advancing an encrypted, secure and human rights enabling environment, as
well as solid assessments of the potential impacts of considered remedies
to mobile network operator difficulties on the right to privacy of an
individual.

In this regard, we wish to remind the drafters and the IAB of the inherent
connection between privacy and freedom of expression. The right to privacy,
or to one's own personhood, reinforces the freedom of expression and
freedom of opinion.

Semantic Suggestions
===========================

The following sections addresses a few semantic problems in the draft
report, that were they solved the draft report would be easier to parse
from both a human rights perspective, and from a business, legal or
technical perspective.

1. Abstract, para 2:

Problem: Draft text contains  value judgements on participants'
presentations that could be avoided.

Solution: Remove the word "honest" in relation to CDN presentations, since
it may cause readers to assume that other presenters were less forthcoming.

The new paragraph would read

   The group discussed the current Internet encryption trends and
   deployment issues identified within the IETF, and the privacy needs
   of users which should be adhered.  Solutions designed around sharing
   data from the network to the endpoints and vice versa were then
   discussed as well as analysing whether the current issues experienced
   on the transport layer are also playing a role here.  Content
   providers and CDNs gave their views of delivering
   content with mobile network operators.  Finally, technical responses
   to regulation was discussed to help the regulated industries relay
   the issues of impossible to implement or bad-for-privacy technologies
   back to regulators.

2. Section 1, Introduction:

Problem: It is unclear whether the "requirements" referred to imply
regulatory requirements enforceable by government authorities, or technical
requirements. Because of the nature of issues discussed during the
workshop, understanding what sorts of "requirements" are being referred to
is imperative.

Solution: Specify the nature of the requirements being referred to, or
remove the reference to requirements.

The new Introduction would read

   Mobile networks have a set of properties which
   places a large emphasis on sophisticated bandwidth optimization.
   Encryption is increasing on the Internet which is positive for
   consumer and business privacy and security.  Many existing mobile
   bandwidth optimization solutions primarily operate on non-encrypted
   communications; this can lead to performance issues being amplified
   on mobile networks.  Encryption on networks will continue to
   increase; and with this understanding the workshop aimed to
   understand how we can solve the issues of bandwidth optimization and
   performance on radio networks in this encrypted world.

3. Section 1.1:

Problem: The first paragraph mixes business models with technical
necessities. The last paragraph in the section Understanding "Bandwidth
Optimization" refers to regulatory requirements (within the meaning of
government enforced requirements or legal requirements, cf above) on mobile
network operators to perform traffic filtering and monitoring.

Solution: It may facilitate understanding of human rights impacts to
separate technical considerations from business considerations and legal
considerations. Paragraph 3 ("Many of these functions can continue...")
could be put as the last paragraph, while Paragraph 1 could be split into a
technical section and a business model section, followed by a legal section.


   For the purposes of this workshop, bandwidth optimization encompasses
   a variety of technical topics related to traffic engineering,
   prioritisation, optimisation and efficiency enhancements. It also
encompasses
   user-related topics such as specific subscription or billing models, and
may touch upon regulatory aspects or other issues relating to regulatory,
within the meaning of government initiated, concerns.

   The first category of bandwidth optimization includes:

   o  Caching

   o  Prioritisation of interactive traffic over background traffic

   o  Per-user bandwidth limit

   The second category of bandwidth optimization may depend on either of
the first category optimization strategies, but may, in particular, also
encompass:

   o  Business-related topics such as content delivery arrangements with
      specific content providers.

   Finally, while not strictly speaking traffic management, some
   networks employ policy-based filtering (e.g., requested parental
   controls) and many networks support some form of legal interception
   functionality per applicable laws.

   Many of these functions can continue as they're performed today, even
   with more encryption.  Others are using methods which inspect parts
   of the communication that are encrypted, and these will have to be
   done differently in an encrypted Internet.


4. Section 4:

Problem: QUIC is an active area of work for the IETF in the transport layer
- this section barely mentions it, and even then does so vaguely. What
problems are solved by QUIC that are general problems rather than TCP
problems? What was the nature of the disagreement around this?

Solution: More detail about how QUIC fits into transport-layer work would
make this section more relevant. In addition, there has been discussion
involving network operators around technical details that have potential
privacy impacts within the QUIC working group (SPIN bit); this section
would benefit greatly from an examination of that.



Human Rights Considerations
===========================

Upon consideration of the draft report, no implications for
internationalization ([RFC8280], sec. 6.2.5), heterogeneity support
([RFC8280], sec. 6.2.8), accessibility ([RFC8280], sec. 6.2.11) or
localization ([RFC8280], sec. 6.2.12) have been found. We will further
suppose that issues relating to Anonymity ([RFC8280], sec. 6.2.9),
Pseudonymity ([RFC8280], sec. 6.2.10) and Confidentiality ([RFC8280], sec.
6.2.16) have been sufficiently addressed in the draft as is.

In the below text, Security ([RFC8280], sec. 6.2.4), Integrity ([RFC8280],
sec. 6.2.16) and Authenticity ([RFC8280], sec. 6.2.17) are further
considered to have been addressed, or as in progress of being addressed by
the specific endeavours pointed out in the report. As such, this assessment
hopes to serve as a complement to remaining Human Rights Considerations
Guidelines which were not addressed by the MaRNEW draft.

## Privacy ([RFC8280], sec. 6.2.2)

We laud the general emphasis on considering user privacy concerns paramount
[Section 2.1.1, 2.3 etc].

In Section 3.1.1, para 1, it would be useful to emphasize that middleboxes
that are "authenticated and invoked explicitly" might not be very effective
at conserving user privacy if they lead to auto-click through. In practice,
"opted-in" middleboxes might not be much better than transparent
middleboxes. Additionally, this poses the danger of making matters worse if
users assume that because they haven't been asked for middlebox permission,
they are not going through a middlebox. For users accessing the Internet on
a browser client: if the connection is MITMed by a middlebox, the browser
would somehow need to convey this effectively and actionably to the user.
Whatever effort is expended on this should involve browser vendors.

## Connectivity ([RFC8280], sec. 6.2.1)

It is a priori obvious that a discussion with mobile network operators
would touch upon connectivity. As a general comment, the HRPC RG is not
concerned that encrypted internet traffic could create topological problems
in network deployment with respect to density of base stations. It is more
sensible to imagine that the density of base stations is kept low by
deployers to save money on infrastructure roll-out.

In the MarNEW draft report, middleboxes are brought up frequently as an
example of infrastructure rendered less useful by the ubiquitous adoption
of encryption. Middleboxes may enhance access to content for individuals,
and may also interfere with their ability to enjoy content free of
surveillance, censorship or content manipulation. The focus of the workshop
of exploring ways in which encrypted materials can benefit from the same
speed of deliverance as un-encrypted materials is therefore welcome.

## Content Agnosticism

Traffic prioritisation, whether based on technical or commercial grounds,
risks interfering with an individual's right to freedom of expression or
opinion, by restricting access or enjoy content of their own choosing. As
such, prioritisation should be made explicit and obvious, and subject to
consent from the individual, whether the motivations for deployment are
commercial or technical.

It is clear that internet filtering and blocking of content of specific
types, whether motivated by network management or regulatory concerns, does
not fulfill a content agnosticism criterion. It is the observation of HRPC
that [RFC7725] (An HTTP Status Code to Report Legal Obstacles) may assist
communication of specific filtering and blocking operations in action.

It the the impetus of the Human Rights Guidelines in RFC8280 that content
agnosticism be respected by protocols developed in the IETF, and in general
an accepted view in the global human rights community that content
agnosticism is desirable at all levels of technical infrastructure. As
such, the HRPC RG is concerned about ideas that traffic be classified
through additional headers or metadata, identifying traffic via 5-tuples,
trust models and frameworks, or heuristics.

--000000000000c2c064056b3c2f77
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default"><div class=3D"gmail_default">=
<span style=3D"color:rgb(51,51,51);font-family:georgia,serif">This is a rev=
iew done within the framework of the Human Rights Review</span><br></div><d=
iv class=3D"gmail_default"><div class=3D"gmail_default"><font color=3D"#333=
333" face=3D"georgia, serif">Team. It was done by Amelia Andersdotter and S=
hivan Kaul Sahib. The Human</font></div><div class=3D"gmail_default"><font =
color=3D"#333333" face=3D"georgia, serif">Rights Review Team aims to implem=
ent and improve the guidelines for</font></div><div class=3D"gmail_default"=
><font color=3D"#333333" face=3D"georgia, serif">human rights consideration=
s provided in RFC8280, and seek to mitigate</font></div><div class=3D"gmail=
_default"><font color=3D"#333333" face=3D"georgia, serif">potentially adver=
se human rights impacts that IETF and IRTF documents</font></div><div class=
=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif">might ha=
ve.</font></div><div class=3D"gmail_default"><font color=3D"#333333" face=
=3D"georgia, serif"><br></font></div><div class=3D"gmail_default"><font col=
or=3D"#333333" face=3D"georgia, serif">We find the topics addressed during =
the workshop interesting and look</font></div><div class=3D"gmail_default">=
<font color=3D"#333333" face=3D"georgia, serif">forward to following future=
 developments.</font></div><div class=3D"gmail_default"><font color=3D"#333=
333" face=3D"georgia, serif"><br></font></div><div class=3D"gmail_default">=
<font color=3D"#333333" face=3D"georgia, serif">---</font></div><div class=
=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif"><br></fo=
nt></div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georg=
ia, serif">Document: <a href=3D"https://datatracker.ietf.org/doc/draft-iab-=
marnew-report/">draft-iab-marnew-report-01</a></font></div><div class=3D"gm=
ail_default"><a href=3D"https://datatracker.ietf.org/doc/draft-iab-marnew-r=
eport/">https://datatracker.ietf.org/doc/draft-iab-marnew-report/</a><br></=
div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, s=
erif"><br></font></div><div class=3D"gmail_default"><font color=3D"#333333"=
 face=3D"georgia, serif">Review:</font></div><div class=3D"gmail_default"><=
font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div class=
=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif">The Huma=
n Rights in Protocols Research Group welcomes the draft report from the MaR=
NEW workshop. In particular, we welcome the efforts to continue advancing a=
n encrypted, secure and human rights enabling environment, as well as solid=
 assessments of the potential impacts of considered remedies to mobile netw=
ork operator difficulties on the right to privacy of an individual.</font><=
/div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, =
serif"><br></font></div><div class=3D"gmail_default"><font color=3D"#333333=
" face=3D"georgia, serif">In this regard, we wish to remind the drafters an=
d the IAB of the inherent connection between privacy and freedom of express=
ion. The right to privacy, or to one&#39;s own personhood, reinforces the f=
reedom of expression and freedom of opinion.</font></div><div class=3D"gmai=
l_default"><font color=3D"#333333" face=3D"georgia, serif"><br></font></div=
><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, seri=
f">Semantic Suggestions</font></div><div class=3D"gmail_default"><font colo=
r=3D"#333333" face=3D"georgia, serif">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</font></div><div class=3D"gma=
il_default"><font color=3D"#333333" face=3D"georgia, serif"><br></font></di=
v><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, ser=
if">The following sections addresses a few semantic problems in the draft r=
eport, that were they solved the draft report would be easier to parse from=
 both a human rights perspective, and from a business, legal or technical p=
erspective.</font></div><div class=3D"gmail_default"><font color=3D"#333333=
" face=3D"georgia, serif"><br></font></div><div class=3D"gmail_default"><fo=
nt color=3D"#333333" face=3D"georgia, serif">1. Abstract, para 2:</font></d=
iv><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, se=
rif"><br></font></div><div class=3D"gmail_default"><font color=3D"#333333" =
face=3D"georgia, serif">Problem: Draft text contains=C2=A0 value judgements=
 on participants&#39; presentations that could be avoided.</font></div><div=
 class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif"><b=
r></font></div><div class=3D"gmail_default"><font color=3D"#333333" face=3D=
"georgia, serif">Solution: Remove the word &quot;honest&quot; in relation t=
o CDN presentations, since it may cause readers to assume that other presen=
ters were less forthcoming.</font></div><div class=3D"gmail_default"><font =
color=3D"#333333" face=3D"georgia, serif"><br></font></div><div class=3D"gm=
ail_default"><font color=3D"#333333" face=3D"georgia, serif">The new paragr=
aph would read</font></div><div class=3D"gmail_default"><font color=3D"#333=
333" face=3D"georgia, serif"><br></font></div><div class=3D"gmail_default">=
<font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0The group disc=
ussed the current Internet encryption trends and</font></div><div class=3D"=
gmail_default"><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=
=A0deployment issues identified within the IETF, and the privacy needs</fon=
t></div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgi=
a, serif">=C2=A0 =C2=A0of users which should be adhered.=C2=A0 Solutions de=
signed around sharing</font></div><div class=3D"gmail_default"><font color=
=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0data from the network to =
the endpoints and vice versa were then</font></div><div class=3D"gmail_defa=
ult"><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0discussed=
 as well as analysing whether the current issues experienced</font></div><d=
iv class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif">=
=C2=A0 =C2=A0on the transport layer are also playing a role here.=C2=A0 Con=
tent</font></div><div class=3D"gmail_default"><font color=3D"#333333" face=
=3D"georgia, serif">=C2=A0 =C2=A0providers and CDNs gave their views of del=
ivering</font></div><div class=3D"gmail_default"><font color=3D"#333333" fa=
ce=3D"georgia, serif">=C2=A0 =C2=A0content with mobile network operators.=
=C2=A0 Finally, technical responses</font></div><div class=3D"gmail_default=
"><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0to regulatio=
n was discussed to help the regulated industries relay</font></div><div cla=
ss=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif">=C2=A0=
 =C2=A0the issues of impossible to implement or bad-for-privacy technologie=
s</font></div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"=
georgia, serif">=C2=A0 =C2=A0back to regulators.</font></div><div class=3D"=
gmail_default"><font color=3D"#333333" face=3D"georgia, serif"><br></font><=
/div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, =
serif">2. Section 1, Introduction:</font></div><div class=3D"gmail_default"=
><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div clas=
s=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif">Problem=
: It is unclear whether the &quot;requirements&quot; referred to imply regu=
latory requirements enforceable by government authorities, or technical req=
uirements. Because of the nature of issues discussed during the workshop, u=
nderstanding what sorts of &quot;requirements&quot; are being referred to i=
s imperative.</font></div><div class=3D"gmail_default"><font color=3D"#3333=
33" face=3D"georgia, serif"><br></font></div><div class=3D"gmail_default"><=
font color=3D"#333333" face=3D"georgia, serif">Solution: Specify the nature=
 of the requirements being referred to, or remove the reference to requirem=
ents.</font></div><div class=3D"gmail_default"><font color=3D"#333333" face=
=3D"georgia, serif"><br></font></div><div class=3D"gmail_default"><font col=
or=3D"#333333" face=3D"georgia, serif">The new Introduction would read</fon=
t></div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgi=
a, serif"><br></font></div><div class=3D"gmail_default"><font color=3D"#333=
333" face=3D"georgia, serif">=C2=A0 =C2=A0Mobile networks have a set of pro=
perties which</font></div><div class=3D"gmail_default"><font color=3D"#3333=
33" face=3D"georgia, serif">=C2=A0 =C2=A0places a large emphasis on sophist=
icated bandwidth optimization.</font></div><div class=3D"gmail_default"><fo=
nt color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0Encryption is inc=
reasing on the Internet which is positive for</font></div><div class=3D"gma=
il_default"><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0co=
nsumer and business privacy and security.=C2=A0 Many existing mobile</font>=
</div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia,=
 serif">=C2=A0 =C2=A0bandwidth optimization solutions primarily operate on =
non-encrypted</font></div><div class=3D"gmail_default"><font color=3D"#3333=
33" face=3D"georgia, serif">=C2=A0 =C2=A0communications; this can lead to p=
erformance issues being amplified</font></div><div class=3D"gmail_default">=
<font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0on mobile netw=
orks.=C2=A0 Encryption on networks will continue to</font></div><div class=
=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =
=C2=A0increase; and with this understanding the workshop aimed to</font></d=
iv><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, se=
rif">=C2=A0 =C2=A0understand how we can solve the issues of bandwidth optim=
ization and</font></div><div class=3D"gmail_default"><font color=3D"#333333=
" face=3D"georgia, serif">=C2=A0 =C2=A0performance on radio networks in thi=
s encrypted world.</font></div><div class=3D"gmail_default"><font color=3D"=
#333333" face=3D"georgia, serif"><br></font></div><div class=3D"gmail_defau=
lt"><font color=3D"#333333" face=3D"georgia, serif">3. Section 1.1:</font><=
/div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, =
serif"><br></font></div><div class=3D"gmail_default"><font color=3D"#333333=
" face=3D"georgia, serif">Problem: The first paragraph mixes business model=
s with technical necessities. The last paragraph in the section Understandi=
ng &quot;Bandwidth Optimization&quot; refers to regulatory requirements (wi=
thin the meaning of government enforced requirements or legal requirements,=
 cf above) on mobile network operators to perform traffic filtering and mon=
itoring.</font></div><div class=3D"gmail_default"><font color=3D"#333333" f=
ace=3D"georgia, serif"><br></font></div><div class=3D"gmail_default"><font =
color=3D"#333333" face=3D"georgia, serif">Solution: It may facilitate under=
standing of human rights impacts to separate technical considerations from =
business considerations and legal considerations. Paragraph 3 (&quot;Many o=
f these functions can continue...&quot;) could be put as the last paragraph=
, while Paragraph 1 could be split into a technical section and a business =
model section, followed by a legal section.</font></div><div class=3D"gmail=
_default"><font color=3D"#333333" face=3D"georgia, serif"><br></font></div>=
<div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif=
"><br></font></div><div class=3D"gmail_default"><font color=3D"#333333" fac=
e=3D"georgia, serif">=C2=A0 =C2=A0For the purposes of this workshop, bandwi=
dth optimization encompasses</font></div><div class=3D"gmail_default"><font=
 color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0a variety of techni=
cal topics related to traffic engineering,</font></div><div class=3D"gmail_=
default"><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0prior=
itisation, optimisation and efficiency enhancements. It also encompasses</f=
ont></div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"geor=
gia, serif">=C2=A0 =C2=A0user-related topics such as specific subscription =
or billing models, and may touch upon regulatory aspects or other issues re=
lating to regulatory, within the meaning of government initiated, concerns.=
</font></div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"g=
eorgia, serif"><br></font></div><div class=3D"gmail_default"><font color=3D=
"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0The first category of bandwi=
dth optimization includes:</font></div><div class=3D"gmail_default"><font c=
olor=3D"#333333" face=3D"georgia, serif"><br></font></div><div class=3D"gma=
il_default"><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0o=
=C2=A0 Caching</font></div><div class=3D"gmail_default"><font color=3D"#333=
333" face=3D"georgia, serif"><br></font></div><div class=3D"gmail_default">=
<font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0o=C2=A0 Priori=
tisation of interactive traffic over background traffic</font></div><div cl=
ass=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif"><br><=
/font></div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"ge=
orgia, serif">=C2=A0 =C2=A0o=C2=A0 Per-user bandwidth limit</font></div><di=
v class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif">=
=C2=A0 =C2=A0</font></div><div class=3D"gmail_default"><font color=3D"#3333=
33" face=3D"georgia, serif">=C2=A0 =C2=A0The second category of bandwidth o=
ptimization may depend on either of the first category optimization strateg=
ies, but may, in particular, also encompass:</font></div><div class=3D"gmai=
l_default"><font color=3D"#333333" face=3D"georgia, serif"><br></font></div=
><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, seri=
f">=C2=A0 =C2=A0o=C2=A0 Business-related topics such as content delivery ar=
rangements with</font></div><div class=3D"gmail_default"><font color=3D"#33=
3333" face=3D"georgia, serif">=C2=A0 =C2=A0 =C2=A0 specific content provide=
rs.</font></div><div class=3D"gmail_default"><font color=3D"#333333" face=
=3D"georgia, serif">=C2=A0 =C2=A0 =C2=A0=C2=A0</font></div><div class=3D"gm=
ail_default"><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0F=
inally, while not strictly speaking traffic management, some</font></div><d=
iv class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif">=
=C2=A0 =C2=A0networks employ policy-based filtering (e.g., requested parent=
al</font></div><div class=3D"gmail_default"><font color=3D"#333333" face=3D=
"georgia, serif">=C2=A0 =C2=A0controls) and many networks support some form=
 of legal interception</font></div><div class=3D"gmail_default"><font color=
=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0functionality per applica=
ble laws.</font></div><div class=3D"gmail_default"><font color=3D"#333333" =
face=3D"georgia, serif"><br></font></div><div class=3D"gmail_default"><font=
 color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0Many of these funct=
ions can continue as they&#39;re performed today, even</font></div><div cla=
ss=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif">=C2=A0=
 =C2=A0with more encryption.=C2=A0 Others are using methods which inspect p=
arts</font></div><div class=3D"gmail_default"><font color=3D"#333333" face=
=3D"georgia, serif">=C2=A0 =C2=A0of the communication that are encrypted, a=
nd these will have to be</font></div><div class=3D"gmail_default"><font col=
or=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0done differently in an =
encrypted Internet.</font></div><div class=3D"gmail_default"><font color=3D=
"#333333" face=3D"georgia, serif"><br></font></div><div class=3D"gmail_defa=
ult"><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div =
class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif">4. =
Section 4:</font></div><div class=3D"gmail_default"><font color=3D"#333333"=
 face=3D"georgia, serif"><br></font></div><div class=3D"gmail_default"><fon=
t color=3D"#333333" face=3D"georgia, serif">Problem: QUIC is an active area=
 of work for the IETF in the transport layer - this section barely mentions=
 it, and even then does so vaguely. What problems are solved by QUIC that a=
re general problems rather than TCP problems? What was the nature of the di=
sagreement around this?</font></div><div class=3D"gmail_default"><font colo=
r=3D"#333333" face=3D"georgia, serif"><br></font></div><div class=3D"gmail_=
default"><font color=3D"#333333" face=3D"georgia, serif">Solution: More det=
ail about how QUIC fits into transport-layer work would make this section m=
ore relevant. In addition, there has been discussion involving network oper=
ators around technical details that have potential privacy impacts within t=
he QUIC working group (SPIN bit); this section would benefit greatly from a=
n examination of that.</font></div><div class=3D"gmail_default"><font color=
=3D"#333333" face=3D"georgia, serif"><br></font></div><div class=3D"gmail_d=
efault"><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><d=
iv class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif">=
<br></font></div><div class=3D"gmail_default"><font color=3D"#333333" face=
=3D"georgia, serif">Human Rights Considerations</font></div><div class=3D"g=
mail_default"><font color=3D"#333333" face=3D"georgia, serif">=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</font=
></div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia=
, serif"><br></font></div><div class=3D"gmail_default"><font color=3D"#3333=
33" face=3D"georgia, serif">Upon consideration of the draft report, no impl=
ications for internationalization ([RFC8280], sec. 6.2.5), heterogeneity su=
pport ([RFC8280], sec. 6.2.8), accessibility ([RFC8280], sec. 6.2.11) or lo=
calization ([RFC8280], sec. 6.2.12) have been found. We will further suppos=
e that issues relating to Anonymity ([RFC8280], sec. 6.2.9), Pseudonymity (=
[RFC8280], sec. 6.2.10) and Confidentiality ([RFC8280], sec. 6.2.16) have b=
een sufficiently addressed in the draft as is.</font></div><div class=3D"gm=
ail_default"><font color=3D"#333333" face=3D"georgia, serif"><br></font></d=
iv><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, se=
rif">In the below text, Security ([RFC8280], sec. 6.2.4), Integrity ([RFC82=
80], sec. 6.2.16) and Authenticity ([RFC8280], sec. 6.2.17) are further con=
sidered to have been addressed, or as in progress of being addressed by the=
 specific endeavours pointed out in the report. As such, this assessment ho=
pes to serve as a complement to remaining Human Rights Considerations Guide=
lines which were not addressed by the MaRNEW draft.</font></div><div class=
=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif"><br></fo=
nt></div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georg=
ia, serif">## Privacy ([RFC8280], sec. 6.2.2)</font></div><div class=3D"gma=
il_default"><font color=3D"#333333" face=3D"georgia, serif"><br></font></di=
v><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, ser=
if">We laud the general emphasis on considering user privacy concerns param=
ount [Section 2.1.1, 2.3 etc].=C2=A0</font></div><div class=3D"gmail_defaul=
t"><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div cl=
ass=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif">In Se=
ction 3.1.1, para 1, it would be useful to emphasize that middleboxes that =
are &quot;authenticated and invoked explicitly&quot; might not be very effe=
ctive at conserving user privacy if they lead to auto-click through. In pra=
ctice, &quot;opted-in&quot; middleboxes might not be much better than trans=
parent middleboxes. Additionally, this poses the danger of making matters w=
orse if users assume that because they haven&#39;t been asked for middlebox=
 permission, they are not going through a middlebox. For users accessing th=
e Internet on a browser client: if the connection is MITMed by a middlebox,=
 the browser would somehow need to convey this effectively and actionably t=
o the user. Whatever effort is expended on this should involve browser vend=
ors.</font></div><div class=3D"gmail_default"><font color=3D"#333333" face=
=3D"georgia, serif"><br></font></div><div class=3D"gmail_default"><font col=
or=3D"#333333" face=3D"georgia, serif">## Connectivity ([RFC8280], sec. 6.2=
.1)</font></div><div class=3D"gmail_default"><font color=3D"#333333" face=
=3D"georgia, serif"><br></font></div><div class=3D"gmail_default"><font col=
or=3D"#333333" face=3D"georgia, serif">It is a priori obvious that a discus=
sion with mobile network operators would touch upon connectivity. As a gene=
ral comment, the HRPC RG is not concerned that encrypted internet traffic c=
ould create topological problems in network deployment with respect to dens=
ity of base stations. It is more sensible to imagine that the density of ba=
se stations is kept low by deployers to save money on infrastructure roll-o=
ut.</font></div><div class=3D"gmail_default"><font color=3D"#333333" face=
=3D"georgia, serif"><br></font></div><div class=3D"gmail_default"><font col=
or=3D"#333333" face=3D"georgia, serif">In the MarNEW draft report, middlebo=
xes are brought up frequently as an example of infrastructure rendered less=
 useful by the ubiquitous adoption of encryption. Middleboxes may enhance a=
ccess to content for individuals, and may also interfere with their ability=
 to enjoy content free of surveillance, censorship or content manipulation.=
 The focus of the workshop of exploring ways in which encrypted materials c=
an benefit from the same speed of deliverance as un-encrypted materials is =
therefore welcome.</font></div><div class=3D"gmail_default"><font color=3D"=
#333333" face=3D"georgia, serif"><br></font></div><div class=3D"gmail_defau=
lt"><font color=3D"#333333" face=3D"georgia, serif">## Content Agnosticism<=
/font></div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"ge=
orgia, serif"><br></font></div><div class=3D"gmail_default"><font color=3D"=
#333333" face=3D"georgia, serif">Traffic prioritisation, whether based on t=
echnical or commercial grounds, risks interfering with an individual&#39;s =
right to freedom of expression or opinion, by restricting access or enjoy c=
ontent of their own choosing. As such, prioritisation should be made explic=
it and obvious, and subject to consent from the individual, whether the mot=
ivations for deployment are commercial or technical.</font></div><div class=
=3D"gmail_default"><font color=3D"#333333" face=3D"georgia, serif"><br></fo=
nt></div><div class=3D"gmail_default"><font color=3D"#333333" face=3D"georg=
ia, serif">It is clear that internet filtering and blocking of content of s=
pecific types, whether motivated by network management or regulatory concer=
ns, does not fulfill a content agnosticism criterion. It is the observation=
 of HRPC that [RFC7725] (An HTTP Status Code to Report Legal Obstacles) may=
 assist communication of specific filtering and blocking operations in acti=
on.</font></div><div class=3D"gmail_default"><font color=3D"#333333" face=
=3D"georgia, serif"><br></font></div><div class=3D"gmail_default"><font col=
or=3D"#333333" face=3D"georgia, serif">It the the impetus of the Human Righ=
ts Guidelines in RFC8280 that content agnosticism be respected by protocols=
 developed in the IETF, and in general an accepted view in the global human=
 rights community that content agnosticism is desirable at all levels of te=
chnical infrastructure. As such, the HRPC RG is concerned about ideas that =
traffic be classified through additional headers or metadata, identifying t=
raffic via 5-tuples, trust models and frameworks, or heuristics.</font></di=
v><div><br></div></div><div style=3D"color:rgb(51,51,51);font-family:georgi=
a,serif;font-size:small"><br></div></div></div>

--000000000000c2c064056b3c2f77--


From nobody Wed May  2 10:17:28 2018
Return-Path: <shivankaul.1993@gmail.com>
X-Original-To: hr-rt@ietfa.amsl.com
Delivered-To: hr-rt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EAE9124B17 for <hr-rt@ietfa.amsl.com>; Wed,  2 May 2018 10:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 3_0FuYiNMURV for <hr-rt@ietfa.amsl.com>; Wed,  2 May 2018 10:17:23 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 580DE1200C1 for <hr-rt@irtf.org>; Wed,  2 May 2018 10:17:22 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id j193-v6so21971976lfg.6 for <hr-rt@irtf.org>; Wed, 02 May 2018 10:17:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cq/WuW0ZSlh9AdjFQOz9IbDjhyuVYfkLAYdVaM7EITs=; b=Q0Ms0d3WZRUA/e43/vJmqZOzqt51NsitBcaZIFwvJRsqcjD1dgF52xH4DeoLVOiSSM ZH5ZPbLlpjuDJO/y/qmeh5Kk5Qowz5M/xW7A/4rPlPen4orVDzS3bH5a67W841BnY6LL wTQuuekLwjaY0n4NByOcJRHWyPGQEgT2TNyEQFNSy9xNfGg2ZUrt9gr5lQJMwUfpj/JN Vs5uDeXYKUNOq67LlusIWgy1SHzYi4wB+n5J7RiquyhZ0TXfY+3j9puRRjpquu3sqWak 8qT/1sH/cQFDkKJS+QSMLSgVpoXYtZO4ZP8osjJ3o55+NaFmfUrz0MdsUxTbZvtgpvkt Uryw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=cq/WuW0ZSlh9AdjFQOz9IbDjhyuVYfkLAYdVaM7EITs=; b=QVVUnpNcM3sg6u+ERBfOx/bLSRWa0/8oM6ttvD70QLnd/33NNF6UibykzTz3xvAqA0 tzrRQpcMAGkZP+UCbwlBKau2rzrvnLhaiN8C8MymiQT8BReyq8GbPCLkcwu7c0VqKGQU KtEA1mWHiYRAcACw5NnHSPvfZC+tgBHmmAcY95LItxS0665uoMH/dWMrQXXfvr3pI7+G TaFO4l+k0UUw8fGz3Anfklx8NZSNN1WeV4iOETxEpUUraBx37jxoefb6i7b28SUtJyUF 2o2xxVvdz6XOAjlwtY918IfWDgZ3Pjois5rvv/TAdNj6VXWGowSAAcTUziftuN0+DzmV xrGQ==
X-Gm-Message-State: ALQs6tAd3+y5drI4d3y4sQtn2YMgYogDyG9Nc9eR7a4wFd9g4QqXiWOd JYRo3RWIw/KTZmlS1c3ktZRVbwgXsw/gzd3w1JPajQ==
X-Google-Smtp-Source: AB8JxZr19ioyeWI7vtp1WOs15bOYSJKBn+jhlkke2WORklvfmvq9jZr7f2mWvmRo5eL5Fu1v90f3/3s3fc5LU6BmeDU=
X-Received: by 2002:a2e:96d2:: with SMTP id d18-v6mr13743141ljj.21.1525281440489;  Wed, 02 May 2018 10:17:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.144.3 with HTTP; Wed, 2 May 2018 10:16:39 -0700 (PDT)
In-Reply-To: <053a8b99-94b6-6e34-eaad-09769200d574@nielstenoever.net>
References: <20180407153608.7v4zzra6qy3w3gfz@nic.fr> <CAG3f7Mg0zNbEJKEB5H38swyd3A6qAB5ogTaQ_2BLMP6j=xL2zQ@mail.gmail.com> <0adcac93-cf66-414b-85c2-119eea9f42e3@nielstenoever.net> <2aadec40-1583-e15b-6f66-f15e626382e4@article19.org> <f2647c8e-bb44-07fe-3575-4b4216db32b4@nielstenoever.net> <b5856287-8949-4d1b-73b9-3ef63967a73e@article19.org> <3215126c-a7b4-4399-31b9-c0f867188d61@nielstenoever.net> <053a8b99-94b6-6e34-eaad-09769200d574@nielstenoever.net>
From: Shivan <shivankaul.1993@gmail.com>
Date: Wed, 2 May 2018 13:16:39 -0400
Message-ID: <CAG3f7MideYnZ2mfmxC_DD87x7_8OKTM1ZD4w=z64qpZzoXBdoQ@mail.gmail.com>
To: Niels ten Oever <mail@nielstenoever.net>
Cc: Amelia Andersdotter <amelia@article19.org>, Stephane Bortzmeyer <bortzmeyer@nic.fr>, hr-rt@irtf.org,  Gordon Lennox <gordon@lennox.paris>
Content-Type: multipart/alternative; boundary="00000000000071652d056b3c4249"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/xeBhxAWYoKzEvteSyQJ8j8QB4n4>
Subject: Re: [HT-rt] [execd@iab.org: Call for Comment: <draft-iab-marnew-report-01> (IAB Workshop on Managing Radio Networks in an Encrypted World (MaRNEW) Report)]
X-BeenThere: hr-rt@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Human Rights Protocol Considerations Review Team <hr-rt.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hr-rt/>
List-Post: <mailto:hr-rt@irtf.org>
List-Help: <mailto:hr-rt-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 17:17:26 -0000

--00000000000071652d056b3c4249
Content-Type: text/plain; charset="UTF-8"

Hey Niels, thanks for keeping track of this. Maybe we can have a pad where
we keep track of deadlines.

I consulted with Amelia and sent a review out. I loosely used the format
used in draft-ietf-mtgvenue-iaoc-venue-selection-process

On Wed, May 2, 2018 at 3:59 AM, Niels ten Oever <mail@nielstenoever.net>
wrote:

> Hi Shivan and Amelia,
>
> Has this been submitted?
>
> The official deadline was yesterday, but it might still be accepted if
> it is submitted today.
>
> Best,
>
> Niels
>
> On 04/11/2018 11:07 AM, Niels ten Oever wrote:
> > Hi Amelia,
> >
> > We don't need a specific format, we can simply send an email with the
> > review.
> >
> > Cheers,
> >
> > Niels
> >
> > On 04/09/2018 07:23 PM, Amelia Andersdotter wrote:
> >> How easiest to draft?
> >>
> >> i started something here:
> >> https://github.com/nllz/IRTF-HRPC/pull/221/files#diff-
> 989e50ba297c8bab8fe8fbd3759ac6d2
> >>
> >>
> >> there's some semantics in this (first), and then i started the
> >> evaluation by removing those considerations that i thought were either
> >> already addressed, or that would best be addressed elsewhere.
> >>
> >> i find it ironic that the telcos don't want to share their APIs /with
> >> their own customers and users(!)/ out of competition concerns. normally,
> >> i'm the customer of by telco, i don't compete with it.
> >>
> >> but a big problem in the mobile markets could then be that vertically
> >> integrated operators can be both mobile OS or mobile app providers /and/
> >> Mobile Network Operators at the same time. Oh, if only the telcos had
> >> lobbied for a competetitve market regulation(!) how many of their
> >> current predicaments (and also end-user human rights concerns) could be
> >> solved. but ok.
> >>
> >> /end whiny transmission
> >>
> >> amelia
> >>
> >>
> >> On 2018-04-09 13:42, Niels ten Oever wrote:
> >>> Hi Amelia,
> >>>
> >>>
> >>> On 04/08/2018 10:19 PM, Amelia Andersdotter wrote:
> >>>> I guess the task is to apply the Human Rights Guidelines from RFC
> 8280?
> >>>>
> >>> Rather the guidelines doc:
> >>> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-00
> >>>
> >>> And feedback any potentially useful changes.
> >>>
> >>>
> >>>> It's a workshop. As I read the draft report GSMA is defending their
> >>>> regulatory and commercial interests, and IETF is saying "well, make it
> >>>> work while stuff is encrypted".
> >>>>
> >>>> So do we mean to criticize GSMA's self-perceived political/commercial
> >>>> interests from a HR perspective?
> >>>>
> >>> We seek to understand the potential impact for the ability of end-users
> >>> to excercise their human rights, a consequence for that could be to
> >>> criticize the proposed architectural reordering.
> >>>
> >>>> ====
> >>>>
> >>>> The workshop appears not to have touch on the upcoming ePrivacy
> >>>> regulation in the EU at all, in spite of it having a fairly big impact
> >>>> on many GSMA members. In particular, GSMA has been lobbying /against/
> >>>> the ePrivacy regulation, in spite of the IETF helpfully solving many
> of
> >>>> their regulatory challenges under the law.
> >>> Interesting - this could fall under the privacy part.
> >>>
> >>>> Telcos are in the place where they want to sell amounts of data. HTTPS
> >>>> increases the amount of data, making telco consumer potentially
> >>> decreases, right?
> >>>
> >>>> unhappier. Encryption can also slow stuff down, and while some vendors
> >>>> say that that's an issue of the past, it's possible that it isn't in
> for
> >>>> instance the developing world. Probably Facebook Free Basic
> connections
> >>>> have data on this.
> >>>>
> >>>> In some countries, notably the UK, telcos may be under obligation to
> >>>> generally filter connections (ensure they're porn-free). I find that
> >>>> policy disagreeable, but nevertheless it's there. For telcos it's a
> >>>> challenge.
> >>>>
> >>> This has an impact on FoE. I don't think we need to have an opinion on
> >>> everything from the get-go, but rather show the (potential)
> implications.
> >>>
> >>>> In Sweden, before the EU open internet regulation entered into effect,
> >>>> several telcos were investigated for traffic prioritisation (which was
> >>>> suspected to run contrary to ePrivacy directive obligations not to
> >>>> monitor traffic). Ironically, the EU open internet law kind of
> permitted
> >>>> commercially motivated traffic discrimination so those inquiries have
> >>>> since been cancelled. The new ANACOM case in Portugal may change this
> >>>> interpretation of what the open internet regulation says, but I don't
> >>>> perceive Portugal to be heading in that direction.
> >>>>
> >>> Cheers,
> >>>
> >>> Niels
> >>>
> >>>> best regards,
> >>>>
> >>>> Amelia
> >>>>
> >>>> On 2018-04-08 12:30, Niels ten Oever wrote:
> >>>>> Amelia know more about radio networks than I do methinks, but happy
> to
> >>>>> do so if Amelia is not available.
> >>>>>
> >>>>> Cheers,
> >>>>>
> >>>>> Niels
> >>>>>
> >>>>> Sent from Blue <http://www.bluemail.me/r?b=12687>
> >>>>> On Apr 7, 2018, at 22:43, Shivan <shivankaul.1993@gmail.com
> >>>>> <mailto:shivankaul.1993@gmail.com>> wrote:
> >>>>>
> >>>>>     I could take a look, if someone could work with me.
> >>>>>
> >>>>>     On Sat, Apr 7, 2018, 11:36 AM Stephane Bortzmeyer
> >>>>>     <bortzmeyer@nic.fr <mailto:bortzmeyer@nic.fr>> wrote:
> >>>>>
> >>>>>         Obvious HR consequences. Any volunteer?
> >>>>>
> >>>>>
> >>>>>
> >>>>>         ---------- Forwarded message ----------
> >>>>>         From: IAB Executive Administrative Manager <execd@iab.org
> >>>>>         <mailto:execd@iab.org>>
> >>>>>         To: IETF Announcement List <ietf-announce@ietf.org
> >>>>>         <mailto:ietf-announce@ietf.org>>
> >>>>>         Cc:
> >>>>>         Bcc:
> >>>>>         Date: Tue, 03 Apr 2018 15:08:39 -0700
> >>>>>         Subject: Call for Comment: <draft-iab-marnew-report-01> (IAB
> >>>>>         Workshop on Managing Radio Networks in an Encrypted World
> >>>>>         (MaRNEW) Report)
> >>>>>         This is an announcement of an IETF-wide Call for Comment on
> >>>>>         draft-iab-marnew-report-01.
> >>>>>
> >>>>>         The document is being considered for publication as an
> >>>>>         Informational RFC
> >>>>>         within the IAB stream, and is available for inspection at:
> >>>>>         https://datatracker.ietf.org/doc/draft-iab-marnew-report/
> >>>>>
> >>>>>         The Call for Comment will last until 2018-05-01. Please send
> >>>>>         comments to
> >>>>>         architecture-discuss@ietf.org
> >>>>>         <mailto:architecture-discuss@ietf.org> and iab@iab.org
> >>>>>         <mailto:iab@iab.org>.
> >>>>>
> >>>>>
> >>>>>         Abstract
> >>>>>
> >>>>>            The MarNEW workshop aimed to discuss solutions for
> bandwidth
> >>>>>            optimisation on mobile networks for encrypted content, as
> >>>>>         current
> >>>>>            solutions rely on unencrypted content which is not
> >>>>>         indicative of the
> >>>>>            security needs of today's Internet users.  The workshop
> >>>>>         gathered IETF
> >>>>>            attendees, IAB members and various organisations involved
> >>>>>         in the
> >>>>>            telecommunications industry including original equipment
> >>>>>            manufacturers and mobile network operators.
> >>>>>
> >>>>>            The group discussed the current Internet encryption
> trends and
> >>>>>            deployment issues identified within the IETF, and the
> >>>>>         privacy needs
> >>>>>            of users which should be adhered.  Solutions designed
> >>>>>         around sharing
> >>>>>            data from the network to the endpoints and vice versa
> were then
> >>>>>            discussed as well as analysing whether the current issues
> >>>>>         experienced
> >>>>>            on the transport layer are also playing a role here.
> Content
> >>>>>            providers and CDNs gave an honest view of their
> experiences
> >>>>>         delivery
> >>>>>            content with mobile network operators.  Finally, technical
> >>>>>         responses
> >>>>>            to regulation was discussed to help the regulated
> >>>>>         industries relay
> >>>>>            the issues of impossible to implement or bad-for-privacy
> >>>>>         technologies
> >>>>>            back to regulators.
> >>>>>
> >>>>>            A group of suggested solutions were devised which will be
> >>>>>         discussed
> >>>>>            in various IETF groups moving forward.
> >>>>>         _______________________________________________
> >>>>>         HR-rt mailing list
> >>>>>         HR-rt@irtf.org <mailto:HR-rt@irtf.org>
> >>>>>         https://www.irtf.org/mailman/listinfo/hr-rt
> >>>>>
> >>>>>     ------------------------------------------------------------
> ------------
> >>>>>
> >>>>>     HR-rt mailing list
> >>>>>     HR-rt@irtf.org
> >>>>>     https://www.irtf.org/mailman/listinfo/hr-rt
> >>>>>
> >>
> >
>
>

--00000000000071652d056b3c4249
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:georgia,=
serif;font-size:small;color:rgb(51,51,51)">Hey Niels, thanks for keeping tr=
ack of this. Maybe we can have a pad where we keep track of deadlines.=C2=
=A0</div><div class=3D"gmail_default" style=3D"font-family:georgia,serif;fo=
nt-size:small;color:rgb(51,51,51)"><br></div><div class=3D"gmail_default" s=
tyle=3D"font-family:georgia,serif;font-size:small;color:rgb(51,51,51)">I co=
nsulted with Amelia and sent a review out. I loosely used the format used i=
n=C2=A0draft-ietf-mtgvenue-iaoc-venue-selection-process</div></div><div cla=
ss=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, May 2, 2018 at 3:=
59 AM, Niels ten Oever <span dir=3D"ltr">&lt;<a href=3D"mailto:mail@nielste=
noever.net" target=3D"_blank">mail@nielstenoever.net</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">Hi Shivan and Amelia,<br>
<br>
Has this been submitted?<br>
<br>
The official deadline was yesterday, but it might still be accepted if<br>
it is submitted today.<br>
<br>
Best,<br>
<br>
Niels<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On 04/11/2018 11:07 AM, Niels ten Oever wrote:<br>
&gt; Hi Amelia,<br>
&gt; <br>
&gt; We don&#39;t need a specific format, we can simply send an email with =
the<br>
&gt; review.<br>
&gt; <br>
&gt; Cheers,<br>
&gt; <br>
&gt; Niels<br>
&gt; <br>
&gt; On 04/09/2018 07:23 PM, Amelia Andersdotter wrote:<br>
&gt;&gt; How easiest to draft?<br>
&gt;&gt;<br>
&gt;&gt; i started something here:<br>
&gt;&gt; <a href=3D"https://github.com/nllz/IRTF-HRPC/pull/221/files#diff-9=
89e50ba297c8bab8fe8fbd3759ac6d2" rel=3D"noreferrer" target=3D"_blank">https=
://github.com/nllz/IRTF-<wbr>HRPC/pull/221/files#diff-<wbr>989e50ba297c8bab=
8fe8fbd3759ac6<wbr>d2</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; there&#39;s some semantics in this (first), and then i started the=
<br>
&gt;&gt; evaluation by removing those considerations that i thought were ei=
ther<br>
&gt;&gt; already addressed, or that would best be addressed elsewhere.<br>
&gt;&gt;<br>
&gt;&gt; i find it ironic that the telcos don&#39;t want to share their API=
s /with<br>
&gt;&gt; their own customers and users(!)/ out of competition concerns. nor=
mally,<br>
&gt;&gt; i&#39;m the customer of by telco, i don&#39;t compete with it.<br>
&gt;&gt;<br>
&gt;&gt; but a big problem in the mobile markets could then be that vertica=
lly<br>
&gt;&gt; integrated operators can be both mobile OS or mobile app providers=
 /and/<br>
&gt;&gt; Mobile Network Operators at the same time. Oh, if only the telcos =
had<br>
&gt;&gt; lobbied for a competetitve market regulation(!) how many of their<=
br>
&gt;&gt; current predicaments (and also end-user human rights concerns) cou=
ld be<br>
&gt;&gt; solved. but ok.<br>
&gt;&gt;<br>
&gt;&gt; /end whiny transmission<br>
&gt;&gt;<br>
&gt;&gt; amelia<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On 2018-04-09 13:42, Niels ten Oever wrote:<br>
&gt;&gt;&gt; Hi Amelia,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On 04/08/2018 10:19 PM, Amelia Andersdotter wrote:<br>
&gt;&gt;&gt;&gt; I guess the task is to apply the Human Rights Guidelines f=
rom RFC 8280?<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt; Rather the guidelines doc:<br>
&gt;&gt;&gt; <a href=3D"https://tools.ietf.org/html/draft-irtf-hrpc-guideli=
nes-00" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<w=
br>draft-irtf-hrpc-guidelines-00</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; And feedback any potentially useful changes.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; It&#39;s a workshop. As I read the draft report GSMA is de=
fending their<br>
&gt;&gt;&gt;&gt; regulatory and commercial interests, and IETF is saying &q=
uot;well, make it<br>
&gt;&gt;&gt;&gt; work while stuff is encrypted&quot;.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; So do we mean to criticize GSMA&#39;s self-perceived polit=
ical/commercial<br>
&gt;&gt;&gt;&gt; interests from a HR perspective?<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt; We seek to understand the potential impact for the ability of =
end-users<br>
&gt;&gt;&gt; to excercise their human rights, a consequence for that could =
be to<br>
&gt;&gt;&gt; criticize the proposed architectural reordering.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; =3D=3D=3D=3D<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The workshop appears not to have touch on the upcoming ePr=
ivacy<br>
&gt;&gt;&gt;&gt; regulation in the EU at all, in spite of it having a fairl=
y big impact<br>
&gt;&gt;&gt;&gt; on many GSMA members. In particular, GSMA has been lobbyin=
g /against/<br>
&gt;&gt;&gt;&gt; the ePrivacy regulation, in spite of the IETF helpfully so=
lving many of<br>
&gt;&gt;&gt;&gt; their regulatory challenges under the law.<br>
&gt;&gt;&gt; Interesting - this could fall under the privacy part.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Telcos are in the place where they want to sell amounts of=
 data. HTTPS<br>
&gt;&gt;&gt;&gt; increases the amount of data, making telco consumer potent=
ially<br>
&gt;&gt;&gt; decreases, right?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; unhappier. Encryption can also slow stuff down, and while =
some vendors<br>
&gt;&gt;&gt;&gt; say that that&#39;s an issue of the past, it&#39;s possibl=
e that it isn&#39;t in for<br>
&gt;&gt;&gt;&gt; instance the developing world. Probably Facebook Free Basi=
c connections<br>
&gt;&gt;&gt;&gt; have data on this.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; In some countries, notably the UK, telcos may be under obl=
igation to<br>
&gt;&gt;&gt;&gt; generally filter connections (ensure they&#39;re porn-free=
). I find that<br>
&gt;&gt;&gt;&gt; policy disagreeable, but nevertheless it&#39;s there. For =
telcos it&#39;s a<br>
&gt;&gt;&gt;&gt; challenge.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt; This has an impact on FoE. I don&#39;t think we need to have a=
n opinion on<br>
&gt;&gt;&gt; everything from the get-go, but rather show the (potential) im=
plications.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; In Sweden, before the EU open internet regulation entered =
into effect,<br>
&gt;&gt;&gt;&gt; several telcos were investigated for traffic prioritisatio=
n (which was<br>
&gt;&gt;&gt;&gt; suspected to run contrary to ePrivacy directive obligation=
s not to<br>
&gt;&gt;&gt;&gt; monitor traffic). Ironically, the EU open internet law kin=
d of permitted<br>
&gt;&gt;&gt;&gt; commercially motivated traffic discrimination so those inq=
uiries have<br>
&gt;&gt;&gt;&gt; since been cancelled. The new ANACOM case in Portugal may =
change this<br>
&gt;&gt;&gt;&gt; interpretation of what the open internet regulation says, =
but I don&#39;t<br>
&gt;&gt;&gt;&gt; perceive Portugal to be heading in that direction.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt; Cheers,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Niels<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; best regards,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Amelia<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On 2018-04-08 12:30, Niels ten Oever wrote:<br>
&gt;&gt;&gt;&gt;&gt; Amelia know more about radio networks than I do methin=
ks, but happy to<br>
&gt;&gt;&gt;&gt;&gt; do so if Amelia is not available.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Cheers,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Niels<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Sent from Blue &lt;<a href=3D"http://www.bluemail.me/r=
?b=3D12687" rel=3D"noreferrer" target=3D"_blank">http://www.bluemail.me/r?b=
=3D<wbr>12687</a>&gt;<br>
&gt;&gt;&gt;&gt;&gt; On Apr 7, 2018, at 22:43, Shivan &lt;<a href=3D"mailto=
:shivankaul.1993@gmail.com">shivankaul.1993@gmail.com</a><br>
&gt;&gt;&gt;&gt;&gt; &lt;mailto:<a href=3D"mailto:shivankaul.1993@gmail.com=
">shivankaul.1993@gmail.<wbr>com</a>&gt;&gt; wrote:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0I could take a look, if someone cou=
ld work with me.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0On Sat, Apr 7, 2018, 11:36 AM Steph=
ane Bortzmeyer<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0&lt;<a href=3D"mailto:bortzmeyer@ni=
c.fr">bortzmeyer@nic.fr</a> &lt;mailto:<a href=3D"mailto:bortzmeyer@nic.fr"=
>bortzmeyer@nic.fr</a>&gt;&gt; wrote:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Obvious HR consequenc=
es. Any volunteer?<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0---------- Forwarded =
message ----------<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0From:=C2=A0IAB Execut=
ive Administrative Manager &lt;<a href=3D"mailto:execd@iab.org">execd@iab.o=
rg</a><br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;mailto:<a href=3D=
"mailto:execd@iab.org">execd@iab.org</a>&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0To:=C2=A0IETF Announc=
ement List &lt;<a href=3D"mailto:ietf-announce@ietf.org">ietf-announce@ietf=
.org</a><br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;mailto:<a href=3D=
"mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a><wbr>&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Cc:=C2=A0<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Bcc:=C2=A0<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Date:=C2=A0Tue, 03 Ap=
r 2018 15:08:39 -0700<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Subject:=C2=A0Call fo=
r Comment: &lt;draft-iab-marnew-report-01&gt; (IAB<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Workshop on Managing =
Radio Networks in an Encrypted World<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(MaRNEW) Report)<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0This is an announceme=
nt of an IETF-wide Call for Comment on<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-iab-marnew-repo=
rt-01.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The document is being=
 considered for publication as an<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Informational RFC<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0within the IAB stream=
, and is available for inspection at:<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://da=
tatracker.ietf.org/doc/draft-iab-marnew-report/" rel=3D"noreferrer" target=
=3D"_blank">https://datatracker.ietf.org/<wbr>doc/draft-iab-marnew-report/<=
/a><br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The Call for Comment =
will last until 2018-05-01. Please send<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0comments to<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:arc=
hitecture-discuss@ietf.org">architecture-discuss@ietf.org</a><br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;mailto:<a href=3D=
"mailto:architecture-discuss@ietf.org">architecture-discuss@<wbr>ietf.org</=
a>&gt; and <a href=3D"mailto:iab@iab.org">iab@iab.org</a><br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;mailto:<a href=3D=
"mailto:iab@iab.org">iab@iab.org</a>&gt;.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Abstract<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0The MarN=
EW workshop aimed to discuss solutions for bandwidth<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0optimisa=
tion on mobile networks for encrypted content, as<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0current<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0solution=
s rely on unencrypted content which is not<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0indicative of the<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0security=
 needs of today&#39;s Internet users.=C2=A0 The workshop<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0gathered IETF<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0attendee=
s, IAB members and various organisations involved<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0in the<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0telecomm=
unications industry including original equipment<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0manufact=
urers and mobile network operators.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0The grou=
p discussed the current Internet encryption trends and<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0deployme=
nt issues identified within the IETF, and the<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0privacy needs<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0of users=
 which should be adhered.=C2=A0 Solutions designed<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0around sharing<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0data fro=
m the network to the endpoints and vice versa were then<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0discusse=
d as well as analysing whether the current issues<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0experienced<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0on the t=
ransport layer are also playing a role here.=C2=A0 Content<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0provider=
s and CDNs gave an honest view of their experiences<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0delivery<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0content =
with mobile network operators.=C2=A0 Finally, technical<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0responses<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0to regul=
ation was discussed to help the regulated<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0industries relay<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0the issu=
es of impossible to implement or bad-for-privacy<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0technologies<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0back to =
regulators.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0A group =
of suggested solutions were devised which will be<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0discussed<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0in vario=
us IETF groups moving forward.<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0_____________________=
_________<wbr>_________________<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0HR-rt mailing list<br=
>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:HR-=
rt@irtf.org">HR-rt@irtf.org</a> &lt;mailto:<a href=3D"mailto:HR-rt@irtf.org=
">HR-rt@irtf.org</a>&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://ww=
w.irtf.org/mailman/listinfo/hr-rt" rel=3D"noreferrer" target=3D"_blank">htt=
ps://www.irtf.org/mailman/<wbr>listinfo/hr-rt</a><br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0------------------------------<wbr>=
------------------------------<wbr>------------<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0HR-rt mailing list<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:HR-rt@irtf.org">H=
R-rt@irtf.org</a><br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.irtf.org/mai=
lman/listinfo/hr-rt" rel=3D"noreferrer" target=3D"_blank">https://www.irtf.=
org/mailman/<wbr>listinfo/hr-rt</a><br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;<br>
&gt; <br>
<br>
</div></div></blockquote></div><br></div>

--00000000000071652d056b3c4249--


From nobody Thu May  3 12:42:07 2018
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: hr-rt@ietfa.amsl.com
Delivered-To: hr-rt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91FE112DA09 for <hr-rt@ietfa.amsl.com>; Thu,  3 May 2018 12:42:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 xtZ-QLotK0pB for <hr-rt@ietfa.amsl.com>; Thu,  3 May 2018 12:42:00 -0700 (PDT)
Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::22d]) (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 4FA1E1241F3 for <hr-rt@irtf.org>; Thu,  3 May 2018 12:42:00 -0700 (PDT)
Received: by mail-yw0-x22d.google.com with SMTP id p144-v6so6019688ywg.7 for <hr-rt@irtf.org>; Thu, 03 May 2018 12:42:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=51BA51Pfw6XXoEHfiAUKi9yXcKezpjBtmnlzQsTzy28=; b=Ttb//Mruos5t4xs8KBi7vN/Ee6VQOqYRnCMIbbOBUwO2UE5PWr87A9k9eA1nQc9cQJ go6N981rankOy8BtlwYaR1olTW+BUjlI0OEZTcywgEoMlnihIpsZ/DLBIWmcuxlpS1Fd p5XmZ239B7cjQDmcG5aItCUdbN2D0L9EMkX9zlYdSvA1YEXFLi+p+gftQyVGAqpmxJ/z tTUn2WlcnZpMb/7T6OqsIgUsWETH6sTuKeRVVRRH6SbXEbWopyUy5VGenym5oMTbSup+ 9sZyaU/k+yycW0IJuhvcl8JZA1WmuxwKvD9cswaOB19QSI8PwY/9r4/tmTf0ocIUfzrp sX8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=51BA51Pfw6XXoEHfiAUKi9yXcKezpjBtmnlzQsTzy28=; b=qGUmJtJnDFmUcbjjrkpV5VS4HI6Yoym8WV5Bn9Z/w55ugHUH+tOp0UaUwe6WJaTqoW KjzwLkNhfJU+/wsTcxaJhiYD4dRjGtsiU5UyNxLca3eGSKmw8m5nHWvvfWxS466/V6kM MVPXkjnXDS5IQpLL080t7SFtGQ3Dmla0B8Ffh/N4zCtz/xaYamSseys3JeAZ5Fs2zBQj QMWdH9UUP5kGwgkEsHTOHXRKb6hzg2klwJknCy06Cse4osVhYLMto4uHw82fMjzL1BpV LhNH0jvLcBBHGnkY+XR1Mu/uM5Z6RF7td/mBdPfoyGANkAJfbN1L4OiSPi/r4Rot2slG iA7w==
X-Gm-Message-State: ALQs6tAwGIJt4rPsQ31/1AcO7v1+psB86IFFE5rf8DNr0XUgUS6lMkjo x9fsERc8mjX/DNrQKK4DSp7rch8PXtl08tZBhHs=
X-Google-Smtp-Source: AB8JxZpbvaZVQSb/+o5AS1q9cwZAG0CvIbI6yRBINCFlPvwZGsAUAZ7tQ4gttNjpQcepRtD76U09j9MbD/8PtzLHvPM=
X-Received: by 2002:a81:29d1:: with SMTP id p200-v6mr13994372ywp.424.1525376519232;  Thu, 03 May 2018 12:41:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a25:d014:0:0:0:0:0 with HTTP; Thu, 3 May 2018 12:41:58 -0700 (PDT)
In-Reply-To: <CAG3f7Mgd3yArxLsGdMS6-Ki2GqemtKhTLeHXrD8mqEMnV7CXLg@mail.gmail.com>
References: <CAG3f7Mgd3yArxLsGdMS6-Ki2GqemtKhTLeHXrD8mqEMnV7CXLg@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 3 May 2018 14:41:58 -0500
Message-ID: <CAKKJt-fV8r-9ysHgD+261J8vxy3vPsD2w463T_kg7mDWdyZu5w@mail.gmail.com>
To: Shivan <shivankaul.1993@gmail.com>
Cc: hr-rt@irtf.org, architecture-discuss@ietf.org, IAB IAB <iab@iab.org>
Content-Type: multipart/alternative; boundary="00000000000093e065056b52652d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/FDgan7LSBGgx2t2fVmjOqgaFBxQ>
Subject: Re: [HT-rt] [arch-d]  HR-RT Review of draft-iab-marnew-report-01
X-BeenThere: hr-rt@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Human Rights Protocol Considerations Review Team <hr-rt.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hr-rt/>
List-Post: <mailto:hr-rt@irtf.org>
List-Help: <mailto:hr-rt-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 May 2018 19:42:05 -0000

--00000000000093e065056b52652d
Content-Type: text/plain; charset="UTF-8"

Hi, Shivan,

On Wed, May 2, 2018 at 12:11 PM, Shivan <shivankaul.1993@gmail.com> wrote:

> This is a review done within the framework of the Human Rights Review
> Team. It was done by Amelia Andersdotter and Shivan Kaul Sahib. The Human
> Rights Review Team aims to implement and improve the guidelines for
> human rights considerations provided in RFC8280, and seek to mitigate
> potentially adverse human rights impacts that IETF and IRTF documents
> might have.
>

Thanks for the comments. On one point below ...


> We find the topics addressed during the workshop interesting and look
> forward to following future developments.
>
> ---
>
> Document: draft-iab-marnew-report-01
> <https://datatracker.ietf.org/doc/draft-iab-marnew-report/>
> https://datatracker.ietf.org/doc/draft-iab-marnew-report/
>
> Review:
>
> The Human Rights in Protocols Research Group welcomes the draft report
> from the MaRNEW workshop. In particular, we welcome the efforts to continue
> advancing an encrypted, secure and human rights enabling environment, as
> well as solid assessments of the potential impacts of considered remedies
> to mobile network operator difficulties on the right to privacy of an
> individual.
>
> In this regard, we wish to remind the drafters and the IAB of the inherent
> connection between privacy and freedom of expression. The right to privacy,
> or to one's own personhood, reinforces the freedom of expression and
> freedom of opinion.
>
> Semantic Suggestions
> ===========================
>
> The following sections addresses a few semantic problems in the draft
> report, that were they solved the draft report would be easier to parse
> from both a human rights perspective, and from a business, legal or
> technical perspective.
>
> 1. Abstract, para 2:
>
> Problem: Draft text contains  value judgements on participants'
> presentations that could be avoided.
>
> Solution: Remove the word "honest" in relation to CDN presentations, since
> it may cause readers to assume that other presenters were less forthcoming.
>
> The new paragraph would read
>
>    The group discussed the current Internet encryption trends and
>    deployment issues identified within the IETF, and the privacy needs
>    of users which should be adhered.  Solutions designed around sharing
>    data from the network to the endpoints and vice versa were then
>    discussed as well as analysing whether the current issues experienced
>    on the transport layer are also playing a role here.  Content
>    providers and CDNs gave their views of delivering
>    content with mobile network operators.  Finally, technical responses
>    to regulation was discussed to help the regulated industries relay
>    the issues of impossible to implement or bad-for-privacy technologies
>    back to regulators.
>
> 2. Section 1, Introduction:
>
> Problem: It is unclear whether the "requirements" referred to imply
> regulatory requirements enforceable by government authorities, or technical
> requirements. Because of the nature of issues discussed during the
> workshop, understanding what sorts of "requirements" are being referred to
> is imperative.
>
> Solution: Specify the nature of the requirements being referred to, or
> remove the reference to requirements.
>
> The new Introduction would read
>
>    Mobile networks have a set of properties which
>    places a large emphasis on sophisticated bandwidth optimization.
>    Encryption is increasing on the Internet which is positive for
>    consumer and business privacy and security.  Many existing mobile
>    bandwidth optimization solutions primarily operate on non-encrypted
>    communications; this can lead to performance issues being amplified
>    on mobile networks.  Encryption on networks will continue to
>    increase; and with this understanding the workshop aimed to
>    understand how we can solve the issues of bandwidth optimization and
>    performance on radio networks in this encrypted world.
>
> 3. Section 1.1:
>
> Problem: The first paragraph mixes business models with technical
> necessities. The last paragraph in the section Understanding "Bandwidth
> Optimization" refers to regulatory requirements (within the meaning of
> government enforced requirements or legal requirements, cf above) on mobile
> network operators to perform traffic filtering and monitoring.
>
> Solution: It may facilitate understanding of human rights impacts to
> separate technical considerations from business considerations and legal
> considerations. Paragraph 3 ("Many of these functions can continue...")
> could be put as the last paragraph, while Paragraph 1 could be split into a
> technical section and a business model section, followed by a legal section.
>
>
>    For the purposes of this workshop, bandwidth optimization encompasses
>    a variety of technical topics related to traffic engineering,
>    prioritisation, optimisation and efficiency enhancements. It also
> encompasses
>    user-related topics such as specific subscription or billing models,
> and may touch upon regulatory aspects or other issues relating to
> regulatory, within the meaning of government initiated, concerns.
>
>    The first category of bandwidth optimization includes:
>
>    o  Caching
>
>    o  Prioritisation of interactive traffic over background traffic
>
>    o  Per-user bandwidth limit
>
>    The second category of bandwidth optimization may depend on either of
> the first category optimization strategies, but may, in particular, also
> encompass:
>
>    o  Business-related topics such as content delivery arrangements with
>       specific content providers.
>
>    Finally, while not strictly speaking traffic management, some
>    networks employ policy-based filtering (e.g., requested parental
>    controls) and many networks support some form of legal interception
>    functionality per applicable laws.
>
>    Many of these functions can continue as they're performed today, even
>    with more encryption.  Others are using methods which inspect parts
>    of the communication that are encrypted, and these will have to be
>    done differently in an encrypted Internet.
>
>
> 4. Section 4:
>
> Problem: QUIC is an active area of work for the IETF in the transport
> layer - this section barely mentions it, and even then does so vaguely.
> What problems are solved by QUIC that are general problems rather than TCP
> problems? What was the nature of the disagreement around this?
>
> Solution: More detail about how QUIC fits into transport-layer work would
> make this section more relevant. In addition, there has been discussion
> involving network operators around technical details that have potential
> privacy impacts within the QUIC working group (SPIN bit); this section
> would benefit greatly from an examination of that.
>

I have comments from two other reviewers asking that this document actually
state the dates of the workshop, and I'll add that.

If the version of the draft you reviewed had included those dates, it would
have been clearer that the workshop happened in September 2015, which was
more than a year before QUIC was chartered (BOF in July 2016, chartered in
October 2016).

I'm helping the IAB finish this report, so taking direction from them, but
my understanding is that IAB workshop reports should reflect the situation
at the time of the workshop, so I shouldn't say much about QUIC in the
workshop report.

FWIW, I agree with you, but I'm keeping that opinion out of the report ...
and now you know why.

Spencer

Human Rights Considerations
> ===========================
>
> Upon consideration of the draft report, no implications for
> internationalization ([RFC8280], sec. 6.2.5), heterogeneity support
> ([RFC8280], sec. 6.2.8), accessibility ([RFC8280], sec. 6.2.11) or
> localization ([RFC8280], sec. 6.2.12) have been found. We will further
> suppose that issues relating to Anonymity ([RFC8280], sec. 6.2.9),
> Pseudonymity ([RFC8280], sec. 6.2.10) and Confidentiality ([RFC8280], sec.
> 6.2.16) have been sufficiently addressed in the draft as is.
>
> In the below text, Security ([RFC8280], sec. 6.2.4), Integrity ([RFC8280],
> sec. 6.2.16) and Authenticity ([RFC8280], sec. 6.2.17) are further
> considered to have been addressed, or as in progress of being addressed by
> the specific endeavours pointed out in the report. As such, this assessment
> hopes to serve as a complement to remaining Human Rights Considerations
> Guidelines which were not addressed by the MaRNEW draft.
>
> ## Privacy ([RFC8280], sec. 6.2.2)
>
> We laud the general emphasis on considering user privacy concerns
> paramount [Section 2.1.1, 2.3 etc].
>
> In Section 3.1.1, para 1, it would be useful to emphasize that middleboxes
> that are "authenticated and invoked explicitly" might not be very effective
> at conserving user privacy if they lead to auto-click through. In practice,
> "opted-in" middleboxes might not be much better than transparent
> middleboxes. Additionally, this poses the danger of making matters worse if
> users assume that because they haven't been asked for middlebox permission,
> they are not going through a middlebox. For users accessing the Internet on
> a browser client: if the connection is MITMed by a middlebox, the browser
> would somehow need to convey this effectively and actionably to the user.
> Whatever effort is expended on this should involve browser vendors.
>
> ## Connectivity ([RFC8280], sec. 6.2..1)
>
> It is a priori obvious that a discussion with mobile network operators
> would touch upon connectivity. As a general comment, the HRPC RG is not
> concerned that encrypted internet traffic could create topological problems
> in network deployment with respect to density of base stations. It is more
> sensible to imagine that the density of base stations is kept low by
> deployers to save money on infrastructure roll-out.
>
> In the MarNEW draft report, middleboxes are brought up frequently as an
> example of infrastructure rendered less useful by the ubiquitous adoption
> of encryption. Middleboxes may enhance access to content for individuals,
> and may also interfere with their ability to enjoy content free of
> surveillance, censorship or content manipulation. The focus of the workshop
> of exploring ways in which encrypted materials can benefit from the same
> speed of deliverance as un-encrypted materials is therefore welcome.
>
> ## Content Agnosticism
>
> Traffic prioritisation, whether based on technical or commercial grounds,
> risks interfering with an individual's right to freedom of expression or
> opinion, by restricting access or enjoy content of their own choosing. As
> such, prioritisation should be made explicit and obvious, and subject to
> consent from the individual, whether the motivations for deployment are
> commercial or technical.
>
> It is clear that internet filtering and blocking of content of specific
> types, whether motivated by network management or regulatory concerns, does
> not fulfill a content agnosticism criterion. It is the observation of HRPC
> that [RFC7725] (An HTTP Status Code to Report Legal Obstacles) may assist
> communication of specific filtering and blocking operations in action.
>
> It the the impetus of the Human Rights Guidelines in RFC8280 that content
> agnosticism be respected by protocols developed in the IETF, and in general
> an accepted view in the global human rights community that content
> agnosticism is desirable at all levels of technical infrastructure. As
> such, the HRPC RG is concerned about ideas that traffic be classified
> through additional headers or metadata, identifying traffic via 5-tuples,
> trust models and frameworks, or heuristics.
>
>
>
>
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss
>
>

--00000000000093e065056b52652d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, Shivan,=C2=A0<div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Wed, May 2, 2018 at 12:11 PM, Shivan <span dir=3D"ltr">=
&lt;<a href=3D"mailto:shivankaul.1993@gmail.com" target=3D"_blank">shivanka=
ul.1993@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><=
div dir=3D"ltr"><div><div><span style=3D"color:rgb(51,51,51);font-family:ge=
orgia,serif">This is a review done within the framework of the Human Rights=
 Review</span><br></div><div><div><font color=3D"#333333" face=3D"georgia, =
serif">Team. It was done by Amelia Andersdotter and Shivan Kaul Sahib. The =
Human</font></div><div><font color=3D"#333333" face=3D"georgia, serif">Righ=
ts Review Team aims to implement and improve the guidelines for</font></div=
><div><font color=3D"#333333" face=3D"georgia, serif">human rights consider=
ations provided in RFC8280, and seek to mitigate</font></div><div><font col=
or=3D"#333333" face=3D"georgia, serif">potentially adverse human rights imp=
acts that IETF and IRTF documents</font></div><div><font color=3D"#333333" =
face=3D"georgia, serif">might have.</font></div></div></div></div></blockqu=
ote><div><br></div><div>Thanks for the comments. On one point below ...</di=
v><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><di=
v><span style=3D"color:rgb(51,51,51);font-family:georgia,serif">We find the=
 topics addressed during the workshop interesting and look</span><br></div>=
<div><font color=3D"#333333" face=3D"georgia, serif">forward to following f=
uture developments.</font></div><div><font color=3D"#333333" face=3D"georgi=
a, serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, se=
rif">---</font></div><div><font color=3D"#333333" face=3D"georgia, serif"><=
br></font></div><div><font color=3D"#333333" face=3D"georgia, serif">Docume=
nt: <a href=3D"https://datatracker.ietf.org/doc/draft-iab-marnew-report/" t=
arget=3D"_blank">draft-iab-marnew-report-01</a></font></div><div><a href=3D=
"https://datatracker.ietf.org/doc/draft-iab-marnew-report/" target=3D"_blan=
k">https://datatracker.ietf.org/<wbr>doc/draft-iab-marnew-report/</a><br></=
div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><=
div><font color=3D"#333333" face=3D"georgia, serif">Review:</font></div><di=
v><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><fo=
nt color=3D"#333333" face=3D"georgia, serif">The Human Rights in Protocols =
Research Group welcomes the draft report from the MaRNEW workshop. In parti=
cular, we welcome the efforts to continue advancing an encrypted, secure an=
d human rights enabling environment, as well as solid assessments of the po=
tential impacts of considered remedies to mobile network operator difficult=
ies on the right to privacy of an individual.</font></div><div><font color=
=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=3D"#=
333333" face=3D"georgia, serif">In this regard, we wish to remind the draft=
ers and the IAB of the inherent connection between privacy and freedom of e=
xpression. The right to privacy, or to one&#39;s own personhood, reinforces=
 the freedom of expression and freedom of opinion.</font></div><div><font c=
olor=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=
=3D"#333333" face=3D"georgia, serif">Semantic Suggestions</font></div><div>=
<font color=3D"#333333" face=3D"georgia, serif">=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</font></div><div><fo=
nt color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font co=
lor=3D"#333333" face=3D"georgia, serif">The following sections addresses a =
few semantic problems in the draft report, that were they solved the draft =
report would be easier to parse from both a human rights perspective, and f=
rom a business, legal or technical perspective.</font></div><div><font colo=
r=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=3D"=
#333333" face=3D"georgia, serif">1. Abstract, para 2:</font></div><div><fon=
t color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font col=
or=3D"#333333" face=3D"georgia, serif">Problem: Draft text contains=C2=A0 v=
alue judgements on participants&#39; presentations that could be avoided.</=
font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font>=
</div><div><font color=3D"#333333" face=3D"georgia, serif">Solution: Remove=
 the word &quot;honest&quot; in relation to CDN presentations, since it may=
 cause readers to assume that other presenters were less forthcoming.</font=
></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></di=
v><div><font color=3D"#333333" face=3D"georgia, serif">The new paragraph wo=
uld read</font></div><div><font color=3D"#333333" face=3D"georgia, serif"><=
br></font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0=
 =C2=A0The group discussed the current Internet encryption trends and</font=
></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0de=
ployment issues identified within the IETF, and the privacy needs</font></d=
iv><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0of use=
rs which should be adhered.=C2=A0 Solutions designed around sharing</font><=
/div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0data=
 from the network to the endpoints and vice versa were then</font></div><di=
v><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0discussed as=
 well as analysing whether the current issues experienced</font></div><div>=
<font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0on the transpo=
rt layer are also playing a role here.=C2=A0 Content</font></div><div><font=
 color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0providers and CDNs =
gave their views of delivering</font></div><div><font color=3D"#333333" fac=
e=3D"georgia, serif">=C2=A0 =C2=A0content with mobile network operators.=C2=
=A0 Finally, technical responses</font></div><div><font color=3D"#333333" f=
ace=3D"georgia, serif">=C2=A0 =C2=A0to regulation was discussed to help the=
 regulated industries relay</font></div><div><font color=3D"#333333" face=
=3D"georgia, serif">=C2=A0 =C2=A0the issues of impossible to implement or b=
ad-for-privacy technologies</font></div><div><font color=3D"#333333" face=
=3D"georgia, serif">=C2=A0 =C2=A0back to regulators.</font></div><div><font=
 color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font colo=
r=3D"#333333" face=3D"georgia, serif">2. Section 1, Introduction:</font></d=
iv><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><d=
iv><font color=3D"#333333" face=3D"georgia, serif">Problem: It is unclear w=
hether the &quot;requirements&quot; referred to imply regulatory requiremen=
ts enforceable by government authorities, or technical requirements. Becaus=
e of the nature of issues discussed during the workshop, understanding what=
 sorts of &quot;requirements&quot; are being referred to is imperative.</fo=
nt></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></=
div><div><font color=3D"#333333" face=3D"georgia, serif">Solution: Specify =
the nature of the requirements being referred to, or remove the reference t=
o requirements.</font></div><div><font color=3D"#333333" face=3D"georgia, s=
erif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, serif"=
>The new Introduction would read</font></div><div><font color=3D"#333333" f=
ace=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" face=
=3D"georgia, serif">=C2=A0 =C2=A0Mobile networks have a set of properties w=
hich</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=
=A0 =C2=A0places a large emphasis on sophisticated bandwidth optimization.<=
/font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=
=A0Encryption is increasing on the Internet which is positive for</font></d=
iv><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0consum=
er and business privacy and security.=C2=A0 Many existing mobile</font></di=
v><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0bandwid=
th optimization solutions primarily operate on non-encrypted</font></div><d=
iv><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0communicati=
ons; this can lead to performance issues being amplified</font></div><div><=
font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0on mobile netwo=
rks.=C2=A0 Encryption on networks will continue to</font></div><div><font c=
olor=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0increase; and with th=
is understanding the workshop aimed to</font></div><div><font color=3D"#333=
333" face=3D"georgia, serif">=C2=A0 =C2=A0understand how we can solve the i=
ssues of bandwidth optimization and</font></div><div><font color=3D"#333333=
" face=3D"georgia, serif">=C2=A0 =C2=A0performance on radio networks in thi=
s encrypted world.</font></div><div><font color=3D"#333333" face=3D"georgia=
, serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, ser=
if">3. Section 1.1:</font></div><div><font color=3D"#333333" face=3D"georgi=
a, serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, se=
rif">Problem: The first paragraph mixes business models with technical nece=
ssities. The last paragraph in the section Understanding &quot;Bandwidth Op=
timization&quot; refers to regulatory requirements (within the meaning of g=
overnment enforced requirements or legal requirements, cf above) on mobile =
network operators to perform traffic filtering and monitoring.</font></div>=
<div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div>=
<font color=3D"#333333" face=3D"georgia, serif">Solution: It may facilitate=
 understanding of human rights impacts to separate technical considerations=
 from business considerations and legal considerations. Paragraph 3 (&quot;=
Many of these functions can continue...&quot;) could be put as the last par=
agraph, while Paragraph 1 could be split into a technical section and a bus=
iness model section, followed by a legal section.</font></div><div><font co=
lor=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=
=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=3D"#=
333333" face=3D"georgia, serif">=C2=A0 =C2=A0For the purposes of this works=
hop, bandwidth optimization encompasses</font></div><div><font color=3D"#33=
3333" face=3D"georgia, serif">=C2=A0 =C2=A0a variety of technical topics re=
lated to traffic engineering,</font></div><div><font color=3D"#333333" face=
=3D"georgia, serif">=C2=A0 =C2=A0prioritisation, optimisation and efficienc=
y enhancements. It also encompasses</font></div><div><font color=3D"#333333=
" face=3D"georgia, serif">=C2=A0 =C2=A0user-related topics such as specific=
 subscription or billing models, and may touch upon regulatory aspects or o=
ther issues relating to regulatory, within the meaning of government initia=
ted, concerns.</font></div><div><font color=3D"#333333" face=3D"georgia, se=
rif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, serif">=
=C2=A0 =C2=A0The first category of bandwidth optimization includes:</font><=
/div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div>=
<div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0o=C2=A0 C=
aching</font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br=
></font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =
=C2=A0o=C2=A0 Prioritisation of interactive traffic over background traffic=
</font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></fon=
t></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0o=
=C2=A0 Per-user bandwidth limit</font></div><div><font color=3D"#333333" fa=
ce=3D"georgia, serif">=C2=A0 =C2=A0</font></div><div><font color=3D"#333333=
" face=3D"georgia, serif">=C2=A0 =C2=A0The second category of bandwidth opt=
imization may depend on either of the first category optimization strategie=
s, but may, in particular, also encompass:</font></div><div><font color=3D"=
#333333" face=3D"georgia, serif"><br></font></div><div><font color=3D"#3333=
33" face=3D"georgia, serif">=C2=A0 =C2=A0o=C2=A0 Business-related topics su=
ch as content delivery arrangements with</font></div><div><font color=3D"#3=
33333" face=3D"georgia, serif">=C2=A0 =C2=A0 =C2=A0 specific content provid=
ers.</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=
=A0 =C2=A0 =C2=A0=C2=A0</font></div><div><font color=3D"#333333" face=3D"ge=
orgia, serif">=C2=A0 =C2=A0Finally, while not strictly speaking traffic man=
agement, some</font></div><div><font color=3D"#333333" face=3D"georgia, ser=
if">=C2=A0 =C2=A0networks employ policy-based filtering (e.g., requested pa=
rental</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=
=A0 =C2=A0controls) and many networks support some form of legal intercepti=
on</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =
=C2=A0functionality per applicable laws.</font></div><div><font color=3D"#3=
33333" face=3D"georgia, serif"><br></font></div><div><font color=3D"#333333=
" face=3D"georgia, serif">=C2=A0 =C2=A0Many of these functions can continue=
 as they&#39;re performed today, even</font></div><div><font color=3D"#3333=
33" face=3D"georgia, serif">=C2=A0 =C2=A0with more encryption.=C2=A0 Others=
 are using methods which inspect parts</font></div><div><font color=3D"#333=
333" face=3D"georgia, serif">=C2=A0 =C2=A0of the communication that are enc=
rypted, and these will have to be</font></div><div><font color=3D"#333333" =
face=3D"georgia, serif">=C2=A0 =C2=A0done differently in an encrypted Inter=
net.</font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br><=
/font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font=
></div><div><font color=3D"#333333" face=3D"georgia, serif">4. Section 4:</=
font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font>=
</div><div><font color=3D"#333333" face=3D"georgia, serif">Problem: QUIC is=
 an active area of work for the IETF in the transport layer - this section =
barely mentions it, and even then does so vaguely. What problems are solved=
 by QUIC that are general problems rather than TCP problems? What was the n=
ature of the disagreement around this?</font></div><div><font color=3D"#333=
333" face=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" =
face=3D"georgia, serif">Solution: More detail about how QUIC fits into tran=
sport-layer work would make this section more relevant. In addition, there =
has been discussion involving network operators around technical details th=
at have potential privacy impacts within the QUIC working group (SPIN bit);=
 this section would benefit greatly from an examination of that.</font></di=
v></div></div></blockquote><div><br></div><div>I have comments from two oth=
er reviewers asking that this document actually state the dates of the work=
shop, and I&#39;ll add that.=C2=A0</div><div><br></div><div>If the version =
of the draft you reviewed had included those dates, it would have been clea=
rer that the workshop happened in September 2015, which was more than a yea=
r before QUIC was chartered (BOF in July 2016, chartered in October 2016).<=
/div><div><br></div><div>I&#39;m helping the IAB finish this report, so tak=
ing direction from them, but my understanding is that IAB workshop reports =
should reflect the situation at the time of the workshop, so I shouldn&#39;=
t say much about QUIC in the workshop report.=C2=A0</div><div><br></div><di=
v>FWIW, I agree with you, but I&#39;m keeping that opinion out of the repor=
t ... and now you know why.</div><div><br></div><div>Spencer</div><div><br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><span style=
=3D"color:rgb(51,51,51);font-family:georgia,serif">Human Rights Considerati=
ons</span><br></div><div><font color=3D"#333333" face=3D"georgia, serif">=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D</font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br=
></font></div><div><font color=3D"#333333" face=3D"georgia, serif">Upon con=
sideration of the draft report, no implications for internationalization ([=
RFC8280], sec. 6.2.5), heterogeneity support ([RFC8280], sec. 6.2.8), acces=
sibility ([RFC8280], sec. 6.2.11) or localization ([RFC8280], sec. 6.2.12) =
have been found. We will further suppose that issues relating to Anonymity =
([RFC8280], sec. 6.2.9), Pseudonymity ([RFC8280], sec. 6.2.10) and Confiden=
tiality ([RFC8280], sec. 6.2.16) have been sufficiently addressed in the dr=
aft as is.</font></div><div><font color=3D"#333333" face=3D"georgia, serif"=
><br></font></div><div><font color=3D"#333333" face=3D"georgia, serif">In t=
he below text, Security ([RFC8280], sec. 6.2.4), Integrity ([RFC8280], sec.=
 6.2.16) and Authenticity ([RFC8280], sec. 6.2.17) are further considered t=
o have been addressed, or as in progress of being addressed by the specific=
 endeavours pointed out in the report. As such, this assessment hopes to se=
rve as a complement to remaining Human Rights Considerations Guidelines whi=
ch were not addressed by the MaRNEW draft.</font></div><div><font color=3D"=
#333333" face=3D"georgia, serif"><br></font></div><div><font color=3D"#3333=
33" face=3D"georgia, serif">## Privacy ([RFC8280], sec. 6.2.2)</font></div>=
<div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div>=
<font color=3D"#333333" face=3D"georgia, serif">We laud the general emphasi=
s on considering user privacy concerns paramount [Section 2.1.1, 2.3 etc].=
=C2=A0</font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br=
></font></div><div><font color=3D"#333333" face=3D"georgia, serif">In Secti=
on 3.1.1, para 1, it would be useful to emphasize that middleboxes that are=
 &quot;authenticated and invoked explicitly&quot; might not be very effecti=
ve at conserving user privacy if they lead to auto-click through. In practi=
ce, &quot;opted-in&quot; middleboxes might not be much better than transpar=
ent middleboxes. Additionally, this poses the danger of making matters wors=
e if users assume that because they haven&#39;t been asked for middlebox pe=
rmission, they are not going through a middlebox. For users accessing the I=
nternet on a browser client: if the connection is MITMed by a middlebox, th=
e browser would somehow need to convey this effectively and actionably to t=
he user. Whatever effort is expended on this should involve browser vendors=
.</font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></fo=
nt></div><div><font color=3D"#333333" face=3D"georgia, serif">## Connectivi=
ty ([RFC8280], sec. 6.2..1)</font></div><div><font color=3D"#333333" face=
=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" face=3D"g=
eorgia, serif">It is a priori obvious that a discussion with mobile network=
 operators would touch upon connectivity. As a general comment, the HRPC RG=
 is not concerned that encrypted internet traffic could create topological =
problems in network deployment with respect to density of base stations. It=
 is more sensible to imagine that the density of base stations is kept low =
by deployers to save money on infrastructure roll-out.</font></div><div><fo=
nt color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font co=
lor=3D"#333333" face=3D"georgia, serif">In the MarNEW draft report, middleb=
oxes are brought up frequently as an example of infrastructure rendered les=
s useful by the ubiquitous adoption of encryption. Middleboxes may enhance =
access to content for individuals, and may also interfere with their abilit=
y to enjoy content free of surveillance, censorship or content manipulation=
. The focus of the workshop of exploring ways in which encrypted materials =
can benefit from the same speed of deliverance as un-encrypted materials is=
 therefore welcome.</font></div><div><font color=3D"#333333" face=3D"georgi=
a, serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, se=
rif">## Content Agnosticism</font></div><div><font color=3D"#333333" face=
=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" face=3D"g=
eorgia, serif">Traffic prioritisation, whether based on technical or commer=
cial grounds, risks interfering with an individual&#39;s right to freedom o=
f expression or opinion, by restricting access or enjoy content of their ow=
n choosing. As such, prioritisation should be made explicit and obvious, an=
d subject to consent from the individual, whether the motivations for deplo=
yment are commercial or technical.</font></div><div><font color=3D"#333333"=
 face=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" face=
=3D"georgia, serif">It is clear that internet filtering and blocking of con=
tent of specific types, whether motivated by network management or regulato=
ry concerns, does not fulfill a content agnosticism criterion. It is the ob=
servation of HRPC that [RFC7725] (An HTTP Status Code to Report Legal Obsta=
cles) may assist communication of specific filtering and blocking operation=
s in action.</font></div><div><font color=3D"#333333" face=3D"georgia, seri=
f"><br></font></div><div><font color=3D"#333333" face=3D"georgia, serif">It=
 the the impetus of the Human Rights Guidelines in RFC8280 that content agn=
osticism be respected by protocols developed in the IETF, and in general an=
 accepted view in the global human rights community that content agnosticis=
m is desirable at all levels of technical infrastructure. As such, the HRPC=
 RG is concerned about ideas that traffic be classified through additional =
headers or metadata, identifying traffic via 5-tuples, trust models and fra=
meworks, or heuristics.</font></div><div><br></div></div><div style=3D"colo=
r:rgb(51,51,51);font-family:georgia,serif;font-size:small"><br><br></div></=
div>
<br>______________________________<wbr>_________________<br>
Architecture-discuss mailing list<br>
<a href=3D"mailto:Architecture-discuss@ietf.org">Architecture-discuss@ietf.=
org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/architecture-discuss" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinf=
o/architecture-discuss</a><br>
<br></blockquote></div><br></div></div>

--00000000000093e065056b52652d--


From nobody Thu May  3 14:47:57 2018
Return-Path: <shivankaul.1993@gmail.com>
X-Original-To: hr-rt@ietfa.amsl.com
Delivered-To: hr-rt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97D8512EAF3 for <hr-rt@ietfa.amsl.com>; Thu,  3 May 2018 14:47:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 m8vjcWH3G5R0 for <hr-rt@ietfa.amsl.com>; Thu,  3 May 2018 14:47:51 -0700 (PDT)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (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 125AB12EA67 for <hr-rt@irtf.org>; Thu,  3 May 2018 14:47:51 -0700 (PDT)
Received: by mail-lf0-x22b.google.com with SMTP id u21-v6so28137887lfu.9 for <hr-rt@irtf.org>; Thu, 03 May 2018 14:47:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=l8+FFcRQ6uJawLSIWYH2l1LbX1AUhsBAbTEe55JJBlE=; b=sUMS3rZIkhGlwSVtYh0hgTpXFbaYYe/zehSuMlmufNLJmSbaEmKZaF6Kj0Ny0vnZsa rw7ALyjzDoBiDVQOkIbVKyKVK9oi3kpWymv5QCcC0CsRitPeWYvcfuZbzv4/XZMSHqsh LtrhdZchOhfiItpsuR51qOVX1LXCJ8scrUrgiNohXW7uLgXwGmrYcamKgN6YK3P/yHDl eNsmp4qjf7iQYHB7MvFx39d8gjB0bAlCKE/oSpQnT6SJWaHlCnUYVVEa8mv2SkmXpiE/ Sgo9/8Wb5sM3rema5rBp2v0LV7cnV4bkDgktvYz49EtSsrTiHg2ZPOBNkjlOgrkTRaL7 Gkmg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=l8+FFcRQ6uJawLSIWYH2l1LbX1AUhsBAbTEe55JJBlE=; b=GsekMNAJu384660U+7HcN3lJ3gnh1I9YQjNtJND3sBC8hTkkPcO1oY5b9mjUbvSeHH EdxDc9ihaFUJ5oYfrZeMYSMbmUAWfAvLkU4J7ijHo0hVc+S1yj9zKD1WaGaLJ+V/SHIA WOZYk1grh1f4H/r1+7aoB7DV5Rwyvewn8Kpzv1kj5locAa2AatauGt6GVwJkagXMUE0k MUTyMEYYSRRKsaPbMaY4jE5oxtmn+xr8y0k97cD/tKNUzf1rw1GvbW/7epxMrMMSYsoR RC1qqIsgEZHZ/gXJoD/XodO90nR7FM2V5Ic3jAtsTaAaV2ogfvD+ajgCQl72EcUy41Xj mmrw==
X-Gm-Message-State: ALQs6tAXzWWf9Nc/cbzghquK9TQWWh8P/F+uzwLqzHnsCy4mS7eJMj7r NDCpxkIjaGcwkHSToavEjBO0zrz7ZOPIcA0cHIo=
X-Google-Smtp-Source: AB8JxZpvl+u8Vj8Mp5FP1O1lA+zDfv9Tii8IgHvgsl4oDKgEJHnJ9T1s2clhS2Nj3EnLvcfQ2FYfKn15aJbUmpRnY0I=
X-Received: by 2002:a2e:96d2:: with SMTP id d18-v6mr17102815ljj.21.1525384069169;  Thu, 03 May 2018 14:47:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.144.3 with HTTP; Thu, 3 May 2018 14:47:08 -0700 (PDT)
In-Reply-To: <CAKKJt-fV8r-9ysHgD+261J8vxy3vPsD2w463T_kg7mDWdyZu5w@mail.gmail.com>
References: <CAG3f7Mgd3yArxLsGdMS6-Ki2GqemtKhTLeHXrD8mqEMnV7CXLg@mail.gmail.com> <CAKKJt-fV8r-9ysHgD+261J8vxy3vPsD2w463T_kg7mDWdyZu5w@mail.gmail.com>
From: Shivan <shivankaul.1993@gmail.com>
Date: Thu, 3 May 2018 17:47:08 -0400
Message-ID: <CAG3f7MihyyyO6xZ9iGoRq9ZbkYNks8qbw5d_iANHYaodmG5+xA@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: hr-rt@irtf.org, architecture-discuss@ietf.org, IAB IAB <iab@iab.org>
Content-Type: multipart/alternative; boundary="00000000000096daea056b542786"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/LL5TxdKR8idKyOWzSCvYSDPS3SI>
Subject: Re: [HT-rt] [arch-d]  HR-RT Review of draft-iab-marnew-report-01
X-BeenThere: hr-rt@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Human Rights Protocol Considerations Review Team <hr-rt.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hr-rt/>
List-Post: <mailto:hr-rt@irtf.org>
List-Help: <mailto:hr-rt-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 May 2018 21:47:56 -0000

--00000000000096daea056b542786
Content-Type: text/plain; charset="UTF-8"

Thanks Spencer for the clarification!

On Thu, May 3, 2018 at 3:41 PM, Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> Hi, Shivan,
>
> On Wed, May 2, 2018 at 12:11 PM, Shivan <shivankaul.1993@gmail.com> wrote:
>
>> This is a review done within the framework of the Human Rights Review
>> Team. It was done by Amelia Andersdotter and Shivan Kaul Sahib. The Human
>> Rights Review Team aims to implement and improve the guidelines for
>> human rights considerations provided in RFC8280, and seek to mitigate
>> potentially adverse human rights impacts that IETF and IRTF documents
>> might have.
>>
>
> Thanks for the comments. On one point below ...
>
>
>> We find the topics addressed during the workshop interesting and look
>> forward to following future developments.
>>
>> ---
>>
>> Document: draft-iab-marnew-report-01
>> <https://datatracker.ietf.org/doc/draft-iab-marnew-report/>
>> https://datatracker.ietf.org/doc/draft-iab-marnew-report/
>>
>> Review:
>>
>> The Human Rights in Protocols Research Group welcomes the draft report
>> from the MaRNEW workshop. In particular, we welcome the efforts to continue
>> advancing an encrypted, secure and human rights enabling environment, as
>> well as solid assessments of the potential impacts of considered remedies
>> to mobile network operator difficulties on the right to privacy of an
>> individual.
>>
>> In this regard, we wish to remind the drafters and the IAB of the
>> inherent connection between privacy and freedom of expression. The right to
>> privacy, or to one's own personhood, reinforces the freedom of expression
>> and freedom of opinion.
>>
>> Semantic Suggestions
>> ===========================
>>
>> The following sections addresses a few semantic problems in the draft
>> report, that were they solved the draft report would be easier to parse
>> from both a human rights perspective, and from a business, legal or
>> technical perspective.
>>
>> 1. Abstract, para 2:
>>
>> Problem: Draft text contains  value judgements on participants'
>> presentations that could be avoided.
>>
>> Solution: Remove the word "honest" in relation to CDN presentations,
>> since it may cause readers to assume that other presenters were less
>> forthcoming.
>>
>> The new paragraph would read
>>
>>    The group discussed the current Internet encryption trends and
>>    deployment issues identified within the IETF, and the privacy needs
>>    of users which should be adhered.  Solutions designed around sharing
>>    data from the network to the endpoints and vice versa were then
>>    discussed as well as analysing whether the current issues experienced
>>    on the transport layer are also playing a role here.  Content
>>    providers and CDNs gave their views of delivering
>>    content with mobile network operators.  Finally, technical responses
>>    to regulation was discussed to help the regulated industries relay
>>    the issues of impossible to implement or bad-for-privacy technologies
>>    back to regulators.
>>
>> 2. Section 1, Introduction:
>>
>> Problem: It is unclear whether the "requirements" referred to imply
>> regulatory requirements enforceable by government authorities, or technical
>> requirements. Because of the nature of issues discussed during the
>> workshop, understanding what sorts of "requirements" are being referred to
>> is imperative.
>>
>> Solution: Specify the nature of the requirements being referred to, or
>> remove the reference to requirements.
>>
>> The new Introduction would read
>>
>>    Mobile networks have a set of properties which
>>    places a large emphasis on sophisticated bandwidth optimization.
>>    Encryption is increasing on the Internet which is positive for
>>    consumer and business privacy and security.  Many existing mobile
>>    bandwidth optimization solutions primarily operate on non-encrypted
>>    communications; this can lead to performance issues being amplified
>>    on mobile networks.  Encryption on networks will continue to
>>    increase; and with this understanding the workshop aimed to
>>    understand how we can solve the issues of bandwidth optimization and
>>    performance on radio networks in this encrypted world.
>>
>> 3. Section 1.1:
>>
>> Problem: The first paragraph mixes business models with technical
>> necessities. The last paragraph in the section Understanding "Bandwidth
>> Optimization" refers to regulatory requirements (within the meaning of
>> government enforced requirements or legal requirements, cf above) on mobile
>> network operators to perform traffic filtering and monitoring.
>>
>> Solution: It may facilitate understanding of human rights impacts to
>> separate technical considerations from business considerations and legal
>> considerations. Paragraph 3 ("Many of these functions can continue...")
>> could be put as the last paragraph, while Paragraph 1 could be split into a
>> technical section and a business model section, followed by a legal section.
>>
>>
>>    For the purposes of this workshop, bandwidth optimization encompasses
>>    a variety of technical topics related to traffic engineering,
>>    prioritisation, optimisation and efficiency enhancements. It also
>> encompasses
>>    user-related topics such as specific subscription or billing models,
>> and may touch upon regulatory aspects or other issues relating to
>> regulatory, within the meaning of government initiated, concerns.
>>
>>    The first category of bandwidth optimization includes:
>>
>>    o  Caching
>>
>>    o  Prioritisation of interactive traffic over background traffic
>>
>>    o  Per-user bandwidth limit
>>
>>    The second category of bandwidth optimization may depend on either of
>> the first category optimization strategies, but may, in particular, also
>> encompass:
>>
>>    o  Business-related topics such as content delivery arrangements with
>>       specific content providers.
>>
>>    Finally, while not strictly speaking traffic management, some
>>    networks employ policy-based filtering (e.g., requested parental
>>    controls) and many networks support some form of legal interception
>>    functionality per applicable laws.
>>
>>    Many of these functions can continue as they're performed today, even
>>    with more encryption.  Others are using methods which inspect parts
>>    of the communication that are encrypted, and these will have to be
>>    done differently in an encrypted Internet.
>>
>>
>> 4. Section 4:
>>
>> Problem: QUIC is an active area of work for the IETF in the transport
>> layer - this section barely mentions it, and even then does so vaguely.
>> What problems are solved by QUIC that are general problems rather than TCP
>> problems? What was the nature of the disagreement around this?
>>
>> Solution: More detail about how QUIC fits into transport-layer work would
>> make this section more relevant. In addition, there has been discussion
>> involving network operators around technical details that have potential
>> privacy impacts within the QUIC working group (SPIN bit); this section
>> would benefit greatly from an examination of that.
>>
>
> I have comments from two other reviewers asking that this document
> actually state the dates of the workshop, and I'll add that.
>
> If the version of the draft you reviewed had included those dates, it
> would have been clearer that the workshop happened in September 2015, which
> was more than a year before QUIC was chartered (BOF in July 2016, chartered
> in October 2016).
>
> I'm helping the IAB finish this report, so taking direction from them, but
> my understanding is that IAB workshop reports should reflect the situation
> at the time of the workshop, so I shouldn't say much about QUIC in the
> workshop report.
>
> FWIW, I agree with you, but I'm keeping that opinion out of the report ...
> and now you know why.
>
> Spencer
>
> Human Rights Considerations
>> ===========================
>>
>> Upon consideration of the draft report, no implications for
>> internationalization ([RFC8280], sec. 6.2.5), heterogeneity support
>> ([RFC8280], sec. 6.2.8), accessibility ([RFC8280], sec. 6.2.11) or
>> localization ([RFC8280], sec. 6.2.12) have been found. We will further
>> suppose that issues relating to Anonymity ([RFC8280], sec. 6.2.9),
>> Pseudonymity ([RFC8280], sec. 6.2.10) and Confidentiality ([RFC8280], sec.
>> 6.2.16) have been sufficiently addressed in the draft as is.
>>
>> In the below text, Security ([RFC8280], sec. 6.2.4), Integrity
>> ([RFC8280], sec. 6.2.16) and Authenticity ([RFC8280], sec. 6.2.17) are
>> further considered to have been addressed, or as in progress of being
>> addressed by the specific endeavours pointed out in the report. As such,
>> this assessment hopes to serve as a complement to remaining Human Rights
>> Considerations Guidelines which were not addressed by the MaRNEW draft.
>>
>> ## Privacy ([RFC8280], sec. 6.2.2)
>>
>> We laud the general emphasis on considering user privacy concerns
>> paramount [Section 2.1.1, 2.3 etc].
>>
>> In Section 3.1.1, para 1, it would be useful to emphasize that
>> middleboxes that are "authenticated and invoked explicitly" might not be
>> very effective at conserving user privacy if they lead to auto-click
>> through. In practice, "opted-in" middleboxes might not be much better than
>> transparent middleboxes. Additionally, this poses the danger of making
>> matters worse if users assume that because they haven't been asked for
>> middlebox permission, they are not going through a middlebox. For users
>> accessing the Internet on a browser client: if the connection is MITMed by
>> a middlebox, the browser would somehow need to convey this effectively and
>> actionably to the user. Whatever effort is expended on this should involve
>> browser vendors.
>>
>> ## Connectivity ([RFC8280], sec. 6.2..1)
>>
>> It is a priori obvious that a discussion with mobile network operators
>> would touch upon connectivity. As a general comment, the HRPC RG is not
>> concerned that encrypted internet traffic could create topological problems
>> in network deployment with respect to density of base stations. It is more
>> sensible to imagine that the density of base stations is kept low by
>> deployers to save money on infrastructure roll-out.
>>
>> In the MarNEW draft report, middleboxes are brought up frequently as an
>> example of infrastructure rendered less useful by the ubiquitous adoption
>> of encryption. Middleboxes may enhance access to content for individuals,
>> and may also interfere with their ability to enjoy content free of
>> surveillance, censorship or content manipulation. The focus of the workshop
>> of exploring ways in which encrypted materials can benefit from the same
>> speed of deliverance as un-encrypted materials is therefore welcome.
>>
>> ## Content Agnosticism
>>
>> Traffic prioritisation, whether based on technical or commercial grounds,
>> risks interfering with an individual's right to freedom of expression or
>> opinion, by restricting access or enjoy content of their own choosing. As
>> such, prioritisation should be made explicit and obvious, and subject to
>> consent from the individual, whether the motivations for deployment are
>> commercial or technical.
>>
>> It is clear that internet filtering and blocking of content of specific
>> types, whether motivated by network management or regulatory concerns, does
>> not fulfill a content agnosticism criterion. It is the observation of HRPC
>> that [RFC7725] (An HTTP Status Code to Report Legal Obstacles) may assist
>> communication of specific filtering and blocking operations in action.
>>
>> It the the impetus of the Human Rights Guidelines in RFC8280 that content
>> agnosticism be respected by protocols developed in the IETF, and in general
>> an accepted view in the global human rights community that content
>> agnosticism is desirable at all levels of technical infrastructure. As
>> such, the HRPC RG is concerned about ideas that traffic be classified
>> through additional headers or metadata, identifying traffic via 5-tuples,
>> trust models and frameworks, or heuristics.
>>
>>
>>
>>
>> _______________________________________________
>> Architecture-discuss mailing list
>> Architecture-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/architecture-discuss
>>
>>
>

--00000000000096daea056b542786
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:georgia,=
serif;font-size:small;color:#333333">Thanks Spencer for the clarification!<=
/div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu=
, May 3, 2018 at 3:41 PM, Spencer Dawkins at IETF <span dir=3D"ltr">&lt;<a =
href=3D"mailto:spencerdawkins.ietf@gmail.com" target=3D"_blank">spencerdawk=
ins.ietf@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div dir=3D"ltr">Hi, Shivan,=C2=A0<div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote"><span class=3D"">On Wed, May 2, 2018 at 12:11 PM, Shivan <=
span dir=3D"ltr">&lt;<a href=3D"mailto:shivankaul.1993@gmail.com" target=3D=
"_blank">shivankaul.1993@gmail.com</a>&gt;</span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex"><div dir=3D"ltr"><div><div><span style=3D"color:rgb(51,51,5=
1);font-family:georgia,serif">This is a review done within the framework of=
 the Human Rights Review</span><br></div><div><div><font color=3D"#333333" =
face=3D"georgia, serif">Team. It was done by Amelia Andersdotter and Shivan=
 Kaul Sahib. The Human</font></div><div><font color=3D"#333333" face=3D"geo=
rgia, serif">Rights Review Team aims to implement and improve the guideline=
s for</font></div><div><font color=3D"#333333" face=3D"georgia, serif">huma=
n rights considerations provided in RFC8280, and seek to mitigate</font></d=
iv><div><font color=3D"#333333" face=3D"georgia, serif">potentially adverse=
 human rights impacts that IETF and IRTF documents</font></div><div><font c=
olor=3D"#333333" face=3D"georgia, serif">might have.</font></div></div></di=
v></div></blockquote><div><br></div></span><div>Thanks for the comments. On=
 one point below ...</div><div><div class=3D"h5"><div>=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex"><div dir=3D"ltr"><div><div><span style=3D"color:rgb(5=
1,51,51);font-family:georgia,serif">We find the topics addressed during the=
 workshop interesting and look</span><br></div><div><font color=3D"#333333"=
 face=3D"georgia, serif">forward to following future developments.</font></=
div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><=
div><font color=3D"#333333" face=3D"georgia, serif">---</font></div><div><f=
ont color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font c=
olor=3D"#333333" face=3D"georgia, serif">Document: <a href=3D"https://datat=
racker.ietf.org/doc/draft-iab-marnew-report/" target=3D"_blank">draft-iab-m=
arnew-report-01</a></font></div><div><a href=3D"https://datatracker.ietf.or=
g/doc/draft-iab-marnew-report/" target=3D"_blank">https://datatracker.ietf.=
org/d<wbr>oc/draft-iab-marnew-report/</a><br></div><div><font color=3D"#333=
333" face=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" =
face=3D"georgia, serif">Review:</font></div><div><font color=3D"#333333" fa=
ce=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" face=3D=
"georgia, serif">The Human Rights in Protocols Research Group welcomes the =
draft report from the MaRNEW workshop. In particular, we welcome the effort=
s to continue advancing an encrypted, secure and human rights enabling envi=
ronment, as well as solid assessments of the potential impacts of considere=
d remedies to mobile network operator difficulties on the right to privacy =
of an individual.</font></div><div><font color=3D"#333333" face=3D"georgia,=
 serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, seri=
f">In this regard, we wish to remind the drafters and the IAB of the inhere=
nt connection between privacy and freedom of expression. The right to priva=
cy, or to one&#39;s own personhood, reinforces the freedom of expression an=
d freedom of opinion.</font></div><div><font color=3D"#333333" face=3D"geor=
gia, serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, =
serif">Semantic Suggestions</font></div><div><font color=3D"#333333" face=
=3D"georgia, serif">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D</font></div><div><font color=3D"#333333" face=
=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" face=3D"g=
eorgia, serif">The following sections addresses a few semantic problems in =
the draft report, that were they solved the draft report would be easier to=
 parse from both a human rights perspective, and from a business, legal or =
technical perspective.</font></div><div><font color=3D"#333333" face=3D"geo=
rgia, serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia,=
 serif">1. Abstract, para 2:</font></div><div><font color=3D"#333333" face=
=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" face=3D"g=
eorgia, serif">Problem: Draft text contains=C2=A0 value judgements on parti=
cipants&#39; presentations that could be avoided.</font></div><div><font co=
lor=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=
=3D"#333333" face=3D"georgia, serif">Solution: Remove the word &quot;honest=
&quot; in relation to CDN presentations, since it may cause readers to assu=
me that other presenters were less forthcoming.</font></div><div><font colo=
r=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=3D"=
#333333" face=3D"georgia, serif">The new paragraph would read</font></div><=
div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><=
font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0The group discu=
ssed the current Internet encryption trends and</font></div><div><font colo=
r=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0deployment issues identi=
fied within the IETF, and the privacy needs</font></div><div><font color=3D=
"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0of users which should be adh=
ered.=C2=A0 Solutions designed around sharing</font></div><div><font color=
=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0data from the network to =
the endpoints and vice versa were then</font></div><div><font color=3D"#333=
333" face=3D"georgia, serif">=C2=A0 =C2=A0discussed as well as analysing wh=
ether the current issues experienced</font></div><div><font color=3D"#33333=
3" face=3D"georgia, serif">=C2=A0 =C2=A0on the transport layer are also pla=
ying a role here.=C2=A0 Content</font></div><div><font color=3D"#333333" fa=
ce=3D"georgia, serif">=C2=A0 =C2=A0providers and CDNs gave their views of d=
elivering</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=
=C2=A0 =C2=A0content with mobile network operators.=C2=A0 Finally, technica=
l responses</font></div><div><font color=3D"#333333" face=3D"georgia, serif=
">=C2=A0 =C2=A0to regulation was discussed to help the regulated industries=
 relay</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=
=A0 =C2=A0the issues of impossible to implement or bad-for-privacy technolo=
gies</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=
=A0 =C2=A0back to regulators.</font></div><div><font color=3D"#333333" face=
=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" face=3D"g=
eorgia, serif">2. Section 1, Introduction:</font></div><div><font color=3D"=
#333333" face=3D"georgia, serif"><br></font></div><div><font color=3D"#3333=
33" face=3D"georgia, serif">Problem: It is unclear whether the &quot;requir=
ements&quot; referred to imply regulatory requirements enforceable by gover=
nment authorities, or technical requirements. Because of the nature of issu=
es discussed during the workshop, understanding what sorts of &quot;require=
ments&quot; are being referred to is imperative.</font></div><div><font col=
or=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=3D=
"#333333" face=3D"georgia, serif">Solution: Specify the nature of the requi=
rements being referred to, or remove the reference to requirements.</font><=
/div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div>=
<div><font color=3D"#333333" face=3D"georgia, serif">The new Introduction w=
ould read</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=
<br></font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=
=A0 =C2=A0Mobile networks have a set of properties which</font></div><div><=
font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0places a large =
emphasis on sophisticated bandwidth optimization.</font></div><div><font co=
lor=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0Encryption is increasi=
ng on the Internet which is positive for</font></div><div><font color=3D"#3=
33333" face=3D"georgia, serif">=C2=A0 =C2=A0consumer and business privacy a=
nd security.=C2=A0 Many existing mobile</font></div><div><font color=3D"#33=
3333" face=3D"georgia, serif">=C2=A0 =C2=A0bandwidth optimization solutions=
 primarily operate on non-encrypted</font></div><div><font color=3D"#333333=
" face=3D"georgia, serif">=C2=A0 =C2=A0communications; this can lead to per=
formance issues being amplified</font></div><div><font color=3D"#333333" fa=
ce=3D"georgia, serif">=C2=A0 =C2=A0on mobile networks.=C2=A0 Encryption on =
networks will continue to</font></div><div><font color=3D"#333333" face=3D"=
georgia, serif">=C2=A0 =C2=A0increase; and with this understanding the work=
shop aimed to</font></div><div><font color=3D"#333333" face=3D"georgia, ser=
if">=C2=A0 =C2=A0understand how we can solve the issues of bandwidth optimi=
zation and</font></div><div><font color=3D"#333333" face=3D"georgia, serif"=
>=C2=A0 =C2=A0performance on radio networks in this encrypted world.</font>=
</div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div=
><div><font color=3D"#333333" face=3D"georgia, serif">3. Section 1.1:</font=
></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></di=
v><div><font color=3D"#333333" face=3D"georgia, serif">Problem: The first p=
aragraph mixes business models with technical necessities. The last paragra=
ph in the section Understanding &quot;Bandwidth Optimization&quot; refers t=
o regulatory requirements (within the meaning of government enforced requir=
ements or legal requirements, cf above) on mobile network operators to perf=
orm traffic filtering and monitoring.</font></div><div><font color=3D"#3333=
33" face=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" f=
ace=3D"georgia, serif">Solution: It may facilitate understanding of human r=
ights impacts to separate technical considerations from business considerat=
ions and legal considerations. Paragraph 3 (&quot;Many of these functions c=
an continue...&quot;) could be put as the last paragraph, while Paragraph 1=
 could be split into a technical section and a business model section, foll=
owed by a legal section.</font></div><div><font color=3D"#333333" face=3D"g=
eorgia, serif"><br></font></div><div><font color=3D"#333333" face=3D"georgi=
a, serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, se=
rif">=C2=A0 =C2=A0For the purposes of this workshop, bandwidth optimization=
 encompasses</font></div><div><font color=3D"#333333" face=3D"georgia, seri=
f">=C2=A0 =C2=A0a variety of technical topics related to traffic engineerin=
g,</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =
=C2=A0prioritisation, optimisation and efficiency enhancements. It also enc=
ompasses</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=
=C2=A0 =C2=A0user-related topics such as specific subscription or billing m=
odels, and may touch upon regulatory aspects or other issues relating to re=
gulatory, within the meaning of government initiated, concerns.</font></div=
><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div=
><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0The first cat=
egory of bandwidth optimization includes:</font></div><div><font color=3D"#=
333333" face=3D"georgia, serif"><br></font></div><div><font color=3D"#33333=
3" face=3D"georgia, serif">=C2=A0 =C2=A0o=C2=A0 Caching</font></div><div><f=
ont color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font c=
olor=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0o=C2=A0 Prioritisatio=
n of interactive traffic over background traffic</font></div><div><font col=
or=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=3D=
"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0o=C2=A0 Per-user bandwidth l=
imit</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=
=A0 =C2=A0</font></div><div><font color=3D"#333333" face=3D"georgia, serif"=
>=C2=A0 =C2=A0The second category of bandwidth optimization may depend on e=
ither of the first category optimization strategies, but may, in particular=
, also encompass:</font></div><div><font color=3D"#333333" face=3D"georgia,=
 serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, seri=
f">=C2=A0 =C2=A0o=C2=A0 Business-related topics such as content delivery ar=
rangements with</font></div><div><font color=3D"#333333" face=3D"georgia, s=
erif">=C2=A0 =C2=A0 =C2=A0 specific content providers.</font></div><div><fo=
nt color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0 =C2=A0=C2=A0</fo=
nt></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0=
Finally, while not strictly speaking traffic management, some</font></div><=
div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0networks e=
mploy policy-based filtering (e.g., requested parental</font></div><div><fo=
nt color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0controls) and man=
y networks support some form of legal interception</font></div><div><font c=
olor=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0functionality per app=
licable laws.</font></div><div><font color=3D"#333333" face=3D"georgia, ser=
if"><br></font></div><div><font color=3D"#333333" face=3D"georgia, serif">=
=C2=A0 =C2=A0Many of these functions can continue as they&#39;re performed =
today, even</font></div><div><font color=3D"#333333" face=3D"georgia, serif=
">=C2=A0 =C2=A0with more encryption.=C2=A0 Others are using methods which i=
nspect parts</font></div><div><font color=3D"#333333" face=3D"georgia, seri=
f">=C2=A0 =C2=A0of the communication that are encrypted, and these will hav=
e to be</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=
=C2=A0 =C2=A0done differently in an encrypted Internet.</font></div><div><f=
ont color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font c=
olor=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=
=3D"#333333" face=3D"georgia, serif">4. Section 4:</font></div><div><font c=
olor=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=
=3D"#333333" face=3D"georgia, serif">Problem: QUIC is an active area of wor=
k for the IETF in the transport layer - this section barely mentions it, an=
d even then does so vaguely. What problems are solved by QUIC that are gene=
ral problems rather than TCP problems? What was the nature of the disagreem=
ent around this?</font></div><div><font color=3D"#333333" face=3D"georgia, =
serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, serif=
">Solution: More detail about how QUIC fits into transport-layer work would=
 make this section more relevant. In addition, there has been discussion in=
volving network operators around technical details that have potential priv=
acy impacts within the QUIC working group (SPIN bit); this section would be=
nefit greatly from an examination of that.</font></div></div></div></blockq=
uote><div><br></div></div></div><div>I have comments from two other reviewe=
rs asking that this document actually state the dates of the workshop, and =
I&#39;ll add that.=C2=A0</div><div><br></div><div>If the version of the dra=
ft you reviewed had included those dates, it would have been clearer that t=
he workshop happened in September 2015, which was more than a year before Q=
UIC was chartered (BOF in July 2016, chartered in October 2016).</div><div>=
<br></div><div>I&#39;m helping the IAB finish this report, so taking direct=
ion from them, but my understanding is that IAB workshop reports should ref=
lect the situation at the time of the workshop, so I shouldn&#39;t say much=
 about QUIC in the workshop report.=C2=A0</div><div><br></div><div>FWIW, I =
agree with you, but I&#39;m keeping that opinion out of the report ... and =
now you know why.</div><div><br></div><div>Spencer</div><div><br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div dir=3D"ltr"><div><span class=3D""><div><spa=
n style=3D"color:rgb(51,51,51);font-family:georgia,serif">Human Rights Cons=
iderations</span><br></div><div><font color=3D"#333333" face=3D"georgia, se=
rif">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D</font></div><div><font color=3D"#333333" face=3D"georgia, seri=
f"><br></font></div><div><font color=3D"#333333" face=3D"georgia, serif">Up=
on consideration of the draft report, no implications for internationalizat=
ion ([RFC8280], sec. 6.2.5), heterogeneity support ([RFC8280], sec. 6.2.8),=
 accessibility ([RFC8280], sec. 6.2.11) or localization ([RFC8280], sec. 6.=
2.12) have been found. We will further suppose that issues relating to Anon=
ymity ([RFC8280], sec. 6.2.9), Pseudonymity ([RFC8280], sec. 6.2.10) and Co=
nfidentiality ([RFC8280], sec. 6.2.16) have been sufficiently addressed in =
the draft as is.</font></div><div><font color=3D"#333333" face=3D"georgia, =
serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, serif=
">In the below text, Security ([RFC8280], sec. 6.2.4), Integrity ([RFC8280]=
, sec. 6.2.16) and Authenticity ([RFC8280], sec. 6.2.17) are further consid=
ered to have been addressed, or as in progress of being addressed by the sp=
ecific endeavours pointed out in the report. As such, this assessment hopes=
 to serve as a complement to remaining Human Rights Considerations Guidelin=
es which were not addressed by the MaRNEW draft.</font></div><div><font col=
or=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=3D=
"#333333" face=3D"georgia, serif">## Privacy ([RFC8280], sec. 6.2.2)</font>=
</div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div=
><div><font color=3D"#333333" face=3D"georgia, serif">We laud the general e=
mphasis on considering user privacy concerns paramount [Section 2.1.1, 2.3 =
etc].=C2=A0</font></div><div><font color=3D"#333333" face=3D"georgia, serif=
"><br></font></div><div><font color=3D"#333333" face=3D"georgia, serif">In =
Section 3.1.1, para 1, it would be useful to emphasize that middleboxes tha=
t are &quot;authenticated and invoked explicitly&quot; might not be very ef=
fective at conserving user privacy if they lead to auto-click through. In p=
ractice, &quot;opted-in&quot; middleboxes might not be much better than tra=
nsparent middleboxes. Additionally, this poses the danger of making matters=
 worse if users assume that because they haven&#39;t been asked for middleb=
ox permission, they are not going through a middlebox. For users accessing =
the Internet on a browser client: if the connection is MITMed by a middlebo=
x, the browser would somehow need to convey this effectively and actionably=
 to the user. Whatever effort is expended on this should involve browser ve=
ndors.</font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br=
></font></div></span><div><font color=3D"#333333" face=3D"georgia, serif">#=
# Connectivity ([RFC8280], sec. 6.2..1)</font></div><span class=3D""><div><=
font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font =
color=3D"#333333" face=3D"georgia, serif">It is a priori obvious that a dis=
cussion with mobile network operators would touch upon connectivity. As a g=
eneral comment, the HRPC RG is not concerned that encrypted internet traffi=
c could create topological problems in network deployment with respect to d=
ensity of base stations. It is more sensible to imagine that the density of=
 base stations is kept low by deployers to save money on infrastructure rol=
l-out.</font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br=
></font></div><div><font color=3D"#333333" face=3D"georgia, serif">In the M=
arNEW draft report, middleboxes are brought up frequently as an example of =
infrastructure rendered less useful by the ubiquitous adoption of encryptio=
n. Middleboxes may enhance access to content for individuals, and may also =
interfere with their ability to enjoy content free of surveillance, censors=
hip or content manipulation. The focus of the workshop of exploring ways in=
 which encrypted materials can benefit from the same speed of deliverance a=
s un-encrypted materials is therefore welcome.</font></div><div><font color=
=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=3D"#=
333333" face=3D"georgia, serif">## Content Agnosticism</font></div><div><fo=
nt color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font co=
lor=3D"#333333" face=3D"georgia, serif">Traffic prioritisation, whether bas=
ed on technical or commercial grounds, risks interfering with an individual=
&#39;s right to freedom of expression or opinion, by restricting access or =
enjoy content of their own choosing. As such, prioritisation should be made=
 explicit and obvious, and subject to consent from the individual, whether =
the motivations for deployment are commercial or technical.</font></div><di=
v><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><fo=
nt color=3D"#333333" face=3D"georgia, serif">It is clear that internet filt=
ering and blocking of content of specific types, whether motivated by netwo=
rk management or regulatory concerns, does not fulfill a content agnosticis=
m criterion. It is the observation of HRPC that [RFC7725] (An HTTP Status C=
ode to Report Legal Obstacles) may assist communication of specific filteri=
ng and blocking operations in action.</font></div><div><font color=3D"#3333=
33" face=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" f=
ace=3D"georgia, serif">It the the impetus of the Human Rights Guidelines in=
 RFC8280 that content agnosticism be respected by protocols developed in th=
e IETF, and in general an accepted view in the global human rights communit=
y that content agnosticism is desirable at all levels of technical infrastr=
ucture. As such, the HRPC RG is concerned about ideas that traffic be class=
ified through additional headers or metadata, identifying traffic via 5-tup=
les, trust models and frameworks, or heuristics.</font></div><div><br></div=
></span></div><div style=3D"color:rgb(51,51,51);font-family:georgia,serif;f=
ont-size:small"><br><br></div></div>
<br>______________________________<wbr>_________________<br>
Architecture-discuss mailing list<br>
<a href=3D"mailto:Architecture-discuss@ietf.org" target=3D"_blank">Architec=
ture-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/architecture-discuss" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinf=
o/architecture-discuss</a><br>
<br></blockquote></div><br></div></div>
</blockquote></div><br></div>

--00000000000096daea056b542786--


From nobody Mon May  7 07:27:28 2018
Return-Path: <shivankaul.1993@gmail.com>
X-Original-To: hr-rt@ietfa.amsl.com
Delivered-To: hr-rt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEE0E126C22 for <hr-rt@ietfa.amsl.com>; Mon,  7 May 2018 07:27:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 iuxndzCKRZEX for <hr-rt@ietfa.amsl.com>; Mon,  7 May 2018 07:27:26 -0700 (PDT)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (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 08041126C26 for <hr-rt@irtf.org>; Mon,  7 May 2018 07:27:25 -0700 (PDT)
Received: by mail-lf0-x22e.google.com with SMTP id r2-v6so4780681lff.4 for <hr-rt@irtf.org>; Mon, 07 May 2018 07:27:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=+7fa/OWwkjzF5YbgJBp2sds+WO3YMOIaLa2zKNUi7WQ=; b=j7CzWrhEwBgdS5GrRk5oE+77RXPPAz7BELTCrAt1sr7n4rionO37seiWLXPfb5Js2i ZrKosB28beHz6YUMkbZ/vYLYUy5ZPVGL6B2FNI2jGk8cRCJ48FIurTVZ/NOVXz/MbwZo UorZMt3qyCULv/B5JiJR3tWtkJi+a+kpbAM3V6aPkihkopOgwAQfkh7HdHmzDuq6ZLkF dywzbJH1xm1dV90bAQV0w8l053+AU8tieKREmbUIc3GFUCabDOa7ofJE7b1RSBgkgrDK /25sPXw1ImDve8Sog+oNrQhnS/5PgqP5kkIWVO+YPd0MEwid6skV+99cVnyPOFhaLIfE OItA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=+7fa/OWwkjzF5YbgJBp2sds+WO3YMOIaLa2zKNUi7WQ=; b=Boncq8dgrUT1IeQUG68wp/cKK/VMYybJK8cO3FusfQ/4l8neuJoTiG/wzR8YfufcCE lygFKnThMdAXRzgc2n1ZnwlpJkXHTMEvK7ESruEkwwofZMuilmIO5wpyqINOtgAZo5yc gEmHPVWpFtGYMQAAGWX7nEqURBqqn8Kvh6F0VqPpv+8h2NFutlx3F+v9CO7/eh/sOvhz Nrvzzqs1L6S4Y/mp4b9SsFO2keVPk5CIRKl16vXrNAzpkPpF2vSYq5Lfve56jgmTwgNv grHC1pZug7TrwejpNWMPVvIL8xjKT6pqAI9A4Fl2wAE563pXnNCPelo17dYFWmLQ2Kz0 NwRg==
X-Gm-Message-State: ALQs6tAaDwwx6AcqvMpVWxgpojv6jf6gFTTt5gM0KsodVwOWFmdVH671 iM51oBUfvKS+WcFnjLuChR9QVCrEgWDfnQ43K0U=
X-Google-Smtp-Source: AB8JxZptnPSrsT6cdXG1CeL6yYebyOvEE2iRU1xILej2aCywp5jyXQwkD+0bKOb7b8Ia0kn26sfY3s71elp1y1gPc+w=
X-Received: by 2002:a2e:4d5d:: with SMTP id a90-v6mr8147960ljb.86.1525703243724;  Mon, 07 May 2018 07:27:23 -0700 (PDT)
MIME-Version: 1.0
From: Shivan <shivankaul.1993@gmail.com>
Date: Mon, 07 May 2018 14:27:12 +0000
Message-ID: <CAG3f7MgRkJc273D-Zv-T4AhC8nN2w6C2zpp5DTuKcroDpGEYhQ@mail.gmail.com>
To: "hr-rt@irtf.org" <hr-rt@irtf.org>
Content-Type: multipart/alternative; boundary="000000000000e00578056b9e777f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/sSBBxKalaesNhRyosBJ6YnDks90>
Subject: [HT-rt] Gitlab project for human Rights review team
X-BeenThere: hr-rt@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Human Rights Protocol Considerations Review Team <hr-rt.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hr-rt/>
List-Post: <mailto:hr-rt@irtf.org>
List-Help: <mailto:hr-rt-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2018 14:27:28 -0000

--000000000000e00578056b9e777f
Content-Type: text/plain; charset="UTF-8"

Hi all, I set up a gitlab project:
https://gitlab.com/ShivanKaul/HR-RT

I uploaded the two analyses that have taken place so far. To suggest a new
draft/RFC for analysis, feel free to create a new issue using the
Suggested-Draft template - I used Mallory's proposed template.

If anyone would like to be made moderator, please let me know your gitlab
username/email.

--000000000000e00578056b9e777f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hi all, I set up a gitlab project:=C2=A0<div><a href=3D"h=
ttps://gitlab.com/ShivanKaul/HR-RT">https://gitlab.com/ShivanKaul/HR-RT</a>=
</div><div dir=3D"auto"><br></div><div dir=3D"auto">I uploaded the two anal=
yses that have taken place so far. To suggest a new draft/RFC for analysis,=
 feel free to create a new issue using the Suggested-Draft template - I use=
d Mallory&#39;s proposed template.=C2=A0</div><div dir=3D"auto"><br></div><=
div dir=3D"auto">If anyone would like to be made moderator, please let me k=
now your gitlab username/email.=C2=A0</div></div>

--000000000000e00578056b9e777f--


From nobody Mon May  7 07:41:20 2018
Return-Path: <mail@nielstenoever.net>
X-Original-To: hr-rt@ietfa.amsl.com
Delivered-To: hr-rt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1DF6126C26 for <hr-rt@ietfa.amsl.com>; Mon,  7 May 2018 07:41:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 9HM2zjxETR4k for <hr-rt@ietfa.amsl.com>; Mon,  7 May 2018 07:41:12 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (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 D58A1126C22 for <hr-rt@irtf.org>; Mon,  7 May 2018 07:41:10 -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 1fFhK8-0005Yj-0b for hr-rt@irtf.org; Mon, 07 May 2018 16:41:08 +0200
To: hr-rt@irtf.org
References: <CAG3f7MgRkJc273D-Zv-T4AhC8nN2w6C2zpp5DTuKcroDpGEYhQ@mail.gmail.com>
From: Niels ten Oever <mail@nielstenoever.net>
Openpgp: preference=signencrypt
Autocrypt: addr=mail@nielstenoever.net; prefer-encrypt=mutual; keydata= xsFNBFgpcR0BEACnfvNwTMlN+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 5mrXMaKvfszqAVkP9HSrk1QVZOipF6vEimL43Czy7Rp1aUaUwwARAQABzSVOaWVscyB0ZW4g T2V2ZXIgPG5pZWxzQGFydGljbGUxOS5vcmc+wsGZBBMBCABDAhsjBQkJZgGABwsJCAcDAgEG FQgCCQoLBBYCAwECHgECF4AWIQQkWAtwXEr9ipSIZDoO2D86RorIswUCWG0tCwIZAQAKCRAO 2D86RorIs3pMD/9W/Tww1uLG0m0jQkBV3TmBOVzS79fVyoj6lEYCNPJigCqOi9wbZSTB2HL6 h4ftSCl4ErGHcIqngRPcNRt7G8/3OoA1h6qRHcqrpS6H4niW1E+rtxIxul+PSsXXZEgDyUSK XXczf4MmRbR6tKGY4hp4KFedSOEL2C0j8htB2um4C8KFyX4gAYMPJoBfZqlrCmXsyLjdjIvN wd7FLLKA6CNVjwYsDgmKiLQm0Np4fz1AW72rnGGktyUT3u0GsbyDmwM6YU80anh647Pc7cyo ie6c21Ajcph1k7BjHAB/EopQzoQVporHFrCNqhpgVXihhlVDGdOD1JSHCgWO4toflJAT6+kP 3uOXeHv6AoLcXKnY/8QWFjwoj9DYtpw4bSsiP++sF3Dg0xaaivvOzU5+IBoSxNTnqj0M7/Fk jergVF60QdwMGukFZDMSjFnX/gvFPbxy4JebvrfzSY5ZJxLjrlswSeVkWTU1DvtfJxJHKTPQ 9dnodrSN3vynJS+u+wRbzQLdSLBgSgGbUVVHu2dyJhXGPwoh/2Gu4gFilV6+dBhcwHwuxlsd 0pdnTdq4wJodT1rDZRgP3QjR+miyFqjahUDMTJlf4BRq6CiWiHb5UfvQvUsPtMLfQafqYCEy 98b4RHnbckPXa+pXRTYz3z9CBuiJTQWTT0CIBVLhyzqQjYrFTM7BTQRYKXEdARAAxYOE3/AF mEfQ0SVVFujYFhZKX+BGXolYytC2a1soZogVYTIIlypxkRtN+ljteFAY3xX/El7cx5Fxj+uX vLKAm9xQRI/DCug7/NGULMk9bDK5bzSGw817cyiL5Kb+0RkWj2Y5ArOAK6XPGBZWZTHwyIaw sSCN9AhDXZQWVRqkR1QXcq3IYKl+OHWMO7+1VfixCSakNf7T/Kiq46rQEPW8Eghk6CVOBR8x UCBbyk5aRW4VSGO6pUD3H21ur+5fTLsVyan1NHhxNNiXfnEJKr+JI5dXSkj7WqA5n8ITaNdF SAttkdT56wAQpxE2h8zaOmBaFUWQ4D8SdXDVymP5QMtLG+ItMMiNV6kXgsRFugAKM5yZtPP9 gIX+ic8QO5iuct37bRXJU/rmrH54Ab0kyAeeRE7oSsfTZPKvgtUh7VLAUEw/wy6TORJHE8JM aX0yYT6h4PGRS3mNM4bka8hjdfcrexI0zSqFOl2I22zQlG3YqSzIvVh98W67hxfAIaCVaTfJ LFPEru3drxNwi6ogdkRmcLGKqqTgeYItrvITyFvzqbrcO2exp0KKEK3cDIZypqHHUf4+uPlD tuExehLsNOMpjP8qhZpFtyLeDS07qunbvstcyvR30wOJ3DyAbHGzq739UyDcO9Jt5jwODyVw k3MK5Em4pJ0+IAJx+F6gta0Bk2MAEQEAAcLBZQQYAQgADwUCWClxHQIbDAUJCWYBgAAKCRAO 2D86RorIs0ykD/4t151SZG9MbeKRVKbs9Ecjady9bO0L3oBos4rhqY12ha8smFlsUzvbgB4C tkBuXQlq+plOBWv+rFEThOzy3bezgEDjlxycoO1W2wJD6E7Fo9fkHT6UOm9fQBkuKRqK83OG nfM02qP1Ky8d7EoZz+nTSMf/DJgWw1YRKrXkMHBwKD83lCENsmePWE5AjMqk8cojPv9Oy1wW y6fHjwx3r+wQSokBNfxgQyAFonmgBbhlic/pZUYRSIcldyUlaomrjFfr4egzmNE7aWDvLwOU YKevBIeJJcqTyfAn3TtJbPCEHOC2+lP6EcmPFyhQdiia+RqOClumqbWOPeQ2VM8j7NWvKKmB NBB5OJ/rmHogbNU+wWPJ723qMBoOp1jIwFNkQhx01W6v55VMwLr+IuBKY1ggJ2BhwQiGpWv4 tMc5oB/qVh3my1VO65ErcJ3S9blpwJdDj5/YDOU7BKEmpRUP+xkaryNzH2x7FzrOOHzJBX6j eYZabGvnTicQlBAzfGpblFqV3YN6EhCF2AHmGLTZ/DrjGYToIsW8cXlEMqN4u8ODEUY0Ohbn ytnopKJKk99bwMoCqDkfQvT3LKDWtZj9NzFndfuoKXsVpwAitrG0mau0/16DKDyVWdtJ9DYm tE40zO6g70VVxUj+dKt2hbJTy/KQTb7Ijhw7wZrGp/P7nhbVyA==
Message-ID: <9f4e7a16-696e-70ec-bfb9-d364d7ec389a@nielstenoever.net>
Date: Mon, 7 May 2018 16:40:52 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <CAG3f7MgRkJc273D-Zv-T4AhC8nN2w6C2zpp5DTuKcroDpGEYhQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
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: a350ae07b5350cdad28cef237d2e7179
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/mQzr_rs9S7KCrfA0119tMf_ojEE>
Subject: Re: [HT-rt] Gitlab project for human Rights review team
X-BeenThere: hr-rt@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Human Rights Protocol Considerations Review Team <hr-rt.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hr-rt/>
List-Post: <mailto:hr-rt@irtf.org>
List-Help: <mailto:hr-rt-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2018 14:41:19 -0000

Hi Shivan,

I have been hitting myself since the beginning of HRPC that I setup the
RG repo under my name instead of setting up a sepate organization (ie
not connected one specific user). Is this also possible on GitLab perhaps?

Does Gitlab also offer a wiki where we can keep track of things? Or
shall we all do that in the README.md file?

Cheers,

Niels

On 05/07/2018 04:27 PM, Shivan wrote:
> Hi all, I set up a gitlab project: 
> https://gitlab.com/ShivanKaul/HR-RT
> 
> I uploaded the two analyses that have taken place so far. To suggest a
> new draft/RFC for analysis, feel free to create a new issue using the
> Suggested-Draft template - I used Mallory's proposed template. 
> 
> If anyone would like to be made moderator, please let me know your
> gitlab username/email. 
> 
> 
> _______________________________________________
> HR-rt mailing list
> HR-rt@irtf.org
> https://www.irtf.org/mailman/listinfo/hr-rt
> 


From nobody Mon May  7 08:05:36 2018
Return-Path: <shivankaul.1993@gmail.com>
X-Original-To: hr-rt@ietfa.amsl.com
Delivered-To: hr-rt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58DA6126CD6 for <hr-rt@ietfa.amsl.com>; Mon,  7 May 2018 08:05:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 tZVg9bj9oHmY for <hr-rt@ietfa.amsl.com>; Mon,  7 May 2018 08:05:32 -0700 (PDT)
Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (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 DCDAD126CB6 for <hr-rt@irtf.org>; Mon,  7 May 2018 08:05:31 -0700 (PDT)
Received: by mail-lf0-x230.google.com with SMTP id g12-v6so41105092lfb.10 for <hr-rt@irtf.org>; Mon, 07 May 2018 08:05:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ziO/L70L33ZOAil5eBz700Tmnopp/M2lQpxnaDAdjL0=; b=UhVWOsyagF0F+hR4hXUyTNqzUyuhMrxtTc/wm15sdkzdX+p9d2rDCxNtFWpFYzQkxh AMmWe0delVInIKv86uVy0b/659nnIBD18U/GHCnFuASPjmFwQ+sECZW2BTCMUC/s9KEi HoZN9dm+575qDNm4OJNsIzRYc7O2DFfViSeBf2e3Oaen+/Rv5X1VvL1byZlNVYP0BKQQ pdQhIikfKc00d4l26cGjJo7JR6GIA1H2QZZNLNL07BTRJ5zWwKT4DhDNIj5MgmsDuqjO b8nFNDv3ANYXt04OFNK6p7WIEpBSXCLsTkbmJshK0MaRSP8N8jpQSpcJS1ifAs4npZqk ECjg==
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=ziO/L70L33ZOAil5eBz700Tmnopp/M2lQpxnaDAdjL0=; b=OCAshyornAEcN280KnXYi1Y69CleVtPp5Axd279p5v77ww0Q5AxjAqVC7Lpc8qldiR bzkJGPD/oiWkTtZ08ytC64/9cgc659JUchht2ywaUOzadVL5sEJpjrkX6urcFOO5EtfY QR1CD/qo5e7wEtXlC5Xbu7Hy5zAFXbjj0JJI/4kLnlFdEu9Vbf6kudpRB1WicSs+WTrP J5lZH1Sx2l5vHPOPUh+pTmrGtAFFXbJ2BLlliVZnoOCUaBMWqbU7WDU7RFi6xtL6toiO WYMR0EZmwcO5GwHCoCD2CUpnHIoevmyqgrH/8zS4vmGmM4sUvG2lsLQmNrKi6x3QNrax LmSg==
X-Gm-Message-State: ALQs6tChRPV+qSLM64oyEYybjJMHM6Ljpv37wCdyLnSgK1KMkjbdbtLA UBXt9TCRSSuqDiiRoJwnMWMhGAnawL0s10ITPKE=
X-Google-Smtp-Source: AB8JxZq1CVTcQHybKuDwdYGhGtkyba4zcHTd+W1apbIebgqtmUR1dL9KuKqp5FtkgdfZ45MTo/BURorYBziS0WYyqHs=
X-Received: by 2002:a19:5348:: with SMTP id h69-v6mr25233394lfb.26.1525705530023;  Mon, 07 May 2018 08:05:30 -0700 (PDT)
MIME-Version: 1.0
References: <CAG3f7MgRkJc273D-Zv-T4AhC8nN2w6C2zpp5DTuKcroDpGEYhQ@mail.gmail.com> <9f4e7a16-696e-70ec-bfb9-d364d7ec389a@nielstenoever.net>
In-Reply-To: <9f4e7a16-696e-70ec-bfb9-d364d7ec389a@nielstenoever.net>
From: Shivan <shivankaul.1993@gmail.com>
Date: Mon, 07 May 2018 15:05:19 +0000
Message-ID: <CAG3f7Mg-762NLd4eYaYVV2f3wMUHZOUTikYAL60dLuXx8YU4og@mail.gmail.com>
To: Niels ten Oever <mail@nielstenoever.net>
Cc: hr-rt@irtf.org
Content-Type: multipart/alternative; boundary="00000000000026290b056b9f00d9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/nN7biy-SHPfNKXyNLyAfnQJTbCo>
Subject: Re: [HT-rt] Gitlab project for human Rights review team
X-BeenThere: hr-rt@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Human Rights Protocol Considerations Review Team <hr-rt.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hr-rt/>
List-Post: <mailto:hr-rt@irtf.org>
List-Help: <mailto:hr-rt-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2018 15:05:34 -0000

--00000000000026290b056b9f00d9
Content-Type: text/plain; charset="UTF-8"

I think so? I'm not really familiar with Gitlab but I'd imagine it has
that. I'll take a look. We could also set it up under 0xacab as Mallory
suggested.

Yes they do offer a wiki! Do people prefer that over a readme? Most GitHub
projects I've seen generally just kept everything in their READMEs. The
advantage is that you have everything you want to know about the project on
the landing page instead of having to be further redirected. If there's not
much project description then just using a README is better imo but either
works.

On Mon, May 7, 2018 at 10:41 AM Niels ten Oever <mail@nielstenoever.net>
wrote:

> Hi Shivan,
>
> I have been hitting myself since the beginning of HRPC that I setup the
> RG repo under my name instead of setting up a sepate organization (ie
> not connected one specific user). Is this also possible on GitLab perhaps?
>
> Does Gitlab also offer a wiki where we can keep track of things? Or
> shall we all do that in the README.md file?
>
> Cheers,
>
> Niels
>
> On 05/07/2018 04:27 PM, Shivan wrote:
> > Hi all, I set up a gitlab project:
> > https://gitlab.com/ShivanKaul/HR-RT
> >
> > I uploaded the two analyses that have taken place so far. To suggest a
> > new draft/RFC for analysis, feel free to create a new issue using the
> > Suggested-Draft template - I used Mallory's proposed template.
> >
> > If anyone would like to be made moderator, please let me know your
> > gitlab username/email.
> >
> >
> > _______________________________________________
> > HR-rt mailing list
> > HR-rt@irtf.org
> > https://www.irtf.org/mailman/listinfo/hr-rt
> >
>
> _______________________________________________
> HR-rt mailing list
> HR-rt@irtf.org
> https://www.irtf.org/mailman/listinfo/hr-rt
>

--00000000000026290b056b9f00d9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><div dir=3D"auto">I think so? I&#39;m not really familiar with Gitlab =
but I&#39;d imagine it has that. I&#39;ll take a look. We could also set it=
 up under 0xacab as Mallory suggested.=C2=A0</div><div dir=3D"auto"><br></d=
iv><div dir=3D"auto">Yes they do offer a wiki! Do people prefer that over a=
 readme? Most GitHub projects I&#39;ve seen generally just kept everything =
in their READMEs. The advantage is that you have everything you want to kno=
w about the project on the landing page instead of having to be further red=
irected. If there&#39;s not much project description then just using a READ=
ME is better imo but either works.=C2=A0</div><br><div class=3D"gmail_quote=
"><div>On Mon, May 7, 2018 at 10:41 AM Niels ten Oever &lt;<a href=3D"mailt=
o:mail@nielstenoever.net">mail@nielstenoever.net</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">Hi Shivan,<br>
<br>
I have been hitting myself since the beginning of HRPC that I setup the<br>
RG repo under my name instead of setting up a sepate organization (ie<br>
not connected one specific user). Is this also possible on GitLab perhaps?<=
br>
<br>
Does Gitlab also offer a wiki where we can keep track of things? Or<br>
shall we all do that in the README.md file?<br>
<br>
Cheers,<br>
<br>
Niels<br>
<br>
On 05/07/2018 04:27 PM, Shivan wrote:<br>
&gt; Hi all, I set up a gitlab project:=C2=A0<br>
&gt; <a href=3D"https://gitlab.com/ShivanKaul/HR-RT" rel=3D"noreferrer" tar=
get=3D"_blank">https://gitlab.com/ShivanKaul/HR-RT</a><br>
&gt; <br>
&gt; I uploaded the two analyses that have taken place so far. To suggest a=
<br>
&gt; new draft/RFC for analysis, feel free to create a new issue using the<=
br>
&gt; Suggested-Draft template - I used Mallory&#39;s proposed template.=C2=
=A0<br>
&gt; <br>
&gt; If anyone would like to be made moderator, please let me know your<br>
&gt; gitlab username/email.=C2=A0<br>
&gt; <br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; HR-rt mailing list<br>
&gt; <a href=3D"mailto:HR-rt@irtf.org" target=3D"_blank">HR-rt@irtf.org</a>=
<br>
&gt; <a href=3D"https://www.irtf.org/mailman/listinfo/hr-rt" rel=3D"norefer=
rer" target=3D"_blank">https://www.irtf.org/mailman/listinfo/hr-rt</a><br>
&gt; <br>
<br>
_______________________________________________<br>
HR-rt mailing list<br>
<a href=3D"mailto:HR-rt@irtf.org" target=3D"_blank">HR-rt@irtf.org</a><br>
<a href=3D"https://www.irtf.org/mailman/listinfo/hr-rt" rel=3D"noreferrer" =
target=3D"_blank">https://www.irtf.org/mailman/listinfo/hr-rt</a><br>
</blockquote></div></div>

--00000000000026290b056b9f00d9--


From nobody Mon May  7 17:57:24 2018
Return-Path: <shivankaul.1993@gmail.com>
X-Original-To: hr-rt@ietfa.amsl.com
Delivered-To: hr-rt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC9CE12D86C for <hr-rt@ietfa.amsl.com>; Mon,  7 May 2018 17:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9VgxWoHoBSwT for <hr-rt@ietfa.amsl.com>; Mon,  7 May 2018 17:57:20 -0700 (PDT)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (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 00F95129C70 for <hr-rt@irtf.org>; Mon,  7 May 2018 17:57:19 -0700 (PDT)
Received: by mail-lf0-x22a.google.com with SMTP id g12-v6so43288995lfb.10 for <hr-rt@irtf.org>; Mon, 07 May 2018 17:57:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=VMe0xm1qeMi8Q+Vlipca53+QVdPM0sJO5Uw+iaDDaQ0=; b=HYENhOGV6ekfJ1Vh2K8Ocx9LHIN1+4qoDAYO4hsi8Z4n2RDS3IfHcin0YwutKdqsA2 PqvLheJ2yF2jCLBDqkR8AMcT75tkss40cedzIan8A0+0KX31RlTLCiH4Wv5HpQCdrkEy oOUUNX+i1HicsoxzUu6zkp/uQ5zjJiQEJdBTGSpnToWgX/XRGGxDt6Zo7tnxeT2pt+bI JKKXjZ84ZcUNHwMcJRxkFnfSnVP+aKao8Qs6RniH+92bkSHWkK78IpLLzyrrQWVDU08y PpoXzr4PH71pxoDhGTITStkAAQnEdJV7H+wOK4OnyXI7RC26Rm1dpeb+VSDUD3hXjvIL 0njw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=VMe0xm1qeMi8Q+Vlipca53+QVdPM0sJO5Uw+iaDDaQ0=; b=HC10Wc+4id1BqVDObnRCLV24iOGmTWvX9NeNO5czLAqelbx9ay8r5bnzJygYJlF9Q1 Hx5FV4za5sZPz3+hUjlN9/bqD9OYv4PvMUPcr+vhbb0hORPePxFkt1T+BH0H0tWR0fkC p1Hu6nCByYnuZKVwRf4PoJvu27xUxUDYzQI0gk/t++56IJeMI0K7BnwBVedPbBPvCMMN Ljz7F27DLkqt3v0Um3olqjIaYw2b93AFtX0j6XjbaWAhqxgbE4fidbT9cZ4TypZFQiQa UbRGCiK/JhfznpoE0BYTa94CM5CH6MNpTGjbpxaY7aMjmef+09+tm56iTboN932guvmK 3Xnw==
X-Gm-Message-State: ALKqPwe6cCJYCcdbo3HNa1iDeYu0ybFe2UWJZecrS/5IZl7UN9+0LPMo OAUu638LI4/5Z511m/qHMjJtyJwKjuYjg3EPS1h4lQ==
X-Google-Smtp-Source: AB8JxZov9tXLS0Tq3AqQ/Fw8A2LwikvkZFUUXOV1qOLrg4yDwSangO00+lwScWInPhRkAZV8EmdKPUHeavXYwvuqZdc=
X-Received: by 2002:a19:1498:: with SMTP id 24-v6mr6889134lfu.128.1525741037929;  Mon, 07 May 2018 17:57:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.144.3 with HTTP; Mon, 7 May 2018 17:56:37 -0700 (PDT)
In-Reply-To: <CAG3f7Mg-762NLd4eYaYVV2f3wMUHZOUTikYAL60dLuXx8YU4og@mail.gmail.com>
References: <CAG3f7MgRkJc273D-Zv-T4AhC8nN2w6C2zpp5DTuKcroDpGEYhQ@mail.gmail.com> <9f4e7a16-696e-70ec-bfb9-d364d7ec389a@nielstenoever.net> <CAG3f7Mg-762NLd4eYaYVV2f3wMUHZOUTikYAL60dLuXx8YU4og@mail.gmail.com>
From: Shivan <shivankaul.1993@gmail.com>
Date: Mon, 7 May 2018 20:56:37 -0400
Message-ID: <CAG3f7MjRGZf3D8R_n_cNNUGREUHtptQzRKHjcB2Ey=Kswh0F3w@mail.gmail.com>
To: Niels ten Oever <mail@nielstenoever.net>
Cc: hr-rt@irtf.org
Content-Type: multipart/alternative; boundary="00000000000095caba056ba744e4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/ZqyD5yraKLoD_UyXpWUAjxJ7kWg>
Subject: Re: [HT-rt] Gitlab project for human Rights review team
X-BeenThere: hr-rt@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Human Rights Protocol Considerations Review Team <hr-rt.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hr-rt/>
List-Post: <mailto:hr-rt@irtf.org>
List-Help: <mailto:hr-rt-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2018 00:57:23 -0000

--00000000000095caba056ba744e4
Content-Type: text/plain; charset="UTF-8"

Okay I set up a GitLab "group" (similar to a GitHub org) for HR-RT with a
"project" (similar to GitHub repo) called Documents. I've invited Niels and
Mallory to be admins - again, if anyone else wants to be, lmk.

https://gitlab.com/hr-rt

On Mon, May 7, 2018 at 11:05 AM, Shivan <shivankaul.1993@gmail.com> wrote:

> I think so? I'm not really familiar with Gitlab but I'd imagine it has
> that. I'll take a look. We could also set it up under 0xacab as Mallory
> suggested.
>
> Yes they do offer a wiki! Do people prefer that over a readme? Most GitHub
> projects I've seen generally just kept everything in their READMEs. The
> advantage is that you have everything you want to know about the project on
> the landing page instead of having to be further redirected. If there's not
> much project description then just using a README is better imo but either
> works.
>
> On Mon, May 7, 2018 at 10:41 AM Niels ten Oever <mail@nielstenoever.net>
> wrote:
>
>> Hi Shivan,
>>
>> I have been hitting myself since the beginning of HRPC that I setup the
>> RG repo under my name instead of setting up a sepate organization (ie
>> not connected one specific user). Is this also possible on GitLab perhaps?
>>
>> Does Gitlab also offer a wiki where we can keep track of things? Or
>> shall we all do that in the README.md file?
>>
>> Cheers,
>>
>> Niels
>>
>> On 05/07/2018 04:27 PM, Shivan wrote:
>> > Hi all, I set up a gitlab project:
>> > https://gitlab.com/ShivanKaul/HR-RT
>> >
>> > I uploaded the two analyses that have taken place so far. To suggest a
>> > new draft/RFC for analysis, feel free to create a new issue using the
>> > Suggested-Draft template - I used Mallory's proposed template.
>> >
>> > If anyone would like to be made moderator, please let me know your
>> > gitlab username/email.
>> >
>> >
>> > _______________________________________________
>> > HR-rt mailing list
>> > HR-rt@irtf.org
>> > https://www.irtf.org/mailman/listinfo/hr-rt
>> >
>>
>> _______________________________________________
>> HR-rt mailing list
>> HR-rt@irtf.org
>> https://www.irtf.org/mailman/listinfo/hr-rt
>>
>

--00000000000095caba056ba744e4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:georgia,=
serif;font-size:small;color:rgb(51,51,51)">Okay I set up a GitLab &quot;gro=
up&quot; (similar to a GitHub org) for HR-RT with a &quot;project&quot; (si=
milar to GitHub repo) called Documents. I&#39;ve invited Niels and Mallory =
to be admins - again, if anyone else wants to be, lmk.=C2=A0</div><div clas=
s=3D"gmail_default" style=3D"font-family:georgia,serif;font-size:small;colo=
r:rgb(51,51,51)"><br></div><div class=3D"gmail_default"><font color=3D"#333=
333" face=3D"georgia, serif"><a href=3D"https://gitlab.com/hr-rt">https://g=
itlab.com/hr-rt</a></font><br></div></div><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On Mon, May 7, 2018 at 11:05 AM, Shivan <span dir=
=3D"ltr">&lt;<a href=3D"mailto:shivankaul.1993@gmail.com" target=3D"_blank"=
>shivankaul.1993@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><div><div dir=3D"auto">I think so? I&#39;m not really familiar with=
 Gitlab but I&#39;d imagine it has that. I&#39;ll take a look. We could als=
o set it up under 0xacab as Mallory suggested.=C2=A0</div><div dir=3D"auto"=
><br></div><div dir=3D"auto">Yes they do offer a wiki! Do people prefer tha=
t over a readme? Most GitHub projects I&#39;ve seen generally just kept eve=
rything in their READMEs. The advantage is that you have everything you wan=
t to know about the project on the landing page instead of having to be fur=
ther redirected. If there&#39;s not much project description then just usin=
g a README is better imo but either works.=C2=A0</div><div><div class=3D"h5=
"><br><div class=3D"gmail_quote"><div>On Mon, May 7, 2018 at 10:41 AM Niels=
 ten Oever &lt;<a href=3D"mailto:mail@nielstenoever.net" target=3D"_blank">=
mail@nielstenoever.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">Hi Shivan,<br>
<br>
I have been hitting myself since the beginning of HRPC that I setup the<br>
RG repo under my name instead of setting up a sepate organization (ie<br>
not connected one specific user). Is this also possible on GitLab perhaps?<=
br>
<br>
Does Gitlab also offer a wiki where we can keep track of things? Or<br>
shall we all do that in the README.md file?<br>
<br>
Cheers,<br>
<br>
Niels<br>
<br>
On 05/07/2018 04:27 PM, Shivan wrote:<br>
&gt; Hi all, I set up a gitlab project:=C2=A0<br>
&gt; <a href=3D"https://gitlab.com/ShivanKaul/HR-RT" rel=3D"noreferrer" tar=
get=3D"_blank">https://gitlab.com/ShivanKaul/<wbr>HR-RT</a><br>
&gt; <br>
&gt; I uploaded the two analyses that have taken place so far. To suggest a=
<br>
&gt; new draft/RFC for analysis, feel free to create a new issue using the<=
br>
&gt; Suggested-Draft template - I used Mallory&#39;s proposed template.=C2=
=A0<br>
&gt; <br>
&gt; If anyone would like to be made moderator, please let me know your<br>
&gt; gitlab username/email.=C2=A0<br>
&gt; <br>
&gt; <br>
&gt; ______________________________<wbr>_________________<br>
&gt; HR-rt mailing list<br>
&gt; <a href=3D"mailto:HR-rt@irtf.org" target=3D"_blank">HR-rt@irtf.org</a>=
<br>
&gt; <a href=3D"https://www.irtf.org/mailman/listinfo/hr-rt" rel=3D"norefer=
rer" target=3D"_blank">https://www.irtf.org/mailman/<wbr>listinfo/hr-rt</a>=
<br>
&gt; <br>
<br>
______________________________<wbr>_________________<br>
HR-rt mailing list<br>
<a href=3D"mailto:HR-rt@irtf.org" target=3D"_blank">HR-rt@irtf.org</a><br>
<a href=3D"https://www.irtf.org/mailman/listinfo/hr-rt" rel=3D"noreferrer" =
target=3D"_blank">https://www.irtf.org/mailman/<wbr>listinfo/hr-rt</a><br>
</blockquote></div></div></div></div></blockquote></div><br></div>

--00000000000095caba056ba744e4--


From nobody Thu May 10 03:19:54 2018
Return-Path: <mallory@article19.org>
X-Original-To: hr-rt@ietfa.amsl.com
Delivered-To: hr-rt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF5C91205F0 for <hr-rt@ietfa.amsl.com>; Thu, 10 May 2018 03:19:52 -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 XhwhqLEXeHYE for <hr-rt@ietfa.amsl.com>; Thu, 10 May 2018 03:19:50 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (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 9050B127286 for <hr-rt@irtf.org>; Thu, 10 May 2018 03:19:49 -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 <mallory@article19.org>) id 1fGifq-0001iE-I4 for hr-rt@irtf.org; Thu, 10 May 2018 12:19:48 +0200
To: hr-rt@irtf.org
References: <CAG3f7MgRkJc273D-Zv-T4AhC8nN2w6C2zpp5DTuKcroDpGEYhQ@mail.gmail.com> <9f4e7a16-696e-70ec-bfb9-d364d7ec389a@nielstenoever.net> <CAG3f7Mg-762NLd4eYaYVV2f3wMUHZOUTikYAL60dLuXx8YU4og@mail.gmail.com> <CAG3f7MjRGZf3D8R_n_cNNUGREUHtptQzRKHjcB2Ey=Kswh0F3w@mail.gmail.com>
From: Mallory Knodel <mallory@article19.org>
Openpgp: preference=signencrypt
Autocrypt: addr=mallory@article19.org; prefer-encrypt=mutual; keydata= xsBNBEx0TWcBCAC8sirY3nlDnRwY6XWmsvZtM9kmEK6H8no3ZuQ723PKwHOddw1nOykh0in/ /QGRmwtyVzsfLh6/94UUZTn10oo+xGAfw2gf1on5IJTIiphykk732PNnUakVGWwHNKQquTVc kLrydUaFVMb89BAXqExBKlMg2ciEjzbYMCs3I/qZAZ0Wr5nF3RQS8O78elTNAgWTZ98yKTZV DlRoDpnvbfwtIPqnISoSjDEvEUBdpykvS3jHqlR1f6Mx6Xs97S5CORaer/0qTcDm0PAb1Z9l IhMsFl05tNt2FpgS4/RN8NyLasAQNOlScpTJbAfRuyyvRm1N8GLIL1KX+YYeLyqzhdhZABEB AAHNJU1hbGxvcnkgS25vZGVsIDxtYWxsb3J5QG1heWZpcnN0Lm9yZz7CwJgEEwECAEICGwMG CwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAhkBFiEE4+tj4GWjskC82bBxDDKicb08x4AFAlqo 9WUFCRAV234ACgkQDDKicb08x4DklAf+ODKRmP6C2MnBz6vL8N8l3vZJUqoRcYXTn3uTpT05 Wou87ZIZ/P/OV2/uOMKkczLQQydj5S8PxbLTeg+U5f/63hdy99ON+K2b4izg7Qasdl1SqXTH q1pmhbrcbLbVKDJ345fdEg7RuMnv4gd3EaT/yQa99zHy8JHaBKaPEUQAa65HTt2Sy2c6L6BA aMZx1TOZ9/cZ7L1gJyytJbEyvg/JLOatJEI4rewUWU2TMSGJijwjAUBagwDPWyxpz+vXdKsD tqRTpY4xvXaeUQo0QXf0c5j1Gcglzv7ywZcyz1MGD1aLS9/CqeB3I4EMbvH/33LS3jNkfKbV XOTSjmo7l22CNc7ATQRMdE1nAQgA4mpP2LjFuAW2li9FPbDYOMzt0MtThXsnvHyY0fDv8FlU qnKgPrMY80VHntnxwqepFS3ncunVX4ipq+fadta+LHpTnbJSmlphBrc9qGJxqcjwf4yo35Xh OXCJFwnaoAwIX237lXRe4Xh6X4VMuJt8jiZdvgpbk/whvQH2grcq8KjCcy1iuL5pBl8ZwYG/ dphitFhQdqEcnc/krIqG4KQgKiUi3K/GR0OeEmw/cscWD7/CLEo7eHiaGQhSOyDQbM+Iu2o/ 6uMXMUPsYlMMqgmVL68zMacO3PE17jx0rQ8oZ7CpBY8YZWOWrzXrtFT8JO9guuCPsvd4KT6y 97y9LRJlPQARAQABwsB8BBgBAgAmAhsMFiEE4+tj4GWjskC82bBxDDKicb08x4AFAlqo9WYF CRAV238ACgkQDDKicb08x4DU4QgAmlyBlFhfU0jpkbyD3HQ+3CJqWdBT422pVIrj3qNT2ehy fWO66Muidmd4Y279uV3p3TQEJOQvnV7FVAC9+bI7AdBy00BAjHgJ5eSQZxKTXUoeeBAsTZHN /HaHewjYWHMvCuuzir/Wt3A6Cehh8gp9I/Vg+oL3dTldVqqgZLgnA83bT/R8fI/e85LDlpdx KJ0+uy/grg3AbH7LUUrmMIC2iO8mQWYuNlizsUZLFvJhCAU2c5l8B5mv2BoWFhL+l7mmNcdF bwBFXon7Ea1jkCnbWVxtXkPYkcuWuMSTJswn9HhZVJWjUonKqUZKAb9PxRzC9crZ+X14tQT3 iJt2a4ZM4w==
Message-ID: <c6f5b1da-4b08-ee17-144b-c04115865014@article19.org>
Date: Thu, 10 May 2018 13:19:44 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <CAG3f7MjRGZf3D8R_n_cNNUGREUHtptQzRKHjcB2Ey=Kswh0F3w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: 02b201d9c048bcde4aa7ed91fc024d05
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/_fpmUUPyT2aZgVogEA6rA1b5Ccs>
Subject: Re: [HT-rt] Gitlab project for human Rights review team
X-BeenThere: hr-rt@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Human Rights Protocol Considerations Review Team <hr-rt.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hr-rt/>
List-Post: <mailto:hr-rt@irtf.org>
List-Help: <mailto:hr-rt-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 10:19:53 -0000

Thanks Shivan!

On 08/05/18 03:56, Shivan wrote:
> Okay I set up a GitLab "group" (similar to a GitHub org) for HR-RT with
> a "project" (similar to GitHub repo) called Documents. I've invited
> Niels and Mallory to be admins - again, if anyone else wants to be, lmk=
.=C2=A0
>=20
> https://gitlab.com/hr-rt
>=20
> On Mon, May 7, 2018 at 11:05 AM, Shivan <shivankaul.1993@gmail.com
> <mailto:shivankaul.1993@gmail.com>> wrote:
>=20
>     I think so? I'm not really familiar with Gitlab but I'd imagine it
>     has that. I'll take a look. We could also set it up under 0xacab as
>     Mallory suggested.=C2=A0
>=20
>     Yes they do offer a wiki! Do people prefer that over a readme? Most
>     GitHub projects I've seen generally just kept everything in their
>     READMEs. The advantage is that you have everything you want to know
>     about the project on the landing page instead of having to be
>     further redirected. If there's not much project description then
>     just using a README is better imo but either works.=C2=A0
>=20
>     On Mon, May 7, 2018 at 10:41 AM Niels ten Oever
>     <mail@nielstenoever.net <mailto:mail@nielstenoever.net>> wrote:
>=20
>         Hi Shivan,
>=20
>         I have been hitting myself since the beginning of HRPC that I
>         setup the
>         RG repo under my name instead of setting up a sepate
>         organization (ie
>         not connected one specific user). Is this also possible on
>         GitLab perhaps?
>=20
>         Does Gitlab also offer a wiki where we can keep track of things=
? Or
>         shall we all do that in the README.md file?
>=20
>         Cheers,
>=20
>         Niels
>=20
>         On 05/07/2018 04:27 PM, Shivan wrote:
>         > Hi all, I set up a gitlab project:=C2=A0
>         > https://gitlab.com/ShivanKaul/HR-RT
>         <https://gitlab.com/ShivanKaul/HR-RT>
>         >
>         > I uploaded the two analyses that have taken place so far. To
>         suggest a
>         > new draft/RFC for analysis, feel free to create a new issue
>         using the
>         > Suggested-Draft template - I used Mallory's proposed template=
.=C2=A0
>         >
>         > If anyone would like to be made moderator, please let me know=
 your
>         > gitlab username/email.=C2=A0
>         >
>         >
>         > _______________________________________________
>         > HR-rt mailing list
>         > HR-rt@irtf.org <mailto:HR-rt@irtf.org>
>         > https://www.irtf.org/mailman/listinfo/hr-rt
>         <https://www.irtf.org/mailman/listinfo/hr-rt>
>         >
>=20
>         _______________________________________________
>         HR-rt mailing list
>         HR-rt@irtf.org <mailto:HR-rt@irtf.org>
>         https://www.irtf.org/mailman/listinfo/hr-rt
>         <https://www.irtf.org/mailman/listinfo/hr-rt>
>=20
>=20
>=20
>=20
> _______________________________________________
> HR-rt mailing list
> HR-rt@irtf.org
> https://www.irtf.org/mailman/listinfo/hr-rt
>=20


--=20
Mallory Knodel
Head of Digital :: article19.org
gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9  B071 0C32 A271 BD3C C780


From nobody Fri May 11 13:39:35 2018
Return-Path: <mail@nielstenoever.net>
X-Original-To: hr-rt@ietfa.amsl.com
Delivered-To: hr-rt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35E9B12D87C for <hr-rt@ietfa.amsl.com>; Fri, 11 May 2018 13:39:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 gx8gqxdYGERb for <hr-rt@ietfa.amsl.com>; Fri, 11 May 2018 13:39:31 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (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 81759127873 for <hr-rt@irtf.org>; Fri, 11 May 2018 13:39:31 -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 1fHEp7-0000j4-9w for hr-rt@irtf.org; Fri, 11 May 2018 22:39:29 +0200
Date: Fri, 11 May 2018 22:39:08 +0200
From: Niels ten Oever <mail@nielstenoever.net>
To: Mallory Knodel <mallory@article19.org>
Cc: hr-rt@irtf.org
Message-ID: <20180511203908.GC13776@mir>
References: <CAG3f7MgRkJc273D-Zv-T4AhC8nN2w6C2zpp5DTuKcroDpGEYhQ@mail.gmail.com> <9f4e7a16-696e-70ec-bfb9-d364d7ec389a@nielstenoever.net> <CAG3f7Mg-762NLd4eYaYVV2f3wMUHZOUTikYAL60dLuXx8YU4og@mail.gmail.com> <CAG3f7MjRGZf3D8R_n_cNNUGREUHtptQzRKHjcB2Ey=Kswh0F3w@mail.gmail.com> <c6f5b1da-4b08-ee17-144b-c04115865014@article19.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="oTHb8nViIGeoXxdp"
Content-Disposition: inline
In-Reply-To: <c6f5b1da-4b08-ee17-144b-c04115865014@article19.org>
User-Agent: Mutt/1.9.5 (2018-04-13)
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: eb84bc049aa50d59c182d1adb242eeac
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/lEV-hEZn67GZFn0eRR5xLoTc78w>
Subject: Re: [HT-rt] Gitlab project for human Rights review team
X-BeenThere: hr-rt@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Human Rights Protocol Considerations Review Team <hr-rt.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hr-rt/>
List-Post: <mailto:hr-rt@irtf.org>
List-Help: <mailto:hr-rt-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 May 2018 20:39:34 -0000

--oTHb8nViIGeoXxdp
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Awesome! Am away coming week, but back at it next one. That week I'll also =
commit to doing a new review.

Cheers,

Niels


On Thu, May 10, 2018 at 01:19:44PM +0300, Mallory Knodel wrote:
> Thanks Shivan!
>=20
> On 08/05/18 03:56, Shivan wrote:
> > Okay I set up a GitLab "group" (similar to a GitHub org) for HR-RT with
> > a "project" (similar to GitHub repo) called Documents. I've invited
> > Niels and Mallory to be admins - again, if anyone else wants to be, lmk=
=2E=A0
> >=20
> > https://gitlab.com/hr-rt
> >=20
> > On Mon, May 7, 2018 at 11:05 AM, Shivan <shivankaul.1993@gmail.com
> > <mailto:shivankaul.1993@gmail.com>> wrote:
> >=20
> >     I think so? I'm not really familiar with Gitlab but I'd imagine it
> >     has that. I'll take a look. We could also set it up under 0xacab as
> >     Mallory suggested.=A0
> >=20
> >     Yes they do offer a wiki! Do people prefer that over a readme? Most
> >     GitHub projects I've seen generally just kept everything in their
> >     READMEs. The advantage is that you have everything you want to know
> >     about the project on the landing page instead of having to be
> >     further redirected. If there's not much project description then
> >     just using a README is better imo but either works.=A0
> >=20
> >     On Mon, May 7, 2018 at 10:41 AM Niels ten Oever
> >     <mail@nielstenoever.net <mailto:mail@nielstenoever.net>> wrote:
> >=20
> >         Hi Shivan,
> >=20
> >         I have been hitting myself since the beginning of HRPC that I
> >         setup the
> >         RG repo under my name instead of setting up a sepate
> >         organization (ie
> >         not connected one specific user). Is this also possible on
> >         GitLab perhaps?
> >=20
> >         Does Gitlab also offer a wiki where we can keep track of things=
? Or
> >         shall we all do that in the README.md file?
> >=20
> >         Cheers,
> >=20
> >         Niels
> >=20
> >         On 05/07/2018 04:27 PM, Shivan wrote:
> >         > Hi all, I set up a gitlab project:=A0
> >         > https://gitlab.com/ShivanKaul/HR-RT
> >         <https://gitlab.com/ShivanKaul/HR-RT>
> >         >
> >         > I uploaded the two analyses that have taken place so far. To
> >         suggest a
> >         > new draft/RFC for analysis, feel free to create a new issue
> >         using the
> >         > Suggested-Draft template - I used Mallory's proposed template=
=2E=A0
> >         >
> >         > If anyone would like to be made moderator, please let me know=
 your
> >         > gitlab username/email.=A0
> >         >
> >         >
> >         > _______________________________________________
> >         > HR-rt mailing list
> >         > HR-rt@irtf.org <mailto:HR-rt@irtf.org>
> >         > https://www.irtf.org/mailman/listinfo/hr-rt
> >         <https://www.irtf.org/mailman/listinfo/hr-rt>
> >         >
> >=20
> >         _______________________________________________
> >         HR-rt mailing list
> >         HR-rt@irtf.org <mailto:HR-rt@irtf.org>
> >         https://www.irtf.org/mailman/listinfo/hr-rt
> >         <https://www.irtf.org/mailman/listinfo/hr-rt>
> >=20
> >=20
> >=20
> >=20
> > _______________________________________________
> > HR-rt mailing list
> > HR-rt@irtf.org
> > https://www.irtf.org/mailman/listinfo/hr-rt
> >=20
>=20
>=20
> --=20
> Mallory Knodel
> Head of Digital :: article19.org
> gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9  B071 0C32 A271 BD3C C780
>=20
> _______________________________________________
> HR-rt mailing list
> HR-rt@irtf.org
> https://www.irtf.org/mailman/listinfo/hr-rt

--=20

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

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


--oTHb8nViIGeoXxdp
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJFgLcFxK/YqUiGQ6Dtg/OkaKyLMFAlr1/2wACgkQDtg/OkaK
yLPKZBAAnCDSJ6WQVR3FB+6eVNjGv46QnqGEPw5tKEXFDXBNkUApugt5hm3K2O90
PnyJiR1tP0RDo8E82ZPU2Ymkt3PJnJMi/AjLJH1qVV7c/UP7FXE0HMxGk/iIL5vK
HhQnVuOU+hwoseExE3UirWPtgezji9cssj2p6LYFJaMB8Zfjg++yQQ1Z/yjTrRKe
KfRxDc5Knu7b5ws4tJkLwLWUNcGLn5lK+2GDfTb7S49l74hbfNv0YYl04NBycnN2
VSDCLyOupqVtaPwg082FJOt35iYW5zll52fPzP85Y4Ntpz0HWhtRo1lu86LI7yXP
JmcAP4JywuqHHh/7vQq55wNLIKLXMdh23upnpxtXAMWrmkk8jpxdM1aQIe1Q+inf
eWakqNdgzmxwJXaX43+kCnN451rj/Zbr9U2nETY84qTy9HhD+vcvLmCvpWdNU+sj
eP1PpGHqmM8zWp2zOBF5tgxNXJiMX4QaktYoAJPh4sOkSL3gEDbxK7yUTRrPxig8
FpRsCmduLpr75CzbMQOAOebL4+47svHIkNx4a5sHdfTLpEKMlBnSeu1Khxqnju84
YVpNqjr4xJXqSjxPUHwwdu2EnwgLfciHso4ShFzLdrc2pM6WDtLmU1YGnRVjvO//
Sv52VJ/cItB5MidHqUdk1alZ3KZaME+18gaU0Zun1PoCtl9oJgE=
=JlRy
-----END PGP SIGNATURE-----

--oTHb8nViIGeoXxdp--


From nobody Thu May 24 21:24:07 2018
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: hr-rt@ietfa.amsl.com
Delivered-To: hr-rt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F53512D885 for <hr-rt@ietfa.amsl.com>; Thu, 24 May 2018 21:24:00 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9WZntx6nz4d7 for <hr-rt@ietfa.amsl.com>; Thu, 24 May 2018 21:23:55 -0700 (PDT)
Received: from mail-yb0-x233.google.com (mail-yb0-x233.google.com [IPv6:2607:f8b0:4002:c09::233]) (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 7863312D88A for <hr-rt@irtf.org>; Thu, 24 May 2018 21:23:55 -0700 (PDT)
Received: by mail-yb0-x233.google.com with SMTP id p22-v6so1401582yba.13 for <hr-rt@irtf.org>; Thu, 24 May 2018 21:23:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3XumPmNTH7m/Vt5/Gcxhnf81ehxhaTAP/YHnVxxpofQ=; b=JUmVWYlmDxQgjeY3/m8R7iMvQvJNR97oreZ8pPudsGnejRQHufmfg7ZCTPAEDsTYP6 1CBqYBupo0ECWMF8RRXanunkBPqPXqXubZ3lb5pnjsO3aeJxZyZ7IhtKfLOFZ86OnPMK 6CcOjnTxegN0HSxISBrBS2OIwuWqYnyV9UPTaAOKY3RBSHi1JP61H1eKygy85BVpAbWa 7O/fMMhqzRNsAusKKg5tLDQXnOEDxNkZFkBAKOY8rGqX+x6+3EABm9lmvbRgsOHnnKBh ZxNqfxsAMnSCO0Dr05CXVjgQ/CUNOaDlw0WVeNGNe0Usui1Eh4B4QzsdkPwco4Ig+eSl R0mQ==
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=3XumPmNTH7m/Vt5/Gcxhnf81ehxhaTAP/YHnVxxpofQ=; b=C9Khp4pWvDT1s1VEGZGQmunVzX0Ovs+DnYUEU9cFNgj2BSEA/p74L7paymNAsy5U1m M+wP+b8n3OBFqpqnQODdez6MwgOwKasqCHsIf79+FC7fAAwLk3Z/Zj0hDYKKv3mDHgRk U14rRHqMZTsW/bOTcDRi3FIUbZVml8fTaZD9kcuvcwHX8tVyzDd1SO5bvj/qQ0UT4ISN e8M4KyENsB9TLxYLIOQZvN/D5UAB9lKdjV7IzflcnTVJfSS1h9IvDp6OTwwwassRkfAE gkYim8ehNTWud58Dufj2VHzxUVjRHdgfT3jsOnsWLxIGvfS592P7RI824s8eWnIp5yLU WeKQ==
X-Gm-Message-State: ALKqPwf2u5FWH/6BxJ4a+z3zWFiHwd9tFRJp228wuonILddKCzz+Rh2n 61wG7Q8t74koIWO3wnyPk4sqYukDWkT45uHof+w=
X-Google-Smtp-Source: AB8JxZpuSZ6KzYC0dBRy1ZEl7TSYaNepkKbS7bpIqq3jTgyThRb78iYlE1pYI/71OnaFE3F0qwlhD2NIoIS4Uca7wKY=
X-Received: by 2002:a25:618f:: with SMTP id v137-v6mr406023ybb.221.1527222234507;  Thu, 24 May 2018 21:23:54 -0700 (PDT)
MIME-Version: 1.0
References: <CAG3f7Mgd3yArxLsGdMS6-Ki2GqemtKhTLeHXrD8mqEMnV7CXLg@mail.gmail.com>
In-Reply-To: <CAG3f7Mgd3yArxLsGdMS6-Ki2GqemtKhTLeHXrD8mqEMnV7CXLg@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 24 May 2018 23:23:42 -0500
Message-ID: <CAKKJt-fQqjFUsUBYZ9rpYtkfAZ3nnv0c3Jt6S3wR4AEPOdbd0Q@mail.gmail.com>
To: Shivan <shivankaul.1993@gmail.com>
Cc: hr-rt@irtf.org, architecture-discuss@ietf.org, IAB IAB <iab@iab.org>
Content-Type: multipart/alternative; boundary="000000000000c7ee5a056d002298"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/E4uXQms8yMkDcJKYEwAueO3aAZM>
Subject: Re: [HT-rt] [arch-d]  HR-RT Review of draft-iab-marnew-report-01
X-BeenThere: hr-rt@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Human Rights Protocol Considerations Review Team <hr-rt.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hr-rt/>
List-Post: <mailto:hr-rt@irtf.org>
List-Help: <mailto:hr-rt-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2018 04:24:01 -0000

--000000000000c7ee5a056d002298
Content-Type: text/plain; charset="UTF-8"

Hi, Amelia and Shivan,

On Wed, May 2, 2018 at 12:12 PM Shivan <shivankaul.1993@gmail.com> wrote:

> This is a review done within the framework of the Human Rights Review
> Team. It was done by Amelia Andersdotter and Shivan Kaul Sahib. The Human
> Rights Review Team aims to implement and improve the guidelines for
> human rights considerations provided in RFC8280, and seek to mitigate
> potentially adverse human rights impacts that IETF and IRTF documents
> might have.
>

An aside - I'm glad we're doing this (and I get to say that as an IESG
member), but I hadn't heard that we would be doing it.

I'm glad this document was picked to review. Thanks for that.

Inline ...


>
> We find the topics addressed during the workshop interesting and look
> forward to following future developments.
>
> ---
>
> Document: draft-iab-marnew-report-01
> <https://datatracker.ietf.org/doc/draft-iab-marnew-report/>
> https://datatracker.ietf.org/doc/draft-iab-marnew-report/
>
> Review:
>
> The Human Rights in Protocols Research Group welcomes the draft report
> from the MaRNEW workshop. In particular, we welcome the efforts to continue
> advancing an encrypted, secure and human rights enabling environment, as
> well as solid assessments of the potential impacts of considered remedies
> to mobile network operator difficulties on the right to privacy of an
> individual.
>
> In this regard, we wish to remind the drafters and the IAB of the inherent
> connection between privacy and freedom of expression. The right to privacy,
> or to one's own personhood, reinforces the freedom of expression and
> freedom of opinion.
>
> Semantic Suggestions
> ===========================
>
> The following sections addresses a few semantic problems in the draft
> report, that were they solved the draft report would be easier to parse
> from both a human rights perspective, and from a business, legal or
> technical perspective.
>
> 1. Abstract, para 2:
>
> Problem: Draft text contains  value judgements on participants'
> presentations that could be avoided.
>
> Solution: Remove the word "honest" in relation to CDN presentations, since
> it may cause readers to assume that other presenters were less forthcoming.
>
> The new paragraph would read
>
>    The group discussed the current Internet encryption trends and
>    deployment issues identified within the IETF, and the privacy needs
>    of users which should be adhered.  Solutions designed around sharing
>    data from the network to the endpoints and vice versa were then
>    discussed as well as analysing whether the current issues experienced
>    on the transport layer are also playing a role here.  Content
>    providers and CDNs gave their views of delivering
>    content with mobile network operators.  Finally, technical responses
>    to regulation was discussed to help the regulated industries relay
>    the issues of impossible to implement or bad-for-privacy technologies
>    back to regulators.
>

I adjusted this to "gave their own views", but, yes.


>
> 2. Section 1, Introduction:
>
> Problem: It is unclear whether the "requirements" referred to imply
> regulatory requirements enforceable by government authorities, or technical
> requirements. Because of the nature of issues discussed during the
> workshop, understanding what sorts of "requirements" are being referred to
> is imperative.
>
> Solution: Specify the nature of the requirements being referred to, or
> remove the reference to requirements.
>
> The new Introduction would read
>
>    Mobile networks have a set of properties which
>    places a large emphasis on sophisticated bandwidth optimization.
>    Encryption is increasing on the Internet which is positive for
>    consumer and business privacy and security.  Many existing mobile
>    bandwidth optimization solutions primarily operate on non-encrypted
>    communications; this can lead to performance issues being amplified
>    on mobile networks.  Encryption on networks will continue to
>    increase; and with this understanding the workshop aimed to
>    understand how we can solve the issues of bandwidth optimization and
>    performance on radio networks in this encrypted world.
>

I used this (with one s/;/,/).

>
> 3. Section 1.1:
>
> Problem: The first paragraph mixes business models with technical
> necessities. The last paragraph in the section Understanding "Bandwidth
> Optimization" refers to regulatory requirements (within the meaning of
> government enforced requirements or legal requirements, cf above) on mobile
> network operators to perform traffic filtering and monitoring.
>
> Solution: It may facilitate understanding of human rights impacts to
> separate technical considerations from business considerations and legal
> considerations. Paragraph 3 ("Many of these functions can continue...")
> could be put as the last paragraph, while Paragraph 1 could be split into a
> technical section and a business model section, followed by a legal section.
>
>
>    For the purposes of this workshop, bandwidth optimization encompasses
>    a variety of technical topics related to traffic engineering,
>    prioritisation, optimisation and efficiency enhancements. It also
> encompasses
>    user-related topics such as specific subscription or billing models,
> and may touch upon regulatory aspects or other issues relating to
> regulatory, within the meaning of government initiated, concerns.
>
>    The first category of bandwidth optimization includes:
>
>    o  Caching
>
>    o  Prioritisation of interactive traffic over background traffic
>
>    o  Per-user bandwidth limit
>
>    The second category of bandwidth optimization may depend on either of
> the first category optimization strategies, but may, in particular, also
> encompass:
>
>    o  Business-related topics such as content delivery arrangements with
>       specific content providers.
>
>    Finally, while not strictly speaking traffic management, some
>    networks employ policy-based filtering (e.g., requested parental
>    controls) and many networks support some form of legal interception
>    functionality per applicable laws.
>
>    Many of these functions can continue as they're performed today, even
>    with more encryption.  Others are using methods which inspect parts
>    of the communication that are encrypted, and these will have to be
>    done differently in an encrypted Internet.
>

I used this structure, and made a few editorial changes that seemed to
clarify the text.

>
>
> 4. Section 4:
>
> Problem: QUIC is an active area of work for the IETF in the transport
> layer - this section barely mentions it, and even then does so vaguely.
> What problems are solved by QUIC that are general problems rather than TCP
> problems? What was the nature of the disagreement around this?
>
> Solution: More detail about how QUIC fits into transport-layer work would
> make this section more relevant. In addition, there has been discussion
> involving network operators around technical details that have potential
> privacy impacts within the QUIC working group (SPIN bit); this section
> would benefit greatly from an examination of that.
>

This topic has grown in interest significantly after the MaRNEW workshop -
the QUIC BOF happened nearly a year later, and formation of the working
group happened a few months after the BOF. We really didn't talk about QUIC
at the workshop, except when people (often from Google) referred to
specific experiences with the proprietary QUIC protocol in discussion.

I look forward to seeing what the next workshop in this space says in its
workshop report ;-) ...


>
>
>
> Human Rights Considerations
> ===========================
>
> Upon consideration of the draft report, no implications for
> internationalization ([RFC8280], sec. 6.2.5), heterogeneity support
> ([RFC8280], sec. 6.2.8), accessibility ([RFC8280], sec. 6.2.11) or
> localization ([RFC8280], sec. 6.2.12) have been found. We will further
> suppose that issues relating to Anonymity ([RFC8280], sec. 6.2.9),
> Pseudonymity ([RFC8280], sec. 6.2.10) and Confidentiality ([RFC8280], sec.
> 6.2.16) have been sufficiently addressed in the draft as is.
>
> In the below text, Security ([RFC8280], sec. 6.2.4), Integrity ([RFC8280],
> sec. 6.2.16) and Authenticity ([RFC8280], sec. 6.2.17) are further
> considered to have been addressed, or as in progress of being addressed by
> the specific endeavours pointed out in the report. As such, this assessment
> hopes to serve as a complement to remaining Human Rights Considerations
> Guidelines which were not addressed by the MaRNEW draft.
>
> ## Privacy ([RFC8280], sec. 6.2.2)
>
> We laud the general emphasis on considering user privacy concerns
> paramount [Section 2.1.1, 2.3 etc].
>
> In Section 3.1.1, para 1, it would be useful to emphasize that middleboxes
> that are "authenticated and invoked explicitly" might not be very effective
> at conserving user privacy if they lead to auto-click through. In practice,
> "opted-in" middleboxes might not be much better than transparent
> middleboxes. Additionally, this poses the danger of making matters worse if
> users assume that because they haven't been asked for middlebox permission,
> they are not going through a middlebox. For users accessing the Internet on
> a browser client: if the connection is MITMed by a middlebox, the browser
> would somehow need to convey this effectively and actionably to the user.
> Whatever effort is expended on this should involve browser vendors.
>

I agree with your point here, but this issue wasn't raised in the workshop
at the time. This is good information to keep in mind as we move forward on
standardization efforts in a post-MaRNEW world.


>
> ## Connectivity ([RFC8280], sec. 6.2..1)
>
> It is a priori obvious that a discussion with mobile network operators
> would touch upon connectivity. As a general comment, the HRPC RG is not
> concerned that encrypted internet traffic could create topological problems
> in network deployment with respect to density of base stations. It is more
> sensible to imagine that the density of base stations is kept low by
> deployers to save money on infrastructure roll-out.
>
> In the MarNEW draft report, middleboxes are brought up frequently as an
> example of infrastructure rendered less useful by the ubiquitous adoption
> of encryption. Middleboxes may enhance access to content for individuals,
> and may also interfere with their ability to enjoy content free of
> surveillance, censorship or content manipulation. The focus of the workshop
> of exploring ways in which encrypted materials can benefit from the same
> speed of deliverance as un-encrypted materials is therefore welcome.
>

I agree, and would say that this is a guiding principle for current
specification efforts in places like the QUIC working group.


>
> ## Content Agnosticism
>
> Traffic prioritisation, whether based on technical or commercial grounds,
> risks interfering with an individual's right to freedom of expression or
> opinion, by restricting access or enjoy content of their own choosing. As
> such, prioritisation should be made explicit and obvious, and subject to
> consent from the individual, whether the motivations for deployment are
> commercial or technical.
>
> It is clear that internet filtering and blocking of content of specific
> types, whether motivated by network management or regulatory concerns, does
> not fulfill a content agnosticism criterion. It is the observation of HRPC
> that [RFC7725] (An HTTP Status Code to Report Legal Obstacles) may assist
> communication of specific filtering and blocking operations in action.
>
> It the the impetus of the Human Rights Guidelines in RFC8280 that content
> agnosticism be respected by protocols developed in the IETF, and in general
> an accepted view in the global human rights community that content
> agnosticism is desirable at all levels of technical infrastructure. As
> such, the HRPC RG is concerned about ideas that traffic be classified
> through additional headers or metadata, identifying traffic via 5-tuples,
> trust models and frameworks, or heuristics.
>

These last points are good things to keep in mind as our specification work
moves forward.

Again, thank you for all of this, and I look forward to considering these
issues more consistently in the future than we were in 2015.

Spencer


>
>
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss
>

--000000000000c7ee5a056d002298
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, Amelia and Shivan,<br><br><div class=3D"gmail_quote"><=
div dir=3D"ltr">On Wed, May 2, 2018 at 12:12 PM Shivan &lt;<a href=3D"mailt=
o:shivankaul.1993@gmail.com">shivankaul.1993@gmail.com</a>&gt; wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><span style=
=3D"color:rgb(51,51,51);font-family:georgia,serif">This is a review done wi=
thin the framework of the Human Rights Review</span><br></div><div><div><fo=
nt color=3D"#333333" face=3D"georgia, serif">Team. It was done by Amelia An=
dersdotter and Shivan Kaul Sahib. The Human</font></div><div><font color=3D=
"#333333" face=3D"georgia, serif">Rights Review Team aims to implement and =
improve the guidelines for</font></div><div><font color=3D"#333333" face=3D=
"georgia, serif">human rights considerations provided in RFC8280, and seek =
to mitigate</font></div><div><font color=3D"#333333" face=3D"georgia, serif=
">potentially adverse human rights impacts that IETF and IRTF documents</fo=
nt></div><div><font color=3D"#333333" face=3D"georgia, serif">might have.</=
font></div></div></div></div></blockquote><div><br></div><div>An aside - I&=
#39;m glad we&#39;re doing this (and I get to say that as an IESG member), =
but I hadn&#39;t heard that we would be doing it.</div><div><br></div><div>=
I&#39;m glad this document was picked to review. Thanks for that.=C2=A0</di=
v><div><br></div><div>Inline ...</div><div>=C2=A0</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex"><div dir=3D"ltr"><div><div><div><font color=3D"#333333" face=3D"=
georgia, serif"><br></font></div><div><font color=3D"#333333" face=3D"georg=
ia, serif">We find the topics addressed during the workshop interesting and=
 look</font></div><div><font color=3D"#333333" face=3D"georgia, serif">forw=
ard to following future developments.</font></div><div><font color=3D"#3333=
33" face=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" f=
ace=3D"georgia, serif">---</font></div><div><font color=3D"#333333" face=3D=
"georgia, serif"><br></font></div><div><font color=3D"#333333" face=3D"geor=
gia, serif">Document: <a href=3D"https://datatracker.ietf.org/doc/draft-iab=
-marnew-report/" target=3D"_blank">draft-iab-marnew-report-01</a></font></d=
iv><div><a href=3D"https://datatracker.ietf.org/doc/draft-iab-marnew-report=
/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-iab-marnew-repo=
rt/</a><br></div><div><font color=3D"#333333" face=3D"georgia, serif"><br><=
/font></div><div><font color=3D"#333333" face=3D"georgia, serif">Review:</f=
ont></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font><=
/div><div><font color=3D"#333333" face=3D"georgia, serif">The Human Rights =
in Protocols Research Group welcomes the draft report from the MaRNEW works=
hop. In particular, we welcome the efforts to continue advancing an encrypt=
ed, secure and human rights enabling environment, as well as solid assessme=
nts of the potential impacts of considered remedies to mobile network opera=
tor difficulties on the right to privacy of an individual.</font></div><div=
><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><fon=
t color=3D"#333333" face=3D"georgia, serif">In this regard, we wish to remi=
nd the drafters and the IAB of the inherent connection between privacy and =
freedom of expression. The right to privacy, or to one&#39;s own personhood=
, reinforces the freedom of expression and freedom of opinion.</font></div>=
<div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div>=
<font color=3D"#333333" face=3D"georgia, serif">Semantic Suggestions</font>=
</div><div><font color=3D"#333333" face=3D"georgia, serif">=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</font></=
div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><=
div><font color=3D"#333333" face=3D"georgia, serif">The following sections =
addresses a few semantic problems in the draft report, that were they solve=
d the draft report would be easier to parse from both a human rights perspe=
ctive, and from a business, legal or technical perspective.</font></div><di=
v><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><fo=
nt color=3D"#333333" face=3D"georgia, serif">1. Abstract, para 2:</font></d=
iv><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><d=
iv><font color=3D"#333333" face=3D"georgia, serif">Problem: Draft text cont=
ains=C2=A0 value judgements on participants&#39; presentations that could b=
e avoided.</font></div><div><font color=3D"#333333" face=3D"georgia, serif"=
><br></font></div><div><font color=3D"#333333" face=3D"georgia, serif">Solu=
tion: Remove the word &quot;honest&quot; in relation to CDN presentations, =
since it may cause readers to assume that other presenters were less forthc=
oming.</font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br=
></font></div><div><font color=3D"#333333" face=3D"georgia, serif">The new =
paragraph would read</font></div><div><font color=3D"#333333" face=3D"georg=
ia, serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, s=
erif">=C2=A0 =C2=A0The group discussed the current Internet encryption tren=
ds and</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=
=A0 =C2=A0deployment issues identified within the IETF, and the privacy nee=
ds</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =
=C2=A0of users which should be adhered.=C2=A0 Solutions designed around sha=
ring</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=
=A0 =C2=A0data from the network to the endpoints and vice versa were then</=
font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=
=A0discussed as well as analysing whether the current issues experienced</f=
ont></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=
=A0on the transport layer are also playing a role here.=C2=A0 Content</font=
></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0pr=
oviders and CDNs gave their views of delivering</font></div><div><font colo=
r=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0content with mobile netw=
ork operators.=C2=A0 Finally, technical responses</font></div><div><font co=
lor=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0to regulation was disc=
ussed to help the regulated industries relay</font></div><div><font color=
=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0the issues of impossible =
to implement or bad-for-privacy technologies</font></div><div><font color=
=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0back to regulators.</font=
></div></div></div></div></blockquote><div><br></div><div>I adjusted this t=
o &quot;gave their own views&quot;, but, yes.</div><div>=C2=A0</div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><div dir=3D"ltr"><div><div><div><font color=3D"#333=
333" face=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" =
face=3D"georgia, serif">2. Section 1, Introduction:</font></div><div><font =
color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=
=3D"#333333" face=3D"georgia, serif">Problem: It is unclear whether the &qu=
ot;requirements&quot; referred to imply regulatory requirements enforceable=
 by government authorities, or technical requirements. Because of the natur=
e of issues discussed during the workshop, understanding what sorts of &quo=
t;requirements&quot; are being referred to is imperative.</font></div><div>=
<font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font=
 color=3D"#333333" face=3D"georgia, serif">Solution: Specify the nature of =
the requirements being referred to, or remove the reference to requirements=
.</font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></fo=
nt></div><div><font color=3D"#333333" face=3D"georgia, serif">The new Intro=
duction would read</font></div><div><font color=3D"#333333" face=3D"georgia=
, serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, ser=
if">=C2=A0 =C2=A0Mobile networks have a set of properties which</font></div=
><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0places a=
 large emphasis on sophisticated bandwidth optimization.</font></div><div><=
font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0Encryption is i=
ncreasing on the Internet which is positive for</font></div><div><font colo=
r=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0consumer and business pr=
ivacy and security.=C2=A0 Many existing mobile</font></div><div><font color=
=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0bandwidth optimization so=
lutions primarily operate on non-encrypted</font></div><div><font color=3D"=
#333333" face=3D"georgia, serif">=C2=A0 =C2=A0communications; this can lead=
 to performance issues being amplified</font></div><div><font color=3D"#333=
333" face=3D"georgia, serif">=C2=A0 =C2=A0on mobile networks.=C2=A0 Encrypt=
ion on networks will continue to</font></div><div><font color=3D"#333333" f=
ace=3D"georgia, serif">=C2=A0 =C2=A0increase; and with this understanding t=
he workshop aimed to</font></div><div><font color=3D"#333333" face=3D"georg=
ia, serif">=C2=A0 =C2=A0understand how we can solve the issues of bandwidth=
 optimization and</font></div><div><font color=3D"#333333" face=3D"georgia,=
 serif">=C2=A0 =C2=A0performance on radio networks in this encrypted world.=
</font></div></div></div></div></blockquote><div><br></div><div>I used this=
 (with one s/;/,/).=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"l=
tr"><div><div><div><font color=3D"#333333" face=3D"georgia, serif"><br></fo=
nt></div><div><font color=3D"#333333" face=3D"georgia, serif">3. Section 1.=
1:</font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></f=
ont></div><div><font color=3D"#333333" face=3D"georgia, serif">Problem: The=
 first paragraph mixes business models with technical necessities. The last=
 paragraph in the section Understanding &quot;Bandwidth Optimization&quot; =
refers to regulatory requirements (within the meaning of government enforce=
d requirements or legal requirements, cf above) on mobile network operators=
 to perform traffic filtering and monitoring.</font></div><div><font color=
=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=3D"#=
333333" face=3D"georgia, serif">Solution: It may facilitate understanding o=
f human rights impacts to separate technical considerations from business c=
onsiderations and legal considerations. Paragraph 3 (&quot;Many of these fu=
nctions can continue...&quot;) could be put as the last paragraph, while Pa=
ragraph 1 could be split into a technical section and a business model sect=
ion, followed by a legal section.</font></div><div><font color=3D"#333333" =
face=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" face=
=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" face=3D"g=
eorgia, serif">=C2=A0 =C2=A0For the purposes of this workshop, bandwidth op=
timization encompasses</font></div><div><font color=3D"#333333" face=3D"geo=
rgia, serif">=C2=A0 =C2=A0a variety of technical topics related to traffic =
engineering,</font></div><div><font color=3D"#333333" face=3D"georgia, seri=
f">=C2=A0 =C2=A0prioritisation, optimisation and efficiency enhancements. I=
t also encompasses</font></div><div><font color=3D"#333333" face=3D"georgia=
, serif">=C2=A0 =C2=A0user-related topics such as specific subscription or =
billing models, and may touch upon regulatory aspects or other issues relat=
ing to regulatory, within the meaning of government initiated, concerns.</f=
ont></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font><=
/div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0The =
first category of bandwidth optimization includes:</font></div><div><font c=
olor=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=
=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0o=C2=A0 Caching</font></d=
iv><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><d=
iv><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0o=C2=A0 Pri=
oritisation of interactive traffic over background traffic</font></div><div=
><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><fon=
t color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0o=C2=A0 Per-user b=
andwidth limit</font></div><div><font color=3D"#333333" face=3D"georgia, se=
rif">=C2=A0 =C2=A0</font></div><div><font color=3D"#333333" face=3D"georgia=
, serif">=C2=A0 =C2=A0The second category of bandwidth optimization may dep=
end on either of the first category optimization strategies, but may, in pa=
rticular, also encompass:</font></div><div><font color=3D"#333333" face=3D"=
georgia, serif"><br></font></div><div><font color=3D"#333333" face=3D"georg=
ia, serif">=C2=A0 =C2=A0o=C2=A0 Business-related topics such as content del=
ivery arrangements with</font></div><div><font color=3D"#333333" face=3D"ge=
orgia, serif">=C2=A0 =C2=A0 =C2=A0 specific content providers.</font></div>=
<div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0 =C2=A0=
=C2=A0</font></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=
=A0 =C2=A0Finally, while not strictly speaking traffic management, some</fo=
nt></div><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0=
networks employ policy-based filtering (e.g., requested parental</font></di=
v><div><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0control=
s) and many networks support some form of legal interception</font></div><d=
iv><font color=3D"#333333" face=3D"georgia, serif">=C2=A0 =C2=A0functionali=
ty per applicable laws.</font></div><div><font color=3D"#333333" face=3D"ge=
orgia, serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia=
, serif">=C2=A0 =C2=A0Many of these functions can continue as they&#39;re p=
erformed today, even</font></div><div><font color=3D"#333333" face=3D"georg=
ia, serif">=C2=A0 =C2=A0with more encryption.=C2=A0 Others are using method=
s which inspect parts</font></div><div><font color=3D"#333333" face=3D"geor=
gia, serif">=C2=A0 =C2=A0of the communication that are encrypted, and these=
 will have to be</font></div><div><font color=3D"#333333" face=3D"georgia, =
serif">=C2=A0 =C2=A0done differently in an encrypted Internet.</font></div>=
</div></div></div></blockquote><div><br></div><div>I used this structure, a=
nd made a few editorial changes that seemed to clarify the text.=C2=A0=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><div><fo=
nt color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font co=
lor=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=
=3D"#333333" face=3D"georgia, serif">4. Section 4:</font></div><div><font c=
olor=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=
=3D"#333333" face=3D"georgia, serif">Problem: QUIC is an active area of wor=
k for the IETF in the transport layer - this section barely mentions it, an=
d even then does so vaguely. What problems are solved by QUIC that are gene=
ral problems rather than TCP problems? What was the nature of the disagreem=
ent around this?</font></div><div><font color=3D"#333333" face=3D"georgia, =
serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, serif=
">Solution: More detail about how QUIC fits into transport-layer work would=
 make this section more relevant. In addition, there has been discussion in=
volving network operators around technical details that have potential priv=
acy impacts within the QUIC working group (SPIN bit); this section would be=
nefit greatly from an examination of that.</font></div></div></div></div></=
blockquote><div><br></div><div>This topic has grown in interest significant=
ly after the MaRNEW workshop - the QUIC BOF happened nearly a year later, a=
nd formation of the working group happened a few months after the BOF. We r=
eally didn&#39;t talk about QUIC at the workshop, except when people (often=
 from Google) referred to specific experiences with the proprietary QUIC pr=
otocol in discussion.=C2=A0</div><div><br></div><div>I look forward to seei=
ng what the next workshop in this space says in its workshop report ;-) ...=
</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div=
><div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div=
><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div=
><font color=3D"#333333" face=3D"georgia, serif"><br></font></div><div><fon=
t color=3D"#333333" face=3D"georgia, serif">Human Rights Considerations</fo=
nt></div><div><font color=3D"#333333" face=3D"georgia, serif">=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</font=
></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></di=
v><div><font color=3D"#333333" face=3D"georgia, serif">Upon consideration o=
f the draft report, no implications for internationalization ([RFC8280], se=
c. 6.2.5), heterogeneity support ([RFC8280], sec. 6.2.8), accessibility ([R=
FC8280], sec. 6.2.11) or localization ([RFC8280], sec. 6.2.12) have been fo=
und. We will further suppose that issues relating to Anonymity ([RFC8280], =
sec. 6.2.9), Pseudonymity ([RFC8280], sec. 6.2.10) and Confidentiality ([RF=
C8280], sec. 6.2.16) have been sufficiently addressed in the draft as is.</=
font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font>=
</div><div><font color=3D"#333333" face=3D"georgia, serif">In the below tex=
t, Security ([RFC8280], sec. 6.2.4), Integrity ([RFC8280], sec. 6.2.16) and=
 Authenticity ([RFC8280], sec. 6.2.17) are further considered to have been =
addressed, or as in progress of being addressed by the specific endeavours =
pointed out in the report. As such, this assessment hopes to serve as a com=
plement to remaining Human Rights Considerations Guidelines which were not =
addressed by the MaRNEW draft.</font></div><div><font color=3D"#333333" fac=
e=3D"georgia, serif"><br></font></div><div><font color=3D"#333333" face=3D"=
georgia, serif">## Privacy ([RFC8280], sec. 6.2.2)</font></div><div><font c=
olor=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=
=3D"#333333" face=3D"georgia, serif">We laud the general emphasis on consid=
ering user privacy concerns paramount [Section 2.1.1, 2.3 etc].=C2=A0</font=
></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font></di=
v><div><font color=3D"#333333" face=3D"georgia, serif">In Section 3.1.1, pa=
ra 1, it would be useful to emphasize that middleboxes that are &quot;authe=
nticated and invoked explicitly&quot; might not be very effective at conser=
ving user privacy if they lead to auto-click through. In practice, &quot;op=
ted-in&quot; middleboxes might not be much better than transparent middlebo=
xes. Additionally, this poses the danger of making matters worse if users a=
ssume that because they haven&#39;t been asked for middlebox permission, th=
ey are not going through a middlebox. For users accessing the Internet on a=
 browser client: if the connection is MITMed by a middlebox, the browser wo=
uld somehow need to convey this effectively and actionably to the user. Wha=
tever effort is expended on this should involve browser vendors.</font></di=
v></div></div></div></blockquote><div><br></div><div>I agree with your poin=
t here, but this issue wasn&#39;t raised in the workshop at the time. This =
is good information to keep in mind as we move forward on standardization e=
fforts in a post-MaRNEW world.</div><div>=C2=A0</div><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex"><div dir=3D"ltr"><div><div><div><font color=3D"#333333" face=3D"ge=
orgia, serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia=
, serif">## Connectivity ([RFC8280], sec. 6.2..1)</font></div><div><font co=
lor=3D"#333333" face=3D"georgia, serif"><br></font></div><div><font color=
=3D"#333333" face=3D"georgia, serif">It is a priori obvious that a discussi=
on with mobile network operators would touch upon connectivity. As a genera=
l comment, the HRPC RG is not concerned that encrypted internet traffic cou=
ld create topological problems in network deployment with respect to densit=
y of base stations. It is more sensible to imagine that the density of base=
 stations is kept low by deployers to save money on infrastructure roll-out=
.</font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></fo=
nt></div><div><font color=3D"#333333" face=3D"georgia, serif">In the MarNEW=
 draft report, middleboxes are brought up frequently as an example of infra=
structure rendered less useful by the ubiquitous adoption of encryption. Mi=
ddleboxes may enhance access to content for individuals, and may also inter=
fere with their ability to enjoy content free of surveillance, censorship o=
r content manipulation. The focus of the workshop of exploring ways in whic=
h encrypted materials can benefit from the same speed of deliverance as un-=
encrypted materials is therefore welcome.</font></div></div></div></div></b=
lockquote><div><br></div><div>I agree, and would say that this is a guiding=
 principle for current specification efforts in places like the QUIC workin=
g group.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div di=
r=3D"ltr"><div><div><div><font color=3D"#333333" face=3D"georgia, serif"><b=
r></font></div><div><font color=3D"#333333" face=3D"georgia, serif">## Cont=
ent Agnosticism</font></div><div><font color=3D"#333333" face=3D"georgia, s=
erif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, serif"=
>Traffic prioritisation, whether based on technical or commercial grounds, =
risks interfering with an individual&#39;s right to freedom of expression o=
r opinion, by restricting access or enjoy content of their own choosing. As=
 such, prioritisation should be made explicit and obvious, and subject to c=
onsent from the individual, whether the motivations for deployment are comm=
ercial or technical.</font></div><div><font color=3D"#333333" face=3D"georg=
ia, serif"><br></font></div><div><font color=3D"#333333" face=3D"georgia, s=
erif">It is clear that internet filtering and blocking of content of specif=
ic types, whether motivated by network management or regulatory concerns, d=
oes not fulfill a content agnosticism criterion. It is the observation of H=
RPC that [RFC7725] (An HTTP Status Code to Report Legal Obstacles) may assi=
st communication of specific filtering and blocking operations in action.</=
font></div><div><font color=3D"#333333" face=3D"georgia, serif"><br></font>=
</div><div><font color=3D"#333333" face=3D"georgia, serif">It the the impet=
us of the Human Rights Guidelines in RFC8280 that content agnosticism be re=
spected by protocols developed in the IETF, and in general an accepted view=
 in the global human rights community that content agnosticism is desirable=
 at all levels of technical infrastructure. As such, the HRPC RG is concern=
ed about ideas that traffic be classified through additional headers or met=
adata, identifying traffic via 5-tuples, trust models and frameworks, or he=
uristics.</font></div></div></div></div></blockquote><div><br></div><div>Th=
ese last points are good things to keep in mind as our specification work m=
oves forward.</div><div><br></div><div>Again, thank you for all of this, an=
d I look forward to considering these issues more consistently in the futur=
e than we were in 2015.</div><div><br></div><div>Spencer</div><div>=C2=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><div><br></di=
v></div><div style=3D"color:rgb(51,51,51);font-family:georgia,serif;font-si=
ze:small"><br></div></div></div>
_______________________________________________<br>
Architecture-discuss mailing list<br>
<a href=3D"mailto:Architecture-discuss@ietf.org" target=3D"_blank">Architec=
ture-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/architecture-discuss" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/arc=
hitecture-discuss</a><br>
</blockquote></div></div>

--000000000000c7ee5a056d002298--

