IETF Logo Mail Archive

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

Matthew Kaufman <matthew@matthew.at> Mon, 13 July 2015 15:16 UTC

Return-Path: <matthew@matthew.at>
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 AFF961B2BDB for <rtcweb@ietfa.amsl.com>; Mon, 13 Jul 2015 08:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level:
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_05=-0.5] 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 iQl13venuG8c for <rtcweb@ietfa.amsl.com>; Mon, 13 Jul 2015 08:16:38 -0700 (PDT)
Received: from mail.eeph.com (mail.eeph.com [IPv6:2001:470:826a:d2::3]) by ietfa.amsl.com (Postfix) with ESMTP id DD5281B2BC3 for <rtcweb@ietf.org>; Mon, 13 Jul 2015 08:16:12 -0700 (PDT)
Received: from [IPv6:2001:470:826a:d0:d5fe:6e06:c62e:6418] (unknown [IPv6:2001:470:826a:d0:d5fe:6e06:c62e:6418]) (Authenticated sender: matthew@eeph.com) by mail.eeph.com (Postfix) with ESMTPSA id BAF312A3509; Mon, 13 Jul 2015 08:16:12 -0700 (PDT)
Message-ID: <55A3D63D.1020108@matthew.at>
Date: Mon, 13 Jul 2015 08:16:13 -0700
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Daniel Roesler <diafygi@gmail.com>, Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
References: <CA+65OspMD_PVjk0BXh7t4LtjmFDcDatoeNjFQOO_OVtC-Br+OA@mail.gmail.com> <55A22A1B.4000202@gmail.com> <CA+65OspKCvwFh0GebiuUrhdtaL9zxYKLw04HdKEfewLCWQ+ZpQ@mail.gmail.com>
In-Reply-To: <CA+65OspKCvwFh0GebiuUrhdtaL9zxYKLw04HdKEfewLCWQ+ZpQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/45hKMYghJ_vfp5SbAnCNqeiwb1c>
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: Mon, 13 Jul 2015 15:16:40 -0000

On 7/12/2015 12:19 PM, Daniel Roesler wrote:
> Thanks very much for the responses! Going to try and address both inline below.
>
> On Sat, Jul 11, 2015 at 9:26 PM, Matthew Kaufman <matthew@matthew.at> wrote:
>> On the IPv6 Internet, the IP address you use to reach the web site is almost
>> certainly the same as your "local" IP address. There's no additional
>> information exposed by allowing an application to discover that information
>> directly via JavaScript.
>>
>> The IPv4 Internet is essentially out of addresses and in the process of
>> being retired. I don't believe there's any reason at this point to disable
>> functionality in order to improve compatibility with this legacy network.
>>
> I disagree with this sentiment. IPv4 will be around for many more
> years

Maybe.

> and many ISPs still do not assign their customers IPv6
> addresses.

Only ones that don't expect to stay in business.

>   If IPv6 is replacing IPv4 so readily, why not only offer
> WebRTC through IPv6?

I would support such a proposal.

> It's a huge double standard to say that we won't
> support privacy issues of one network while at the same time
> supporting connectivity though it.

IPv6 won't have that "privacy", so there's no reason for IPv4 users to 
continue to expect such.

Matthew Kaufman

v2.23.0 | Report a Bug | By Email