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

Ted Hardie <ted.ietf@gmail.com> Wed, 07 March 2018 22:14 UTC

Return-Path: <ted.ietf@gmail.com>
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 D845512D958 for <rtcweb@ietfa.amsl.com>; Wed, 7 Mar 2018 14:14:13 -0800 (PST)
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 ALpRjxoxGxgQ for <rtcweb@ietfa.amsl.com>; Wed, 7 Mar 2018 14:14:11 -0800 (PST)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::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 91DD3127419 for <rtcweb@ietf.org>; Wed, 7 Mar 2018 14:14:11 -0800 (PST)
Received: by mail-oi0-x22a.google.com with SMTP id x12so2889293oie.13 for <rtcweb@ietf.org>; Wed, 07 Mar 2018 14:14:11 -0800 (PST)
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=P1T2lha+SjTM67VnubA+gemcF8CVpJWT5UYVW/7QXI0=; b=DDdRbSqYHHFHQC+x0k9CWg/FHa8iHsxnaSSeT563aK/x8OpgOT7p2xtYnjigiiLcTT kAAk+nY15ZX4UgWylRgZQUK1+XVnp7nckfmDk6c5dn7fW4G1s14s66ZPVbR1f2moj7lD MnUNJot2sdgAYk8SueweT+uBT19Fw+eVXNKJ21zKRgjB5nAr9GELKNni/wUNWnWIwK2Z 0hsBFJrJ3uCFjmGb7FXiyxxy2r94qvnYbw0KCBUi5WOJ4CNli6YLPqR+741t0VQNCy2n AbtWFNdphyKLbSag5ps9usLAadmjUwoJn9VEpYZ795DxNGfAlgjLOsKqYlApU3KYTYw/ /qwA==
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=P1T2lha+SjTM67VnubA+gemcF8CVpJWT5UYVW/7QXI0=; b=Fmx1/c+kIUWh5E4kDckGHTbVYePzbtBYsa5/THXJvRN056yeNDYNIFjAqZt7XSN6sZ 0Qyzi1s2Bg+3bXmA037FVkzUeeN/eReaWWTSMbvFfKd7SXz2U0q00g1i6ez+EQ/4EY4G RHWAOcyvpauJTlCRerWG2UAzjgTedvhWucYt5dA23CbcA5Q9KX/BLMDMdISbiV6bkFYh YVFQ0K5RNudNocILVB4PVHNv9BAX1x9VPT7xH2RMaYa4CFWEG9NfWBR5gjAhl54ljAyc BwJ2TRnox5S/v8a+wqmNLF0QN6yBpUc/Z8VDcbBjBoMKhC1gC3mZdK8/313rdeDiPful gWtw==
X-Gm-Message-State: AElRT7G8m9BznzByddwkANmDOk6ZYVGktCL2LJseOs0D/6QunbEsZD1O Y69WRNWoEqHVoiUilFU3aaZARn8H5pYE36LONlw=
X-Google-Smtp-Source: AG47ELvsjP8k6cbPsGop6sLCHNUBrN63cLiLNTSc0j/dmLdmAorUcEzGyl0yF53KIebeJYL/vGBZwhE3LeeWBIJeB9Q=
X-Received: by 10.202.235.12 with SMTP id j12mr14956859oih.284.1520460850691; Wed, 07 Mar 2018 14:14:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.7.27 with HTTP; Wed, 7 Mar 2018 14:13:40 -0800 (PST)
In-Reply-To: <403713b4-31d4-9085-d639-d3f60935ed5a@cs.tcd.ie>
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>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 07 Mar 2018 14:13:40 -0800
Message-ID: <CA+9kkMBPUNOuMzM+fMtoFAAVbCD-Vd0Y1uViZmUW-Xi7iWPg5A@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Justin Uberti <juberti@google.com>, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="001a113cc70ce684a70566d9e015"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/qho7UtTRrTtDh0OMtLN1GTdtjC4>
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 22:14:14 -0000

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.

If you know of a different term of art here that would be similarly
well-understood, I would be glad to know of it.  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
>
>