W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2012

[Bug 17615] Support for different CDM communication models

From: <bugzilla@jessica.w3.org>
Date: Wed, 04 Jul 2012 06:12:12 +0000
Message-Id: <E1SmIou-0004QT-TL@jessica.w3.org>
To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17615

Yang Sun <eric.sun@huawei.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eric.sun@huawei.com

--- Comment #2 from Yang Sun <eric.sun@huawei.com> 2012-07-04 06:12:12 UTC ---
The html media element already support the option 2, and the retrieveKey does
not need to be defined in W3C, it is not a JS API.

(In reply to comment #0)
> The current communication model (section 1) assumes that the application
> communicates with the license server. In today's deployments, this is not
> always the case. There are at least two models in the industry:
> 1. The CDM generates a Key Request and does not rely on a specific
> communication protocol but rather lets the application communicate with the
> license server to deliver the request and eventually get the encrypted key back
> (i.e. license).
> 2. The CDM includes its own communication protocol to the license server.  In
> this case, the application does not need to go through the 'generateKeyRequest
> -> Get Key -> addKey' sequence but can simply call retrieveKey and the CDM
> handles the rest. 
> The Encrypted Media Extension proposal should support both of these models.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 4 July 2012 06:12:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 4 July 2012 06:12:14 GMT