- From: <bugzilla@jessica.w3.org>
- Date: Thu, 28 Feb 2013 21:26:37 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21155 Fred Andrews <fredandw@live.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fredandw@live.com Summary|EME should be explicit |EME should be explicit |about its relationship with |about its relationship with |Web Platform APIs that |Web Platform APIs that |allow video frames are |allow video frames and |audio samples to be |audio samples to be |extracted from an |extracted from an |HTMLMediaElement |HTMLMediaElement --- Comment #1 from Fred Andrews <fredandw@live.com> --- Standards reflect consensus among some web browser implementers and thus have no standing or ability to impose restrictions that might advantage the business interests of some content authors. The EME task force has already declared that the implications of the operation of the CDM are out of scope as is the level of protection that the CDM provides. Some expected use cases for the EME do suggest that on some proprietary stacks that the decoded output of some CDMs may not be available and thus such APIs could not in general be depended on. I would not that the diagram in the EME specifications notes that decoded frames may, or may not, be returned to the UA. Standards reflect consensus among web browser implementers, which may include users, and thus have no standing or ability to impose restrictions that might protect the business interests of some content authors. The implications of an attempt to do so should be explored. Further, attempts to fingerprint the UA in order to restrict content delivery based on detected capabilities could restrict normal UA operations, such as UA spoofing, and the implications of attempts to so should be explored. The EME Impact document hosted at the WHATWG Wiki is happy to host such analysis, and a note has been added about your concern, see: http://wiki.whatwg.org/wiki/Encrypted_Media_Extensions_Impact -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 28 February 2013 21:26:38 UTC