Re: [rtcweb] WGLC for draft-ietf-rtcweb-ip-handling

westhawk <thp@westhawk.co.uk> Sun, 01 April 2018 12:51 UTC

Return-Path: <thp@westhawk.co.uk>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F1D4120724 for <rtcweb@ietfa.amsl.com>; Sun, 1 Apr 2018 05:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 9KxQACYaOTPT for <rtcweb@ietfa.amsl.com>; Sun, 1 Apr 2018 05:51:32 -0700 (PDT)
Received: from smtp002.apm-internet.net (smtp002.apm-internet.net [85.119.248.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 219661200E5 for <rtcweb@ietf.org>; Sun, 1 Apr 2018 05:51:31 -0700 (PDT)
Received: (qmail 32680 invoked from network); 1 Apr 2018 12:51:29 -0000
X-APM-Authkey: 255286/0(159927/0) 114
Received: from unknown (HELO zimbra003.verygoodemail.com) (85.119.248.218) by smtp002.apm-internet.net with SMTP; 1 Apr 2018 12:51:29 -0000
Received: from localhost (localhost [127.0.0.1]) by zimbra003.verygoodemail.com (Postfix) with ESMTP id A552318A0B69; Sun, 1 Apr 2018 13:51:29 +0100 (BST)
Received: from zimbra003.verygoodemail.com ([127.0.0.1]) by localhost (zimbra003.verygoodemail.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id YYDphn5iGzUh; Sun, 1 Apr 2018 13:51:29 +0100 (BST)
Received: from [192.67.4.84] (unknown [192.67.4.84]) by zimbra003.verygoodemail.com (Postfix) with ESMTPSA id 81C9318A067F; Sun, 1 Apr 2018 13:51:29 +0100 (BST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: westhawk <thp@westhawk.co.uk>
In-Reply-To: <562af54d-9fcd-48c3-5709-6c8fa469e995@cs.tcd.ie>
Date: Sun, 01 Apr 2018 13:51:28 +0100
Cc: RTCWeb IETF <rtcweb@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8D1E1BA7-9BDE-4302-A698-B1C3E4686F12@westhawk.co.uk>
References: <1D5B431C-801E-4F8C-8026-6BCBB72FF478@sn3rd.com> <63282b84-4493-3fcb-a95f-4afe17d96bb6@cs.tcd.ie> <CAOJ7v-1gTq+EEjb+-q-T-pABBW--rpNGegoj_d2_7f7AKGksCA@mail.gmail.com> <403713b4-31d4-9085-d639-d3f60935ed5a@cs.tcd.ie> <CAOJ7v-0ED-FK=JmSxBJYfM=PCdgY6kmbiq6aFLcP7OXugG07EA@mail.gmail.com> <e6938f7d-542d-736b-0a3d-9269d7dd06e5@cs.tcd.ie> <CAOW+2dv1ORz2tEkgDTvdM1DtgyOdgXqKU30T4QhLAp1NT+rirg@mail.gmail.com> <CAOJ7v-0tCcg3FdzyfSJ6Y3JaH-TivFf-Sey6+tD8BANJKsjqtQ@mail.gmail.com> <1fceb3c4-35f3-34f7-de1d-79d5805e6d22@gmail.com> <9517D601-D3E8-46E1-94E5-7EC29FD6319B@sn3rd.com> <b5d323ac-2205-2aee-05c9-f270e80215f5@gmail.com> <CAOJ7v-0+hr-NddbLCwgjkfyEFEzoLYW8BcE5OYZ+HUiqDRnarg@mail.gmail.com> <0dee004d-159a-a9be-a0b8-ecbfd4204d72@gmail.com> <03D3C806-B93F-4CD0-B57B-507B07E869A0@westhawk.co.uk> <540AF425-A798-41BB-8C22-9F697DF46117@westhawk.co.uk> <562af54d-9fcd-48c3-5709-6c8fa469e995@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/7vHb6vDRW7OsGi6HdRwTIg11tPk>
Subject: Re: [rtcweb] WGLC for draft-ietf-rtcweb-ip-handling
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Apr 2018 12:51:34 -0000


> On 1 Apr 2018, at 12:51, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> 
> Hiya,
> 
> On 01/04/18 12:32, T H Panton wrote:
>> - I'm no GDPR specialist, but I think adding 'informed' above may be wise.
> 
> Luckily, I'm also not a GDPR specialist:-)

Giving literal consent is somewhat frowned on these days - hence ‘informed'.

> 
> But I think adding "informed" takes this further from reality and so is
> worse. (Further from reality in terms of me just not believing that ICE
> is understandable for a random user, and therefore consent of any kind
> to doing iCE, isn't possible, so informed consent is even less
> possible;-)
> 

Ah, that’s where we disagree. We don’t have to explain ICE -
(frankly almost no-one understands ICE
not even those of us who have implemented it.)
Just like we don’t explain the detailed risks of giving camera permissions.

But I do think we can give a better hint at what the area of risk is, fundamentally:
"do you trust this website with your (network) location?”

Whilst some of the detailed risks are shared with
“do you want to use your camera?” Not enough of them are IMHO.


> In general I'm not sure wordsmithing will help here - I reckon those of
> us in the rough (well, me at least), have a fundamental problem with
> the current state of implementations and with the basic idea in the
> draft so I don't think any simple wording change can solve that. (I'm
> not saying that to be difficult but to avoid us all wasting time
> thinking we can solve the problems via wordsmithing.)

Mmm, I think we differ, I’d rather give wordsmithing a try before we go back to square 1.

T.

> 
> Cheers,
> S.
> <0x5AB2FAF17B172BEA.asc>