- From: Cullen Jennings <fluffy@iii.ca>
- Date: Sun, 18 May 2014 15:19:45 -0400
- To: Martin Thomson <martin.thomson@gmail.com>
- Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
Two comments …. 1) It seems like your ALPN draft solves this 2) users A and B trust each other and their browsers and operating systems, it’s the web site setting up the call they don’t trust On May 15, 2014, at 1:21 AM, Martin Thomson <martin.thomson@gmail.com> wrote: > This is probably best handled in a room, but here goes. > > A has isolated streams because it thinks it's making a "private" call. > (Scare quotes intentional.) > > B has regular streams. > > A and B try to establish a call. Nothing in the signaling they are > using (SDP, woo!) indicates that they are screwed. The browser runs > the O/A exchange and it seems OK, until the DTLS session blows up. > > Do we want a signal in SDP for this state? I think that it would be > nice. We can put a wee attributey thing on the a=identity line. > > Sorry, scratch that, we can request that the RTCWEB working group > consider this as a new requirement on their signaling work. > >
Received on Sunday, 18 May 2014 19:17:02 UTC