[Bug 17615] Support for different CDM communication models

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17615

Petr Peterka <petr@verimatrix.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |---

--- Comment #4 from Petr Peterka <petr@verimatrix.com> ---
This bug was previously closed but the closure was later invalidated (3) by
explicitly removing the ability of a CDM to implement an independent key
management protocol. (See Abstract: " 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.")

The current communication model forces the communication between the License
Server and CDM to go through the Application. However, in order to enable some
protection systems, direct communication between the CDM and a License Server
is required. 

According to the Web & TV Interest Group requirements document for content
protection (1) the goal is to standardize an interface that supports "any
content protection system to be used to protect content". Also EME '1.1 Goals'
states as a design goal: "Support a range of content security models, including
software and hardware-based models".

We do believe that the direct communication option will enable broader EME
applications and support and that this option does fit within the current EME
(earlier bug 17615 (2)  was closed as out of scope) and would not limit any
existing use cases. 
The proposed change is to remove the limitation by reverting the introduced
addition (3) and to make the first iteration of the key messages in
'Introduction' dotted, as they are in the second iteration. We don’t see any
other mandatory changes.

(1)
https://dvcs.w3.org/hg/webtv/raw-file/tip/mpreq/cpreq.html#u1.-support-authorized-access-to-content 
(2) https://www.w3.org/Bugs/Public/show_bug.cgi?id=17615 
(3) https://dvcs.w3.org/hg/html-media/rev/1ca7610af922

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 20 August 2013 00:27:43 UTC