[Bug 25218] Allow license management directly via MediaKeySession

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

--- Comment #5 from David Dorwin <ddorwin@google.com> ---
(In reply to Joe Steele from comment #0)
> We have been having a lot of discussion about how key lifecycle should be
> managed. I will throw another proposal out there which can meet all the
> needs I have heard expressed so far. 

Can you be more specific about the requirements this addresses? I'm assuming
these are related to the key chaining and domain key scenarios.


EME is currently designed around key sessions, which represent "the lifetime of
the license(s)/key(s) [they] contains and associates all messages related to
them." This proposal seems to be a departure from that. An API could be
designed around keys, licenses, or something else, but that is not currently
the case with EME.

Some potential issues:
* Are loaded/queried keys really part of the session?
* What if they are associated with a persisted session ID?
* What if that key is contained in a license that contains other keys? Are they
loaded to? What if only one of the keys is released?

Does this proposal really solve the underlying requirements or use cases? Are
there ways to achieve the same goals without effectively adding a second set of
APIs? If the application needs to know about the different keys anyway, why not
put them in different sessions and figure out a way for them to interact?

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

Received on Monday, 7 April 2014 21:58:58 UTC