IETF Logo Mail Archive

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

Martin Thomson <martin.thomson@gmail.com> Fri, 17 July 2015 23:56 UTC

Return-Path: <martin.thomson@gmail.com>
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 ADBC31A9302 for <rtcweb@ietfa.amsl.com>; Fri, 17 Jul 2015 16:56:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] 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 oLbIrmoGQGQb for <rtcweb@ietfa.amsl.com>; Fri, 17 Jul 2015 16:56:58 -0700 (PDT)
Received: from mail-yk0-x22c.google.com (mail-yk0-x22c.google.com [IPv6:2607:f8b0:4002:c07::22c]) (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 92C431A92F3 for <rtcweb@ietf.org>; Fri, 17 Jul 2015 16:56:58 -0700 (PDT)
Received: by ykay190 with SMTP id y190so101809022yka.3 for <rtcweb@ietf.org>; Fri, 17 Jul 2015 16:56:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=veaYFOWBnu9odDU6y8HApMnK7F9eKR3PLjtYkX1N054=; b=K27St7/qQ3Qlkon/BMuwPud6nPfluhdkJxd+H3FYqOf7rI+DsMt2PTCYprAiROYIu8 hGdEiTOnC7E5RRwEQNHLKrpMZR44i9ptlDsGOskTUdrqHSsLqT7fR4VzoO3Y/2y3k5Cn y2dBasr69Fy7zKN2HF8fujBgfnNbNVdFwRQvhrKgI0kxTivbS5K8HpblO0gm0rMqUH0X wi2RsuhS00YgYV41G4CZB4VNWiluTGOPpToBA6tPI1MzLK4yusZ2rMIVAnTA+lNoDpZN mVqRSaBZmf1zhH1Jdz6aoQd6Zx1G3SxKmRmt6w7I6SI0LM/2MjFrPwRCO7J2o8TsI4Gk TLRA==
MIME-Version: 1.0
X-Received: by 10.129.103.84 with SMTP id b81mr17750906ywc.55.1437177418042; Fri, 17 Jul 2015 16:56:58 -0700 (PDT)
Received: by 10.129.110.138 with HTTP; Fri, 17 Jul 2015 16:56:57 -0700 (PDT)
Received: by 10.129.110.138 with HTTP; Fri, 17 Jul 2015 16:56:57 -0700 (PDT)
In-Reply-To: <CALiegfkpbLy1QXxr-RRF0oOpVv1sWsFeab=vvC4iT4DnPtjKQw@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>
Date: Fri, 17 Jul 2015 16:56:57 -0700
Message-ID: <CABkgnnVWcuhX2NjZgx87L+Uo6df6rEBWW73cxbaX3mu_VfHmCA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Content-Type: multipart/alternative; boundary="001a11490eb87b5473051b1af16f"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/mIh5Uuij3pftMZYmUGdhmqcLa1I>
Cc: 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: Fri, 17 Jul 2015 23:56:59 -0000

On Jul 17, 2015 4:48 PM, "Iñaki Baz Castillo" <ibc@aliax.net> wrote:
> If you bind to 0.0.0.0 the OS will find out the proper interface to
> send the STUN/TURN request.

No, that's the point, you need control too get this right.

> 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).

> >  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

v2.23.0 | Report a Bug | By Email