[webkit-dev] Adding Encrypted Media Extensions
oliver at apple.com
Wed Apr 4 10:37:13 PDT 2012
Last I saw, there hadn't been any attempt to actually define how the content is encrypted. Has that changed? If it hasn't how do we get interoperable implementations? The only way for this spec to not break the openness of <video> and <audio> is for the encryption algorithm to be completely defined in the spec.
On Apr 4, 2012, at 9:55 AM, David Dorwin wrote:
> Hi WebKit!
> I plan to add the Encrypted Media Extensions to the media elements. The extensions allow web applications using <audio> and <video> to control key exchange. The extensions will be behind the ENCRYPTED_MEDIA feature define. The feature is tracked as https://bugs.webkit.org/show_bug.cgi?id=82968.
> Implementation will be based on the draft proposal at http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html, which was published jointly by Google, Microsoft, and Netflix . It appears a Media Task Force will be taking this on to produce a Working Draft . Having an implementation will allow us to include implementation experience in the development of the draft.
> As described in the proposal, several new methods and events are added to HTMLMediaElement and a new keySystem parameter and attribute are added to canPlayType() and HTMLSourceElement, respectively. As with much of the media stack, most of the functionality will be implemented within the various ports. ENCRYPTED_MEDIA will be enabled for the Chromium port and covered by its buildbot.
>  http://lists.w3.org/Archives/Public/public-html/2012Feb/0273.html
>  http://lists.w3.org/Archives/Public/public-html/2012Apr/0007.html
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev