IETF Logo Mail Archive

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

Cullen Jennings <fluffy@iii.ca> Tue, 03 April 2018 20:52 UTC

Return-Path: <fluffy@iii.ca>
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 8DDCD12D873 for <rtcweb@ietfa.amsl.com>; Tue, 3 Apr 2018 13:52:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 kjPuSmCepCV0 for <rtcweb@ietfa.amsl.com>; Tue, 3 Apr 2018 13:52:39 -0700 (PDT)
Received: from smtp121.iad3a.emailsrvr.com (smtp121.iad3a.emailsrvr.com [173.203.187.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DD3912706D for <rtcweb@ietf.org>; Tue, 3 Apr 2018 13:52:39 -0700 (PDT)
Received: from smtp16.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp16.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 66C6D5BCA; Tue, 3 Apr 2018 16:52:36 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp16.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 03D5658A3; Tue, 3 Apr 2018 16:52:35 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.91] (S0106004268479ae3.cg.shawcable.net [70.77.44.153]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Tue, 03 Apr 2018 16:52:36 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_33F95179-B256-4E28-8E6B-45D6CB7729EA"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <B39901B1-6DB1-4856-A6D8-BEF945766361@westhawk.co.uk>
Date: Tue, 03 Apr 2018 14:52:34 -0600
Cc: RTCWeb IETF <rtcweb@ietf.org>
Message-Id: <F806B6D5-B1EA-4CE9-BEF1-261598DA5FFF@iii.ca>
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> <CAOJ7v-0+hr-NddbLCwgjkfyEFEzoLYW8BcE5OYZ+HUiqDRnarg@mail.gmail.com> <0dee004d-159a-a9be-a0b8-ecbfd4204d72@gmail.com> <03D3C806-B93F-4CD0-B57B-507B07E869A0@westhawk.co.uk> <540AF425-A798-41BB-8C22-9F697DF46117@westhawk.co.uk> <562af54d-9fcd-48c3-5709-6c8fa469e995@cs.tcd.ie> <8D1E1BA7-9BDE-4302-A698-B1C3E4686F12@westhawk.co.uk> <8d528cc5-84d9-c0cf-be5a-19e836f7ca89@cs.tcd.ie> <CABcZeBPXZ54xf-H8wCrmEF1_2F43OXRaoiHNsobmEgGtLiC+6A@mail.gmail.com> <443FC3E5-891C-49BB-90A1-C3139D3C0655@iii.ca> <B39901B1-6DB1-4856-A6D8-BEF945766361@westhawk.co.uk>
To: Tim Panton <thp@westhawk.co.uk>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/_LC63Glrv_yLFZwLGxm7t501Q2Y>
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: Tue, 03 Apr 2018 20:52:41 -0000


> On Apr 3, 2018, at 3:14 AM, T H Panton <thp@westhawk.co.uk> wrote:
> 
> In case anyone thinks this issue will go away if we ignore it:
> 
> https://www.theregister.co.uk/2018/03/29/almost_a_quarter_of_vpns_tested_leak_ip_addresses/ <https://www.theregister.co.uk/2018/03/29/almost_a_quarter_of_vpns_tested_leak_ip_addresses/>
> 
> T.

I’d phrase that as 77% of VPNs are not broken and here is a simple WebRTC test to find out if your VPN is totally broken. Note that if it is broken for WebRTC, is is also broken for non WebRTC apps like Skype. I will not that since that article was published, the guys that did the tests has updated the data at https://voidsec.com/vpn-leak/ and now only 83% of the VPN are not broken. It clear that VPN providers are fixing this problem.

v2.23.0 | Report a Bug | By Email