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

Iñaki Baz Castillo <ibc@aliax.net> Sat, 18 July 2015 00:01 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 8D4671A00C1 for <rtcweb@ietfa.amsl.com>; Fri, 17 Jul 2015 17:01:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level:
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, 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 co1W2vfKUu6t for <rtcweb@ietfa.amsl.com>; Fri, 17 Jul 2015 17:01:05 -0700 (PDT)
Received: from mail-yk0-f172.google.com (mail-yk0-f172.google.com [209.85.160.172]) (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 B6B4D1A00E1 for <rtcweb@ietf.org>; Fri, 17 Jul 2015 17:01:05 -0700 (PDT)
Received: by ykay190 with SMTP id y190so101858663yka.3 for <rtcweb@ietf.org>; Fri, 17 Jul 2015 17:01:05 -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:content-transfer-encoding; bh=6T1Cu4D2wzX3ZeBsbUE8ZcfvgBTioEZex14bFTlp4nE=; b=KSdQhv8w7Mzlj/yIMbSwLZlzdI3NrvB+jSYPxxMy7gJCXdvfJVXOVc7wzD8HEYIdJ0 1sDeX3EDQWEy+j3SvJCA8BRHO4KZQeNJq6HUh8uE8uZOl+TrXgHtmlYS90XpC6D5ytjZ gjKeFmNN4TKQhHC+ECnb3prVRFCJuXGgfQqGw7jT9aoJjUVff5x7GaKl89MCxCjm4fjw /eUYKYLcd0+TLXC/0Zbdl12wJ4BmwpGXAzavMGdD3ZiVd3TeB+n7qnA9f3Q7974F4djM JF1Tsd1A09jxCWc2rA6hwP6yvYRibeOQSJkPzFMaRWhLvjMNqfvR74/+/7HfejhxzSXQ r4qw==
X-Gm-Message-State: ALoCoQkfipu6+emtmGrv0TyQZmU9rXNbN85z2gJnGSGL0qpIzjs7T3uzHff5QbNQhmlA0slRJ2I5
X-Received: by 10.129.79.4 with SMTP id d4mr18033763ywb.15.1437177665144; Fri, 17 Jul 2015 17:01:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.215.206 with HTTP; Fri, 17 Jul 2015 17:00:45 -0700 (PDT)
In-Reply-To: <CABkgnnVWcuhX2NjZgx87L+Uo6df6rEBWW73cxbaX3mu_VfHmCA@mail.gmail.com>
References: <CA+65OspMD_PVjk0BXh7t4LtjmFDcDatoeNjFQOO_OVtC-Br+OA@mail.gmail.com> <CAOJ7v-0UBGtP0-atxP7X4OTj-H6Lost5o42aAS65mA6CEqcQsw@mail.gmail.com> <CA+65OsrhXHK+cRAFLCZFt+34vr8eRhj+CN3DgznUBfSwmWYggw@mail.gmail.com> <CAOJ7v-24VCW6kkn7LOLkqZzhYEU0r=nmd_F7Zns1rnyqKN6xAg@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>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Sat, 18 Jul 2015 02:00:45 +0200
Message-ID: <CALiegfkQWAn-jMrjhcDPA3rtowOPVk-S8z3c-jvjpNmjtf=3hA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/VSXg-q9gDy8V0DBTLHmTYTSBkaQ>
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: Sat, 18 Jul 2015 00:01:06 -0000

2015-07-18 1:56 GMT+02:00 Martin Thomson <martin.thomson@gmail.com>:
>> The browser should then check the chosen
>> source IP to match the associated local candidate.
>
> That doesn't always work either. The source address of the packet you send
> isn't always reported correctly (not does it necessarily go out the
> interface you choose, but that is another problem).

The point is that you don't even choose the interface. The OS will do for you.


>> >  If you bind to 0.0.0.0, you can't handle multiple interfaces
>> > correctly, and that reduces the odds of completing ICE with the best
>> > result.
>>
>> Any real usecase in which that could be true? Why should the app
>> override the OS routing table?
>
> Which use case? ICE

I understand we are here discussing how ICE is supposed to work. What
I wonder is: in which case it is useful to send packets to the
STUN/TURN server on all the interfaces instead on relying on the
interface the OS would choose to reach that server?





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