- From: <bugzilla@jessica.w3.org>
- Date: Mon, 28 Apr 2014 23:05:33 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25218 Mark Watson <watsonm@netflix.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |watsonm@netflix.com --- Comment #7 from Mark Watson <watsonm@netflix.com> --- I confess to not having followed the threads associated with this issue, but I'm going to give my opinion anyway ;-) I believe that as far as the EME API is concerned, a MediaKeySession contains a content key or keys, each associated with a key id. Concepts such as licenses and domains are not modeled in our API. I think the question here is do they need to be ? If they are not, this does not mean such concepts to do exist in any given CDM, it's just that they are not visible on the API and the CDM is left to do whatever it chooses with them. Specifically, I would expect that if a license is a vehicle for communicating keys to the CDM, then any given license remains in the CDM until all the keys that it contains are released, unless we explicitly expect the keys to be persisted, in which case the license may be persisted. Likewise, if a DRM has a concept of 'domain' and licenses are associated with domains then the state associated with a domain needs to live for at least long as the licenses associated with it, but again could be persisted for longer than that if the CDM chooses. This is not to say a CDM MUST operate in the way described above: all we say in EME is that there are keys and key ids and they live in sessions. Everything else is up to the CDM. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 28 April 2014 23:05:34 UTC