[Bug 26887] Allowing license servers and CDMs to control data persistence and secure release

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

--- Comment #8 from Jerry Smith <jdsmith@microsoft.com> ---
Reply to Mark:

Are keys used in a session the grouping you really want?  I would think you’d
want to group key data by a given show or movie that was watched.  Secure
release would then need to associate some collection of licenses and data with
that show or movie, and confirm that it was securely deleted, and the pipeline
that used it securely terminated.  I don’t think MediaKeySessions map very
cleanly to this.  Do they?

My thought on reusing a persistent license was that the session would be
initialized with initData, but that the persistent license would be found and
no messages exchanged.  A keychange (or keyfound) event would be fired after
the stored keys were loaded.  This wouldn’t require initializing the session
with IDs from the persisted license itself.

If multiple valid licenses are stored for a given keyId, then the first found
might be used.  This assumes that we don’t have a specific scenario that cares
which license is used.  I’m not sure exactly how this case could be created.

If there are multiple secure release records, would the app not want to
complete them all before proceeding?  That too assumes there is not a need to
be specific on completing some secure releases, but not others.  Would it be
valid for an app to first start playback of secure release content, and then go
looking for old sessions not released?  That could mix the current session in
with the old ones.

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

Received on Wednesday, 1 October 2014 20:56:29 UTC