Identity and Streams Interim, Washington DC Martin Thomson Stream - - PowerPoint PPT Presentation

identity and streams
SMART_READER_LITE
LIVE PREVIEW

Identity and Streams Interim, Washington DC Martin Thomson Stream - - PowerPoint PPT Presentation

W3C stuff Identity and Streams Interim, Washington DC Martin Thomson Stream Isolation A receiver should soon be able to distinguish between streams that are isolated at the source and regular streams Sending Receiving peerIdentity


slide-1
SLIDE 1

W3C stuff

Identity and Streams

Interim, Washington DC Martin Thomson

slide-2
SLIDE 2

Stream Isolation

❖ A receiver should soon be able to distinguish between

streams that are isolated at the source and regular streams

Sending Browser Receiving Browser

peerIdentity isolated encrypted, peer authenticated isolation too

slide-3
SLIDE 3

Problem

❖ A mismatch causes DTLS to fail to negotiate

Browser A Browser B

peerIdentity isolated Session failure not isolated

slide-4
SLIDE 4

Proposal

❖ Request that the IETF WG create a marker in the SDP

that would allow the API to detect this failure

❖ If isolation is in the remote SDP and we aren’t isolated,

either:

❖ A) Fail setRemoteDescription (easy) ❖ B) Check if local streams can be isolated, and isolate them,

  • therwise, fail setRemoteDescription (bleargh)
slide-5
SLIDE 5

requestIdentity

❖ Reminder: RTCConfiguration parameter with three

values: “yes”, “ifconfigured”, “no”.

❖ Originally included in support of browsers having IdP

configuration

❖ We don’t need this, does anyone else?

slide-6
SLIDE 6

Stream Issues

slide-7
SLIDE 7

captureStream[UntilEnded]

❖ For a media element (<video>, <audio>), be able to

create a media stream from its contents

❖ Great for web audio

❖ … also a potential source of WebRTC streams

❖ captureStream generates media from the source ❖ captureStreamUntilEnded stops when the stream ends

❖ Switching sources causes this to end

slide-8
SLIDE 8

Isolation Issues

❖ Isolation issues are similar to those for other MediaStream ❖ Isolation state can change

❖ At HTTP layer, due to redirects on media fragments changing origin ❖ In the page, due to switching of source (captureStream only)

❖ Current implementation in Firefox causes these media

streams to become inaccessible while they contain cross

  • rigin content

❖ Potential drawback is that media from x.com can’t be sent to x.com

using WebRTC

slide-9
SLIDE 9

Blocked Streams

❖ Streams can become “blocked” for several reasons:

❖ Pausing the media element ❖ Becoming isolated ❖ WebRTC pause ❖ Network blips

❖ This usually manifests as either a frozen frame or solid black in

video, and silence in audio playback

❖ MediaRecorder might need to know about this

❖ Should we add an option (and all that entails upstream) to elide these gaps

from recordings?

slide-10
SLIDE 10

Boring Process Stuff

❖ What do we want to do with captureWossname? ❖ We’ve found it to be useful, but we haven’t seen a lot of

interest

❖ Options seem to be:

❖ it is an abomination and should not be allowed to live ❖ not right now, or not right here, or whatever man ❖ adopt this cute kitten, it’s adorable