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

Justin Uberti <juberti@google.com> Sat, 31 March 2018 22:27 UTC

Return-Path: <juberti@google.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 3075F120725 for <rtcweb@ietfa.amsl.com>; Sat, 31 Mar 2018 15:27:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 4xNMMDEDY4_u for <rtcweb@ietfa.amsl.com>; Sat, 31 Mar 2018 15:27:04 -0700 (PDT)
Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::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 65E0C1200F1 for <rtcweb@ietf.org>; Sat, 31 Mar 2018 15:27:04 -0700 (PDT)
Received: by mail-vk0-x230.google.com with SMTP id v134so6628784vkd.10 for <rtcweb@ietf.org>; Sat, 31 Mar 2018 15:27:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sRv2ECwFkzBtObJBjQMzQQew96r7X+6nzRKUDp9VgfQ=; b=RHfJfVTRGiXd+dpTCc1w+PINjfUEL+0wIT4+a1ppd8bHnfCVjrwt9nLrHaTJE4csLL cZjs7JTWQUMad7d4qaBP848yk/JhcdGgoI+5ZmG7o2eFcVG+FaZic54kfAQ3uDc2kdsQ zzYndnB/IaKk6lvX8GCHx0t8A7eU155O7rO2KCvtKZD15Acj2kkJi9uPtUrZk2DBZh3c wdb5Flh924hyoXplwvQk8qUWY0eetvemgYiBTsF3lqUF0PJxsKcSPgCjfW+yP2tu8RMW HVXrJp6LUkhnCXvp4s/Muj5AV1LwhJPa/SACGB8pEy81uIlbAF3DDXb+Iy5CtTe9s9fx sUOg==
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=sRv2ECwFkzBtObJBjQMzQQew96r7X+6nzRKUDp9VgfQ=; b=q1Vxa+L7iasmhL9EBMjdqYEaaO1lKMLv1DnOtk+wrLvUHSFDDNcLl5Tr7nt/j6vJTJ HIOk7IhS5qtmZNk8VkzUiuKr4tEUHff1DDdSPa0FFuMzISf1yrGseMplwkrNK9Vaqc9+ EqGuCYVq2Pus80zhLun2Cl2nwhAhWJjOwWesoCjne0LOoMFNr89HQXFafBQlZv3qpA0T D3EotFXZDgtEwRD5UwMGeyxJ9cekJ2J8+vb91fNro+jrVt00Yi5VlClRamLoeFcOOvMw OhLarEUtgEGtszaWevkDPPcGGzcJfEI+JW2HFWK7Yaw/J1PSqVWIFS5PpbzpiDgiHYOc I0dQ==
X-Gm-Message-State: ALQs6tBreJsGqbapXd0K3zlrz7Qe9LLHdUXY0qDfxwHGlkYL3EnXCNKY /8kZTeT/6b7tvw6ZmU/heeL+ZzBQ2OLtllDm1Iamqy7J
X-Google-Smtp-Source: AIpwx4+V36hM87N6IlMsP0UfpXKUHbM+cw/exMQ3t84SyeUeJDg1XPnVmrkK7oZliHb7WLhDwGeu9CR/9vnslEDfLBs=
X-Received: by 10.31.252.68 with SMTP id a65mr2411829vki.78.1522535222818; Sat, 31 Mar 2018 15:27:02 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <b5d323ac-2205-2aee-05c9-f270e80215f5@gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Sat, 31 Mar 2018 22:26:50 +0000
Message-ID: <CAOJ7v-0+hr-NddbLCwgjkfyEFEzoLYW8BcE5OYZ+HUiqDRnarg@mail.gmail.com>
To: Lennart Grahl <lennart.grahl@gmail.com>
Cc: Sean Turner <sean@sn3rd.com>, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c14c6cc1e04060568bcdb47"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/rUzrMzDYvW92mNl3tTCBQJZ0KSs>
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: Sat, 31 Mar 2018 22:27:06 -0000

As stated before, this is not a problem unique to web browsers. That is, by
installing a mobile application, you implicitly allow it to use all of your
network interfaces. As such, trying to design browser mechanisms for
networking consent seems like misdirected effort.

Perhaps the key issue here is the word 'consent'. If we replaced this with
some notion of 'trust', i.e., that the user has specifically engaged with
this app with the intent of having a communications session, maybe that
provides a way out, as one can easily claim that installed mobile
applications and web apps with gUM rights are 'trusted'.

On Sat, Mar 31, 2018 at 3:18 AM Lennart Grahl <lennart.grahl@gmail.com>
wrote:

> I really don't have a good suggestion other than being completely
> honest: "Hey user, I want to establish a direct connection - is that
> okay for you? Oh, and here is a help page that will tell you what impact
> this may have on your privacy..."
>
> These permission requests don't have to be mutually exclusive either.
> The above request could also be embedded inside the permission request
> for getUserMedia to avoid multiple requests:
>
> Camera to share:
> [WebCam 3000 |v]
> :WebCam 3000   :
> :WebCam 4000   :
>
> Direct connection: (?) <-- "help" button
> [No (Default)                    |v]
> :Yes                               :
> :Yes, but hide private addresses   :
> :No (Default)                      :
> :No, and force using a proxy       :
>
> [x] Remember the decision for this page
>
> [Don't allow] [Allow]
>
> Cheers
> Lennart
>
> On 31.03.2018 00:12, Sean Turner wrote:
> >
> >
> >> On Mar 29, 2018, at 23:48, Lennart Grahl <lennart.grahl@gmail.com>
> wrote:
> >>
> >> I'm fine with the modes, I don't have a strong opinion on whether or not
> >> an IETF document should include some form of "consent". But I do have a
> >> problem with the suggestion to use getUserMedia. Can we maybe remove it?
> >
> > As the draft shepherd, I’m trying to figure out how to draw this WGLC to
> a close all in the hopes that we can help each other get this RTCweb WG
> ship docked.
> >
> > As far as dropping the getUserMedia suggestion, I’m a little hesitant to
> just drop it at this late date.  That suggestion has been in the draft
> since October 2016 and it’s stood the test of a couple of WG reviews; not
> last calls mind you but there’s been plenty of time for folks to say get
> that outta there.  And technically, it’s just a suggestion with no
> normative language.  So … maybe a happy middle ground is to have another
> suggestion so that there’s more than one potential mechanism?
> >
> > spt
> >
>