Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How does remote playback interact with EME? #124

joeyparrish opened this issue Jul 1, 2019 · 3 comments


Copy link

commented Jul 1, 2019

This came out of discussion started in w3ctag/design-reviews#323 (comment):

I don't see any mention of MediaKeys in the spec, and I don't understand the resolution from #41 or #55. Can you give an example of how EME would work with remote playback? Or is it simply not supported / supportable?


@joeyparrish joeyparrish referenced this issue Jul 1, 2019
1 of 3 tasks complete

This comment has been minimized.

Copy link

commented Jul 9, 2019

IMO Remote Playback shouldn't work with EME because there are two ways to do Remote Playback:

  • Send the file URL to the remote device for it to play. In this case, if the file is protected, the other device wouldn't be able to play it.
  • Stream the media to the other device. In this case, it seems not the best idea to stream the decoded bytes in clear.

@mfoltzgoogle may have other thoughts especially with Open Screen.


This comment has been minimized.

Copy link

commented Jul 9, 2019

As far as the Remote Playback API spec is concerned, it looks like it's up to the user agent to implement remote playback or not for encrypted media. It's possible to implement, though. Either the remote display needs to obtain a license to decode the media locally (which generally requires messaging through e.g. the Presentation API), or the media transport needs to comply with a standard like HDCP. No reasonable implementation sends remote playback media "in the clear" for security and privacy reasons.

Regarding Open Screen Protocol, handling encrypted content is specifically out of scope for the charter of the spec, so there won't be any spec language around it at this point. If an agent implements OSP for remote playback, and wants to query and report the HDCP status of the remote display, it would have to be through a custom extension to the core protocol.

However, there may be interest in adding this to the current or a future iteration of the OSP spec.


This comment has been minimized.

Copy link

commented Sep 12, 2019

(NOTE: Not an advocate of DRM. Feedback is from an end user experience perspective.)

Having this supported in a future iteration of the spec would be definitely useful. From a user's perspective, some videos being possible to cast to a remote display and some being impossible (internally due to DRM) is not something that would be expected.

From an end user perspective, requesting a Netflix video (which presumably is DRM protected) which you were watching on a native app to be put on the big screen should not be different from that stream request being initiated from web content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
4 participants
You can’t perform that action at this time.