IETF Logo Mail Archive

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

Justin Uberti <juberti@google.com> Tue, 14 November 2017 19:21 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 408A7128799 for <rtcweb@ietfa.amsl.com>; Tue, 14 Nov 2017 11:21:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] 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 WMtl3LkZbSf3 for <rtcweb@ietfa.amsl.com>; Tue, 14 Nov 2017 11:21:16 -0800 (PST)
Received: from mail-ua0-x22b.google.com (mail-ua0-x22b.google.com [IPv6:2607:f8b0:400c:c08::22b]) (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 0EB77124BAC for <rtcweb@ietf.org>; Tue, 14 Nov 2017 11:21:15 -0800 (PST)
Received: by mail-ua0-x22b.google.com with SMTP id q18so13647070uaa.0 for <rtcweb@ietf.org>; Tue, 14 Nov 2017 11:21:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=75WNKqS1i4Jwc38BhNx2dMg6phP64qV+elZghSrn+GE=; b=ceOfdmMIriT4Tghn9seorks9w4BVY+bPASBO0RbjRYd7Hp2QR5uYdDS5/idbnvTVf8 eJkj+q9CuJOneQwUmjlY6izNe3f5FTpMsnQnIUnuLCwUd/oQoaUfWPZyYDkwlHmJyOKw NNEXyBDYHRQ2QjcByZvh+ssbaSpU+3vDLhW4/BDrqdJuM34GgP4uNN0J8luHX4XkgtKN 0WVNVUfuiYLa6NsCGdrj4Bdi5M1SnLNLbQHtJEqQPvR3+AnTEvsd9hRwv6/IGn1EgIGH 4uwriMGn0psWieE9yWBLjh4CdpcEw8XMIVsrFvkV7YM2uUCmcVIcAbfy8Q6v/BDDTUaP wa2A==
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=75WNKqS1i4Jwc38BhNx2dMg6phP64qV+elZghSrn+GE=; b=p6o7tRvonRi6ECpFWjOd+sPgYBf5GgpAt7lbSXM2mWf7ML69MEoev6CvWZVgHSfXH9 Oi+2lddakF4h46DYE00qwteTghyAxfBA8srgpqEmgEvlFSfFROxCpEBQbpYtsxczL/Ho 9zQrTc8GEpNozs3NbnRyoZt/ZlWTlKBEhZKYUCc1w8jpisg++BXlraM+/bVgi2+5H7iZ m4tsNNSBsDXckVI/XKXGR9ho/6Lh/AbqXfYtitZgaRTa/YbFXl8w2uQe7bwNCPt38AlU zkVHNxkIVNsFP+XKmrMeuE/HuUEd3y/I/l4OnYLKVYlp6l3P1/6q+rpEDEtVSCDZh95y CykQ==
X-Gm-Message-State: AJaThX4Yh4h4GFpuSpeOAsdFAqFFjFXH+G4q6SXOX7yi/GpINIskPwPQ pWVk9AOuncQkPYY+MfEP4ZaEkYbr9d3HoM0ZeB2UBtUBJwQ=
X-Google-Smtp-Source: AGs4zMbMzJkwvNNON4xM0o/phheNct58iEMykTnIdnz1fREnVvIwhqQEq7qoyh5MO3PrxyB66CYghNmzHQnBsQmFOyU=
X-Received: by 10.176.80.2 with SMTP id b2mr8405970uaa.198.1510687274497; Tue, 14 Nov 2017 11:21:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.174.215 with HTTP; Tue, 14 Nov 2017 11:20:53 -0800 (PST)
In-Reply-To: <EEEB4601-56DE-4B5A-A354-194DB0C0BB23@iii.ca>
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>
From: Justin Uberti <juberti@google.com>
Date: Tue, 14 Nov 2017 11:20:53 -0800
Message-ID: <CAOJ7v-1C5jR_SDD2NbKMB_iFG6kjwnhRpnw2axGV_JN91+ikww@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Cc: James Pearce <james@jamesandjo.com>, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c18ee445d8657055df64aea"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/qaAT9UAna17kCcZ8zG9zq0z0bdM>
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: Tue, 14 Nov 2017 19:21:18 -0000

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