- From: Mark Foltz \(Google\) via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Jul 2019 17:26:39 +0000
- To: public-secondscreen@w3.org
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. -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/124#issuecomment-509732914 using your GitHub account
Received on Tuesday, 9 July 2019 17:26:41 UTC