Re: [rtcweb] Asking TLS for help with media isolation

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 10 April 2014 21:30 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 7F1981A0214 for <rtcweb@ietfa.amsl.com>; Thu, 10 Apr 2014 14:30:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 pzi_nL8Z0x8T for <rtcweb@ietfa.amsl.com>; Thu, 10 Apr 2014 14:30:08 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 9DC891A0073 for <rtcweb@ietf.org>; Thu, 10 Apr 2014 14:30:08 -0700 (PDT)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta03.westchester.pa.mail.comcast.net with comcast id oH9h1n0031ap0As53MW7Cn; Thu, 10 Apr 2014 21:30:07 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta22.westchester.pa.mail.comcast.net with comcast id oMW61n00x3ZTu2S3iMW7vV; Thu, 10 Apr 2014 21:30:07 +0000
Message-ID: <53470D5D.5040806@alum.mit.edu>
Date: Thu, 10 Apr 2014 17:30:05 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
References: <CABkgnnWWuU63Vd=gw+wrh2ADgVYtQzhoRzRE1sv5azJE=MhWDg@mail.gmail.com> <533F191D.8050109@alum.mit.edu> <CABkgnnVht5EmJ7a2LDh50ivjUdoTpJ8GannQKReBSJbVGQGmgA@mail.gmail.com> <53419ED4.8020102@alum.mit.edu> <CABkgnnVjZ51bt5WQ1uvHHUz-4xFzpXQGhuMqxeMpOqJ1d+hQiA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D2B26CB@ESESSMB209.ericsson.se> <CAOW+2dsZrgQrOwJDu+bFE0U-dSUj5D--s_Dx1Nu9Ac60yuYCrA@mail.gmail.com> <CABkgnnUgiW7K7C9rTXGU6nAw2mO_5DPZU9ra64nRK=EVCENUzQ@mail.gmail.com> <53465CA2.4010607@alvestrand.no> <5346AFFF.4070803@alum.mit.edu> <CABkgnnW37xNk9P9fZpe3pmG8LpdLHbakfU7Eby+8-KMx_1kJ7Q@mail.gmail.com>
In-Reply-To: <CABkgnnW37xNk9P9fZpe3pmG8LpdLHbakfU7Eby+8-KMx_1kJ7Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1397165407; bh=61aslY8VEmxJcLBDTYOsfQNgYzl02CyIJUB4IWdtegc=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=aTDVtYehg2lVlHNyQ+ijlww3+/SubYPN1sf72tydN466wP9SiAR8PgpKqwCE5ELZO Uomaqa0Ior0zxHDAm/VaaEmBR+et9esCeOiTCHhpjHwYxHB/95TGZ1u4/nhsj6LBVN f7OGExQBqR8JVGnimlU6Dph1jZ41PVg7hubv8YQ4U2IOOVYI01F0w1N1I/j1QylU5c oykUsoYhxaNSrXEOHd4a8n3jLufZfM3HXfKzZs2cIX43JXvjWgaWdULRaOsP3gZM4l DrtU7qUoAVowsZG5GeMEKah9HtjN+yfHO4f7+OisAmUh5/0Aigi/uaFbD/8eHKCQOA qGuUkfqjzdu1A==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/Sj2OT5dELVnS9xnSZ9cBrWLDxLA
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] 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: Thu, 10 Apr 2014 21:30:09 -0000

On 4/10/14 3:33 PM, Martin Thomson wrote:
> On 10 April 2014 07:51, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>> So what does this mean for screen sharing with a conference?
>
> It means the same thing, if the stream is isolated, it will not be
> possible to share with a conference MCU.
>
> (You can go full mesh to retain good isolation, but that requires
> multiple differently isolated streams, and it's likely to annoy the
> user with gUM prompts.)

Well, apparently it will be at the discretion of the conference focus. 
Since it presumably doesn't have a browser, it will only be governed by 
its own policies and whatever normative statements are made about the 
behavior of servers in this case.

There will be a business motivation to allow such sharing if a rationale 
can be made that it is allowed.

So that puts a premium on clear normative statements.

	Thanks,
	Paul