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

Justin Uberti <juberti@google.com> Wed, 04 April 2018 04:59 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 A5A6F126DED for <rtcweb@ietfa.amsl.com>; Tue, 3 Apr 2018 21:59:18 -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 xccvNQ9DhTal for <rtcweb@ietfa.amsl.com>; Tue, 3 Apr 2018 21:59:16 -0700 (PDT)
Received: from mail-vk0-x233.google.com (mail-vk0-x233.google.com [IPv6:2607:f8b0:400c:c05::233]) (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 5B57A126DC2 for <rtcweb@ietf.org>; Tue, 3 Apr 2018 21:59:16 -0700 (PDT)
Received: by mail-vk0-x233.google.com with SMTP id v134so11614247vkd.10 for <rtcweb@ietf.org>; Tue, 03 Apr 2018 21:59:16 -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=wzRNTUFjjojIqhpa0PCLclJSBKBIUNnZuBpJhlQDIrM=; b=u+ssgBNS2T10b2Jy2m6Ht3PTfLew6pR24ow6MGktxpUREo72+3dT934Cuxl/dlNmn2 /GWcD5DkRqe2Jvt7Ryp5CSdV5/bWJ2liyLVRy54Mq4YNg4Lb6oWw8Wrh9K1lwWfLeFDr i0B7mX/T0A+g6Hx4vKRwZE/wCXxRSKtKNIf9G+856+kP1k8g5NhvysD+2m/hEp4hPkbN mDJ36QaJugPi/ynAlH+b4KNJMUhwq61q+k7s1V+oZRIx40pXeQXsk5qs1lEDhlVlchKn Dw1z9ixHEkdap+SAEVD9e5V+euHUhlnT4JmrVWM638+N3TxM7J9t3kjQAEan/bK5m5V2 jQUQ==
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=wzRNTUFjjojIqhpa0PCLclJSBKBIUNnZuBpJhlQDIrM=; b=GHjMoWsxUgi2C3j4V4eywQ6U3qjRt6y9jb9Y/QSCrG4GYjN66KQP/GrFyPCOrerSLr 9jU1Gy9RiTVUpJf8vMp/9UoF1fL02xSwH7UyC/YdczZUMi7/WgwkMnNHt9p8uAAl+LKe Tl64JtNP/cs2++uVNiI8d6LmFM1EHgX0fW5d7gmYibOD69dHxJUecHIh8uCagu2CwsQw /qpzriOLYFpTyjhAoXy0IaX5qO3abTnNjnQzKKjeR2sRtI78+f4s1ZfnbQskKrPHWLFD F2Yy06H+OhA1aYHnF1WkTAK9Qxd9TckYD9wQT/Cd05Y+MCdOL6ouP89B9Nx7DAD46zrP LKkg==
X-Gm-Message-State: ALQs6tAjdAKJzFUfVzhhv20ikGJfz0ei2Q/b6lCDEQ1btmvOQiQ75j8Z 488lGZT2QYpNIYXY/ZtEC35Bu6zrlT6ODnpFDFD2Mw==
X-Google-Smtp-Source: AIpwx48LH/MlM9qs7fVQSkXgt+sGZnxv1oJr5khLttWngfnfLxUAKKmfbMKYD+e5iY4Odk28jCEUJIdJtYzucY7p0FY=
X-Received: by 10.31.158.207 with SMTP id h198mr8853131vke.165.1522817954831; Tue, 03 Apr 2018 21:59:14 -0700 (PDT)
MIME-Version: 1.0
References: <1D5B431C-801E-4F8C-8026-6BCBB72FF478@sn3rd.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> <a94ec743-96df-99a4-7e93-615c20bf722c@goodadvice.pages.de> <CAB7PXwS+8cbuTFeE4vZUX=k34m5pbvqtYOv88+bBFhg_nLRXiA@mail.gmail.com>
In-Reply-To: <CAB7PXwS+8cbuTFeE4vZUX=k34m5pbvqtYOv88+bBFhg_nLRXiA@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Wed, 04 Apr 2018 04:59:04 +0000
Message-ID: <CAOJ7v-1BcEMgr=U5LXQSaAezhC_8S7g4X91scE7LS_k5hqik1A@mail.gmail.com>
To: andyhutton.ietf@gmail.com
Cc: Philipp Hancke <fippo@goodadvice.pages.de>, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="001a1142793a4208800568feaf85"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/61IRZJ6On9bqHz1qU8c1kw7yR7o>
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, 04 Apr 2018 04:59:19 -0000

On Tue, Apr 3, 2018 at 7:56 AM Andy Hutton <andyhutton.ietf@gmail.com>
wrote:

> On 3 April 2018 at 14:17, Philipp Hancke <fippo@goodadvice.pages.de>
> wrote:
> > Am 03.04.2018 um 11:14 schrieb T H Panton:
> >>
> >> 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/
> >
> >
> >
> > It turned out the issue in this case is
> > a) browser extensions that add a proxy server calling themselves a "VPN"
> > b) said browser extensions being unaware of the Chrome Extension API to
> set
> > mode 4 which prevents UDP from being used if a proxy server is set.
> >
>
> The reference to mode 4 forced me to read that part of the draft again
> and now I have a question:
>
> In the description of mode 4
> *https://tools.ietf.org/html/draft-ietf-rtcweb-ip-handling-06#section-5.2)
> what is meant by "or the WebRTC implementation does not support UDP
> proxying"?
>
> Does "UDP Proxying" refer to the return proxy mechanism, a network
> specific TURN server, or something else?
>

UDP proxying refers to any technique that allows the browser to tunnel UDP
through a proxy, which would include RETURN, and possibly other types of
proxies (QUIC?) in the future.