Re: [rtcweb] Please require user consent for data channels

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Sun, 19 July 2015 07:42 UTC

Return-Path: <sergio.garcia.murillo@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E1E21A1A8A for <rtcweb@ietfa.amsl.com>; Sun, 19 Jul 2015 00:42:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001] autolearn=ham
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 Mnw9wG5njFtU for <rtcweb@ietfa.amsl.com>; Sun, 19 Jul 2015 00:42:00 -0700 (PDT)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (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 1E06B1A00B8 for <rtcweb@ietf.org>; Sun, 19 Jul 2015 00:42:00 -0700 (PDT)
Received: by iggf3 with SMTP id f3so62782824igg.1 for <rtcweb@ietf.org>; Sun, 19 Jul 2015 00:41:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2szdZ4f/KMo9KzEq2BkCra+4SgngTxT5SzEjMGT+b3Y=; b=WjB9VNT/NMd+kWYzj6JKKQ8gDc+grNWTQZBWYUtht6jBytwCWr5Jh6wo4dcTLitiJG nVgN+zte8GYoH1cX84TX6OrfRv60ZGfHZhLxER/vriIEbNjrGaAph3aU2/MhBQ3EU2RG nIchwAJXIzb4X+uNrgbCbjFyQQiaRLyl3NRGYPzHXKcy/QCmqeTOdZTC59Ecwmppli9v R+9AInfseKmRIO/44GWha2WDfBIPU/wtNzqGqg3nVsNkT7j8YtqEqvkB71XJUbGbzPUo GCYVKbPa6U/3Bzw3kZ2+9M4/na+R4mLlNbNNCWAOnB9eya7dRLYY0SwpGVX6u7rf/BJo DF1Q==
MIME-Version: 1.0
X-Received: by 10.50.142.9 with SMTP id rs9mr6664480igb.17.1437291719598; Sun, 19 Jul 2015 00:41:59 -0700 (PDT)
Received: by 10.107.168.195 with HTTP; Sun, 19 Jul 2015 00:41:59 -0700 (PDT)
Received: by 10.107.168.195 with HTTP; Sun, 19 Jul 2015 00:41:59 -0700 (PDT)
In-Reply-To: <CAOJ7v-1cB47793yH+-mWrdU9rNqX=+HadZpbRf3PezXspqLm1A@mail.gmail.com>
References: <CA+65OspMD_PVjk0BXh7t4LtjmFDcDatoeNjFQOO_OVtC-Br+OA@mail.gmail.com> <CAOJ7v-0UBGtP0-atxP7X4OTj-H6Lost5o42aAS65mA6CEqcQsw@mail.gmail.com> <CA+65OsrhXHK+cRAFLCZFt+34vr8eRhj+CN3DgznUBfSwmWYggw@mail.gmail.com> <CAOJ7v-24VCW6kkn7LOLkqZzhYEU0r=nmd_F7Zns1rnyqKN6xAg@mail.gmail.com> <55A95364.2070806@gmail.com> <CAOJ7v-3t9BQabR2e4EHs4G0Sec4sU9DFC2aiSXXYrat+an+RYg@mail.gmail.com> <55A96DA3.1040907@gmail.com> <CAOJ7v-1ui7349NzK6NZNRHPbnHWZajctk4cDgMKqRZSv47EYdA@mail.gmail.com> <55A9860D.8030903@gmail.com> <CAOJ7v-3LGd32rnpFVW_U0s3+iVaJXsL4vt_YAo=cyp6YyOArdw@mail.gmail.com> <55A99148.1040105@gmail.com> <CAOJ7v-1cB47793yH+-mWrdU9rNqX=+HadZpbRf3PezXspqLm1A@mail.gmail.com>
Date: Sun, 19 Jul 2015 09:41:59 +0200
Message-ID: <CA+ag07aEQKwYPB_TaCqKfdUCQs-xZQ=cSx2EcO0ZEdAMw+PHyQ@mail.gmail.com>
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
To: Justin Uberti <juberti@google.com>
Content-Type: multipart/alternative; boundary="001a11c2ff1c62ab48051b358ecd"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/xRqk9INxqu8QcvaKgvBBDrK7O08>
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Please require user consent for data channels
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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, 19 Jul 2015 07:42:01 -0000

El 18/7/2015 2:19, "Justin Uberti" <juberti@google.com> escribió:
>
> Sometimes this will be desirable: imagine someone working from home who
wants to connect to their corp VPN, but wants to have their video
conferencing traffic not go through the VPN. Sometimes this will not be
desirable, i.e. when the VPN is being used for privacy. This makes picking
a perfect default setting difficult, although we have some ideas that we
are exploring.

Most probably you already have thought about it, but how about adding an
interface black/white list for webrtc in privacy settings? IIRC chrome was
already skipping some hardcoded virtual interface names.

Best regards
Sergio