- From: <bugzilla@jessica.w3.org>
- Date: Wed, 27 Jun 2012 06:01:13 +0000
- To: public-html-media@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17615 Summary: Support for different CDM communication models Product: HTML WG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: critical Priority: P2 Component: Encrypted Media Extensions AssignedTo: adrianba@microsoft.com ReportedBy: petr@verimatrix.com QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-media@w3.org 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 on the CC list for the bug.
Received on Wednesday, 27 June 2012 06:01:23 UTC