Re: [rtcweb] Isolating data channels (Re: Asking TLS for help with media isolation)

Martin Thomson <martin.thomson@gmail.com> Mon, 07 April 2014 17:01 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 2B4EA1A07AE for <rtcweb@ietfa.amsl.com>; Mon, 7 Apr 2014 10:01:22 -0700 (PDT)
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, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 S8OacO-L03GX for <rtcweb@ietfa.amsl.com>; Mon, 7 Apr 2014 10:01:17 -0700 (PDT)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 8C15D1A07C1 for <rtcweb@ietf.org>; Mon, 7 Apr 2014 10:01:16 -0700 (PDT)
Received: by mail-we0-f169.google.com with SMTP id w62so7149608wes.0 for <rtcweb@ietf.org>; Mon, 07 Apr 2014 10:01:10 -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=CTET50qn25cN5sNl2dMdAMWt7do1UuS+STtZK6zwIN4=; b=ugtVhxgwPpvxg5EMfo8w01Ffv2sZO483b56HDbqvGGqKxtto3XWL8lzE1MpXecl5ht s7tuHAg3znkdno6ZmuRO8NulMoewYdB6STCTTNGm9J6ox3PaOsw/9UNzDLELvPqKrcD1 yNFdxOYYoLCIeWIEydRFd2WB9OVdP8wQr0fub//DdI0muFw4KdokKDSAVP6uF7HZdwNl I5xBMZJ0hg4fNB4A/ncfzxkC9LTDrvhZC6PcQIgHHXlhFHslZzOKlcrZTm9rufHZcs7I 26p3LvDmmTCusXi922BYz83UUznHrzJMf90DIh70drNp9U2YaUAYqYwGUtbaern2wpnT Sj6Q==
MIME-Version: 1.0
X-Received: by 10.180.185.197 with SMTP id fe5mr26695200wic.56.1396890070374; Mon, 07 Apr 2014 10:01:10 -0700 (PDT)
Received: by 10.227.147.10 with HTTP; Mon, 7 Apr 2014 10:01:10 -0700 (PDT)
In-Reply-To: <53425BAF.4070105@alvestrand.no>
References: <CABkgnnWWuU63Vd=gw+wrh2ADgVYtQzhoRzRE1sv5azJE=MhWDg@mail.gmail.com> <533F191D.8050109@alum.mit.edu> <CABkgnnVht5EmJ7a2LDh50ivjUdoTpJ8GannQKReBSJbVGQGmgA@mail.gmail.com> <53425BAF.4070105@alvestrand.no>
Date: Mon, 7 Apr 2014 10:01:10 -0700
Message-ID: <CABkgnnXKe65-30qkuhkCLmaUYVfe8vrWv9BCJzOvC7KaRwUH=g@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/vdchn6bPqkSqD_uPWx80RKREvp4
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Isolating data channels (Re: Asking TLS for help with media isolation)
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: <http://www.ietf.org/mail-archive/web/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, 07 Apr 2014 17:01:22 -0000

The subject is largely speculative, but when it comes to solutions,
the problem will not be a lack of options, but an inability to choose
a "right" one.

On 7 April 2014 01:02, Harald Alvestrand <harald@alvestrand.no> wrote:
> Wild suggestion: if you want per-track isolation properties, open up a data
> channel with a protocol called '*WebRTCIsolationInfo' and use it to send
> information about the isolation status of each track, thereby also providing
> a working example for the rule 'all data channels that have protocols
> starting with "*" are for browser internal usage'.....

I assume that you are talking PPID here.  Given that it's off limits
for JavaScript currently, then it does provide an opportunity for this
communication.  The problem there is that you need to spin up data
channels, even if the application has no need of them.  That's a
fairly high cost.