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)]
Shivan <shivankaul.1993@gmail.com> Wed, 02 May 2018 17:17 UTC
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, 02 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
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 > >>>>> > >> > > > >
- [HT-rt] [execd@iab.org: Call for Comment: <draft-… Stephane Bortzmeyer
- Re: [HT-rt] [execd@iab.org: Call for Comment: <dr… Shivan
- Re: [HT-rt] [execd@iab.org: Call for Comment: <dr… Niels ten Oever
- Re: [HT-rt] [execd@iab.org: Call for Comment: <dr… Amelia Andersdotter
- Re: [HT-rt] [execd@iab.org: Call for Comment: <dr… Niels ten Oever
- Re: [HT-rt] [execd@iab.org: Call for Comment: <dr… Amelia Andersdotter
- Re: [HT-rt] [execd@iab.org: Call for Comment: <dr… Niels ten Oever
- Re: [HT-rt] [execd@iab.org: Call for Comment: <dr… Amelia Andersdotter
- Re: [HT-rt] [execd@iab.org: Call for Comment: <dr… Shivan
- Re: [HT-rt] [execd@iab.org: Call for Comment: <dr… Niels ten Oever
- Re: [HT-rt] [execd@iab.org: Call for Comment: <dr… Shivan