IETF Logo Mail Archive

Re: [rtcweb] draft-ietf-rtcweb-ip-handling: Mode 2 and VPN scenarios

James Pearce <james@jamesandjo.com> Wed, 15 November 2017 09:48 UTC

Return-Path: <james@jamesandjo.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 98658127337 for <rtcweb@ietfa.amsl.com>; Wed, 15 Nov 2017 01:48:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jamesandjo-com.20150623.gappssmtp.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 Gvj8QpxbTpw0 for <rtcweb@ietfa.amsl.com>; Wed, 15 Nov 2017 01:47:58 -0800 (PST)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::231]) (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 D0B8B124205 for <rtcweb@ietf.org>; Wed, 15 Nov 2017 01:47:58 -0800 (PST)
Received: by mail-qt0-x231.google.com with SMTP id u42so10074464qte.7 for <rtcweb@ietf.org>; Wed, 15 Nov 2017 01:47:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jamesandjo-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=P6oBBJX+g1xVn7u5fUdI4MzAzKRvLc8bHK4XmWgRlYw=; b=PwDgXICDlb//061GzBqz+B1UcuMdQNqhHOBNlsMpz57ScjOCMwqcLqqnSbyGhLZVd6 5Ngbb5100TX6wrsdB3H44o4dS33v67ECKwX8RKA/tE3iP7XI0jdhXAYSO6ocSBNzfI04 unQz4U2FSllTnaa6zKya+nkG/Yf7N1hnMP7V7qF+9nRPiQCjZFdrXRKD4u54fSkGPUCQ NKPJpyYErMz2wVK3HvFrbe9HtlkBb2geniKpO9SOoiA5PabZUB2rcHT/nJl3cvfNPpBx Gpt+Uz3q9X/a6BRF5w2iPmVEbgXC4twIjiUJCr/zy0uU9TnpT004vWf65ccVehC/Dh4T 3qVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=P6oBBJX+g1xVn7u5fUdI4MzAzKRvLc8bHK4XmWgRlYw=; b=aQsg+aJElvglJFAgAGBVXprapCEC8RdtnW9MTBcpUrNSjWaNSNbG24rF/fK3mKFkV3 iYg78gP99h2YxYvtetSCzmWjC7DuwcLuBSptSGFRjBROgoLO7qKzYtvyW3B56xm8r7zg JcbtmHTX7rcbohuhlykH0LGTC8pHUSK+q3epSASAMbvkllRlXr1EyBIy5XSbdmsnBgnB YgSq/OSD5GPQYNJ7D8768Nosu17nTRfyEiSM6p/o8kVm/cg3g1lLl1aeWcS/nwBnIvOM FHJznDj8VrKU9932PsabB5D5TomHi10N6Ig4rPHMV0KRmNKeJRJ9CEUns1oh5bCOeqM5 ooDA==
X-Gm-Message-State: AJaThX4l8MSBLfa8oC4SxDBgM+NQUSPX8KGnFQPhTDK7yrNeTevGyW41 132keooe00Yt27BwQBv59aJO/tR6K2QrirXhoq8JWg==
X-Google-Smtp-Source: AGs4zMZatHvwcae375pE5ewicdY656cbxGs6j8pWr+m1UtbAAALcj9zApZrxztqAoYORewnVV5uo2oHSoavA7AW8FwM=
X-Received: by 10.237.53.174 with SMTP id c43mr19800356qte.273.1510739277896; Wed, 15 Nov 2017 01:47:57 -0800 (PST)
MIME-Version: 1.0
Received: by 10.200.46.248 with HTTP; Wed, 15 Nov 2017 01:47:57 -0800 (PST)
In-Reply-To: <CAOJ7v-1C5jR_SDD2NbKMB_iFG6kjwnhRpnw2axGV_JN91+ikww@mail.gmail.com>
References: <768A1C2E-4D4A-44C4-A65D-07728F900C96@jamesandjo.com> <8AACCCBE-CB5D-420C-8B31-C3144D9634F0@iii.ca> <CAO5ixTFmw_x4bdim1SzoWASShAop5aiurueoGy-y0XoFtTqVKQ@mail.gmail.com> <EEEB4601-56DE-4B5A-A354-194DB0C0BB23@iii.ca> <CAOJ7v-1C5jR_SDD2NbKMB_iFG6kjwnhRpnw2axGV_JN91+ikww@mail.gmail.com>
From: James Pearce <james@jamesandjo.com>
Date: Wed, 15 Nov 2017 09:47:57 +0000
Message-ID: <CAO5ixTG6LrhGPquprOyqBjg5XQrFEw1ArXBvLdi6mn9sY4J2Zw@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: Cullen Jennings <fluffy@iii.ca>, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c0041601fee4055e02669f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/Rv8gtRh4DQ_h3lZvIc05JL0Q1b4>
Subject: Re: [rtcweb] draft-ietf-rtcweb-ip-handling: Mode 2 and VPN scenarios
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, 15 Nov 2017 09:48:00 -0000

Perfect. Thanks!

On 14 November 2017 at 19:20, Justin Uberti <juberti@google.com> wrote:

> Yes - tracked in https://github.com/juberti/draughts/issues/87.
>
> On Mon, Nov 13, 2017 at 2:05 PM, Cullen Jennings <fluffy@iii.ca> wrote:
>
>>
>> My recollection is that we agreed to do this but the draft has not been
>> updated with this yet.
>>
>>
>> On Nov 10, 2017, at 5:36 AM, James Pearce <james@jamesandjo.com> wrote:
>>
>> Hi All,
>>
>> Apologies for resurrecting this topic from August. Has anything been
>> decided regarding this? Has it been rolled into other changes, or is it
>> still being considered?
>>
>> Many thanks,
>>
>> James
>>
>> On 1 September 2017 at 14:57, Cullen Jennings <fluffy@iii.ca> wrote:
>>
>>>
>>> > On Aug 23, 2017, at 3:06 PM, James Pearce <james@jamesandjo.com>
>>> wrote:
>>> >
>>> >
>>> > The obvious solution seems to be to change the behaviour of mode 2.
>>> Rather than using the default route in all cases, we should use the route
>>> that was used to fetch the origin. This seems to resolve both the usability
>>> and privacy concerns without reducing existing security.
>>>
>>> I agree this is a significant problem and your proposal does seems like
>>> a better solution that the current text. We should get people to think
>>> about the implications of that change.
>>>
>>>
>>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>>
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>>
>

v2.23.0 | Report a Bug | By Email