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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 07 March 2018 23:04 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 CAE3A1242F5 for <rtcweb@ietfa.amsl.com>; Wed, 7 Mar 2018 15:04:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level:
X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 oGd9shSCwrEK for <rtcweb@ietfa.amsl.com>; Wed, 7 Mar 2018 15:04:45 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3466120727 for <rtcweb@ietf.org>; Wed, 7 Mar 2018 15:04:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 8EB0CBE5D; Wed, 7 Mar 2018 23:04:43 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2pCsvKLsT2G5; Wed, 7 Mar 2018 23:04:39 +0000 (GMT)
Received: from [10.244.2.138] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 8ED07BE5B; Wed, 7 Mar 2018 23:04:39 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1520463879; bh=SSVm+6LnsMLbzr0GrCoEbU3HQdrP6Arx+N8IR4EbE7I=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=x64onNThalJwXnJK9DIvrk9wzQi9hFHZfMgQiR3jsB1N5smXE/T+vZ1dX2po01E+t 0fpB++JFryB7EyUS5yO1vSqMPwD4098eCSmI/zZqP4YeInSQg+HIUQp37oHbBn9Kg3 wgEukVfTIX4+Xo6A7pjq6OeBkHllD8nnE0nZ+WzM=
To: Ted Hardie <ted.ietf@gmail.com>
Cc: Justin Uberti <juberti@google.com>, RTCWeb IETF <rtcweb@ietf.org>
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> <CA+9kkMBPUNOuMzM+fMtoFAAVbCD-Vd0Y1uViZmUW-Xi7iWPg5A@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=5BB5A6EA5765D2C5863CAE275AB2FAF17B172BEA; url=
Message-ID: <dc009bb5-8b3d-f4f5-8c6c-aad2ef4a8e32@cs.tcd.ie>
Date: Wed, 07 Mar 2018 23:04:38 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CA+9kkMBPUNOuMzM+fMtoFAAVbCD-Vd0Y1uViZmUW-Xi7iWPg5A@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="nHS5qQGTDUpXaXutaZrVlXFVdws5QnrYB"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/jBdXYys4MILMdaLcN7zEje8gX-g>
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: Wed, 07 Mar 2018 23:04:48 -0000

Hiya,

On 07/03/18 22:13, Ted Hardie wrote:
> On Wed, Mar 7, 2018 at 1:12 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
> wrote:
> 
>>
>> Hiya,
>>
>> To also be clear: my main objection is to the term consent being
>> used at all. The stuff below isn't that big a deal, though would
>> change if the WG did drop the idea of "consent" supposedly being
>> a real thing.
>>
>>
> So, while I am sympathetic (just generally, really, not just to this), I
> think "consent" is basically a term of art in the web world and that its
> use in the document is consistent with the more general use.
Yes. And there's IMO plenty of reason to not want to be consistent
with that general (ab)use. If we start down that road, I worry that
we'll end up with the moral equivalent of "you looked at my web-page
(possibly whilst ignoring 300 pages of legal crap); therefore you
have already agreed to my T&Cs" which'd be an even worse thing if
attempted/applied at lower layers. To me, this usage matches that
(slightly exaggerated) anti-pattern.

> If you know of a different term of art here that would be similarly
> well-understood, I would be glad to know of it.  

Fair point and a fair ask.

I'll think some more about it, but TBH, I doubt I could come up
with something with a chance of garnering WG consensus. (I don't
think this is just terminology btw - I suspect with any better
term, the modes defined would also have to change.)

If I get inspired, I'll post something. (Hopefully someone smarter
than I and with more WebRTC/STUN clue will get there first:-)

If I don't, and nobody else does, it's fair to consider me in the
rough.

Cheers,
S.

> It may also be an
> interesting project to create such a term.  But I don't think the document
> should wait on that.
> 
> 
> 
>> On 07/03/18 20:47, Justin Uberti wrote:
>>> To be clear, the MUST does not say that all interfaces MUST be used if
>>> consent is given, rather the converse, that you MUST only use all
>>> interfaces if there is consent.
>>
>> It's unclear to me that there's any practical difference there.
>> Are there any implementations that do something else? (Apologies
>> if that's clear to everyone else:-)
>>
>>> In addition, while gUM consent is given as an example, it is not
>> normative.
>>>
>>>    Mode 1 MUST only be used when user consent has been provided.  The
>>>    details of this consent are left to the implementation; one potential
>>>    mechanism is to tie this consent to getUserMedia consent.
>>
>> Sure. OTOH, IIUC, that is what's done in web browsers so it kind
>> of really is normative, in practice. Again, apologies if there
>> are other things done in browsers.
>>
>> If I recall correctly, it was not made normative because mobile
> applications might use this using advice outside browser contexts.  I can't
> find an immediate citation to that, though, so it may be a convenient
> reconstruction rather than an accurate memory.
> 
> Ted
> 
> 
> 
>> S.
>>
>>
>>>
>>>
>>>
>>> On Wed, Mar 7, 2018 at 12:12 PM, Stephen Farrell <
>> stephen.farrell@cs.tcd.ie>
>>> wrote:
>>>
>>>>
>>>> Hiya,
>>>>
>>>> On 07/03/18 19:49, Sean Turner wrote:
>>>>> All,
>>>>>
>>>>> This is the WGLC for the "WebRTC IP Address Handling Requirements”
>>>>> draft available @
>>>>> https://datatracker.ietf.org/doc/draft-ietf-rtcweb-ip-handling/.
>>>>> Please review the draft and send your comments to this list by
>>>>> 2359UTC on 30 March 30 2017.
>>>>
>>>> I've raised this previously, so this is, I guess, mostly just
>>>> for the record, and I'll likely still be in the rough...
>>>>
>>>> I continue to think it is a bad idea to use the term "consent"
>>>> at all, and especially coupled with getUserMedia and with mode
>>>> 1 having a MUST for using all interfaces based on what I think
>>>> is such a bogus concept. There is, IMO, no valid way in which a
>>>> person can fairly be considered to have consented to any of this.
>>>> I think entwining IETF specifications in the tangled web of web
>>>> "consent" (so called) is going in exactly the wrong direction.
>>>>
>>>> Cheers,
>>>> S.
>>>>
>>>>
>>>>>
>>>>> Thanks, C/T/S _______________________________________________ rtcweb
>>>>> mailing list rtcweb@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/rtcweb
>>>>>
>>>>
>>>> _______________________________________________
>>>> rtcweb mailing list
>>>> rtcweb@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/rtcweb
>>>>
>>>>
>>>
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>>
>