Video Breakthroughs
242.6K views | +0 today
Follow
Video Breakthroughs
Monitoring innovations in post-production, head-end, streaming, OTT, second-screen, UHDTV, multiscreen strategies & tools
Curated by Nicolas Weil
Your new post is loading...
Your new post is loading...
Scooped by Nicolas Weil
Scoop.it!

EME WTF?: An introduction to Encrypted Media Extensions

EME WTF?: An introduction to Encrypted Media Extensions | Video Breakthroughs | Scoop.it
Encrypted Media Extensions provides an API that enables web applications to interact with content protection systems. Learn how to allow playback of encrypted audio and video.
No comment yet.
Scooped by Nicolas Weil
Scoop.it!

Encrypted Media Extensions for HTML5 by Google, Microsoft and Netflix

Encrypted Media Extensions for HTML5 by Google, Microsoft and Netflix | Video Breakthroughs | Scoop.it

This proposal extends HTMLMediaElement to enable playback of protected content. The proposed API supports use cases ranging from simple clear key decryption to high value video (given an appropriate user agent implementation). License/key exchange is controlled by the application, facilitating the development of robust playback applications supporting a range of content decryption and protection technologies. No "DRM" is added to the HTML5 specification, and only simple clear key decryption is required as a common baseline.

No comment yet.
Scooped by Nicolas Weil
Scoop.it!

HTML5 Encrypted Media Extensions W3C Working Draft

HTML5 Encrypted Media Extensions W3C Working Draft | Video Breakthroughs | Scoop.it

This proposal extends HTMLMediaElement providing APIs to control playback of protected content.

 

The API supports use cases ranging from simple clear key decryption to high value video (given an appropriate user agent implementation). License/key exchange is controlled by the application, facilitating the development of robust playback applications supporting a range of content decryption and protection technologies.

 

This specification does not define a content protection or Digital Rights Management system. Rather, it defines a common API that may be used to discover, select and interact with such systems as well as with simpler content encryption systems. Implementation of Digital Rights Management is not required for compliance with this specification: only the simple clear key system is required to be implemented as a common baseline.

 

The common API supports a simple set of content encryption capabilities, leaving application functions such as authentication and authorization to page authors. This is achieved by requiring content protection system-specific messaging to be mediated by the page rather than assuming out-of-band communication between the encryption system and a license or other server.

No comment yet.