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.
--Oliver 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 [1]. It > appears a Media Task Force will be taking this on to produce a Working Draft > [2]. 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. > > Regards, > David > > [1] http://lists.w3.org/Archives/Public/public-html/2012Feb/0273.html > [2] http://lists.w3.org/Archives/Public/public-html/2012Apr/0007.html > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
