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

Iñaki Baz Castillo <ibc@aliax.net> Mon, 20 July 2015 13:51 UTC

Return-Path: <ibc@aliax.net>
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 4CA371A88A6 for <rtcweb@ietfa.amsl.com>; Mon, 20 Jul 2015 06:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level:
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7] autolearn=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 FKsIE3uxl7xD for <rtcweb@ietfa.amsl.com>; Mon, 20 Jul 2015 06:51:23 -0700 (PDT)
Received: from mail-yk0-f173.google.com (mail-yk0-f173.google.com [209.85.160.173]) (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 CA9841A8895 for <rtcweb@ietf.org>; Mon, 20 Jul 2015 06:51:22 -0700 (PDT)
Received: by ykdu72 with SMTP id u72so138872860ykd.2 for <rtcweb@ietf.org>; Mon, 20 Jul 2015 06:51:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=JNAUqZ0lXtL8w2Dq5SPii8MBR4A6wboeV+eJUiPPdpo=; b=m08gzCVHLFOSUtQd/soybWM7UrTzCIiEeJ3JFR/pv7+6FD6bIg3ggn6g4WSFo05yIB 9DxpVdJrqyhDe4ge84ERYuX/q4ftVjXoVLmaY9xMGWVNpgdXtEhmQWIfZTq8BB+CLLqs s0rRB1sqm5HoGAbucpiifptZLyJYFdSLi+RcMQitMC+3wyF8x8et10i5Y3kRTNvI941y nERR4hvk08Xv3pDrBkwCez7h9ZZRq5wVhPV8Vybn9z/Xg7BFnRmufuul19Bo6/56p8sT 4iF51MKx+wPyY8AapK67GOz9r1gkIoWn+Up9RcKa7XRvumbSBbPSEUxI6dcrFUV6jU1E dUjQ==
X-Gm-Message-State: ALoCoQnIRH4WnI7PHAwM45YR4pLtIlDh2IdtxPzcDt5Wbj+DHnZUtUu9CtCd7crfX7m67F4V6t1B
X-Received: by 10.129.108.2 with SMTP id h2mr28260694ywc.161.1437400282197; Mon, 20 Jul 2015 06:51:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.215.206 with HTTP; Mon, 20 Jul 2015 06:51:02 -0700 (PDT)
In-Reply-To: <55ACF880.9090704@jive.com>
References: <CA+65OspMD_PVjk0BXh7t4LtjmFDcDatoeNjFQOO_OVtC-Br+OA@mail.gmail.com> <55A95364.2070806@gmail.com> <CAOJ7v-3t9BQabR2e4EHs4G0Sec4sU9DFC2aiSXXYrat+an+RYg@mail.gmail.com> <55A96DA3.1040907@gmail.com> <CAOJ7v-1ui7349NzK6NZNRHPbnHWZajctk4cDgMKqRZSv47EYdA@mail.gmail.com> <55A9860D.8030903@gmail.com> <CAOJ7v-3LGd32rnpFVW_U0s3+iVaJXsL4vt_YAo=cyp6YyOArdw@mail.gmail.com> <CALiegfmiS18Jux-kCgOhTKKiyGtMertj6xCegpFrox5NOf9EJg@mail.gmail.com> <CABkgnnW0Tmjqz823vKiF84_u6HasBJC7ERMYCO2HL_NPj5saTA@mail.gmail.com> <CALiegfkpbLy1QXxr-RRF0oOpVv1sWsFeab=vvC4iT4DnPtjKQw@mail.gmail.com> <CABkgnnVWcuhX2NjZgx87L+Uo6df6rEBWW73cxbaX3mu_VfHmCA@mail.gmail.com> <CALiegfkQWAn-jMrjhcDPA3rtowOPVk-S8z3c-jvjpNmjtf=3hA@mail.gmail.com> <CABkgnnWERM4oxozNCSvRf1o0Wm-d9Bjw=9B+xh_NJ+h6GfBJ6Q@mail.gmail.com> <7F818FAC-5559-4074-B1FC-EB9516A98FB7@phonefromhere.com> <55ACEA74.8050300@jive.com> <CALiegfm6PG4cEJdWtYMOcfgLn5Z7Knf1TxoYvNDVrt4sEdQZAA@mail.gmail.com> <55ACF880.9090704@jive.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 20 Jul 2015 15:51:02 +0200
Message-ID: <CALiegf=-DaPKJ6ALZW-beB0wdJpEEKSEraV=Kqo+EsKuwwHdEw@mail.gmail.com>
To: Simon Perreault <sperreault@jive.com>
Content-Type: multipart/alternative; boundary="001a114dae7a389dd5051b4ed540"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/6d2ZlmoN-NyS8PiqlX6esbrQ4eI>
Cc: "rtcweb@ietf.org" <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, 20 Jul 2015 13:51:25 -0000

2015-07-20 15:32 GMT+02:00 Simon Perreault <sperreault@jive.com>:

> > The fact that the client announces its (probably) private VPN addresses
> > to the remote peer does not mean that it also reveals the associated
> > public reflexive IP. That just happens if the client performs STUN
> > procedures over that interface, which is exactly the issue being
> > discussed (at least right now).
>
> If you can find a server-reflexive candidate on the VPN interface, it
> means you can talk to the Internet using that interface, using that
> server-reflexive IP address. How is that private knowledge at all? How
> do you expect to keep your server-reflexive address private but still
> use it for communication?
>

Ok, let's simplify this subject:

- Computer with two default routes (A and B) and a private network route
(C).
- A is the preferred default route one so has priority in the routing table.
- Every packet whose destination is not C network should be sent over A.
...
- or not? should a specific app override it?

 This seems more a moral issue.




> The routing table is *not* overridden by explicitly binding to an
> interface.
>

I meant "using a secondary default route". Sorry for the confusion.


> >     That is a valid concern, and the answer to it is MIF.
> >
> >
> > Sorry, what does MIF stand for?
>
> https://datatracker.ietf.org/wg/mif/documents/
>
> The MIF WG is working on exactly this kind of problem. They are
> developing an API for solving precisely this kind of interface
> preference problem. IMHO ICE could perhaps be extended to make use of
> this API. But I see it as "just" an enhancement.


Good to know. Thanks.



-- 
Iñaki Baz Castillo
<ibc@aliax.net>