[Bug 21869] Need clarity on stored keys for CDMs

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

--- Comment #10 from Mark Watson <watsonm@netflix.com> ---
(In reply to comment #3)

> Seems like the client side could be simpler by handling this by the keys
> expiring often and the connection to the license server being chatty with
> re-requesting keys all the time as a form of heartbeat. If the server side
> doesn't like the complexity, maybe the server side should relax tracking
> requirements. 
> 

We have found significant advantage for long-form content if a connection to
the application servers is not required for streaming to continue. That is,
once the key and content URLs have been acquired, streaming can continue even
if the application server connection is lost. If a heartbeat is *required* to
continue streaming, then the availability requirements on the application
servers go up by an order of magnitude.

OTOH, relaxing tracking requirements would make it impossible to implement
business rules like limitations on the number of concurrent streams on an
account.

This is why we prefer a solution with secure proof of key release. This does
require CDM storage for the 'last CDM state' - specifically the identities of
the keys the CDM is currently using or for which secure proof of key release
has not been acknowledged by the server and a reliable indication of the time.

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

Received on Tuesday, 16 July 2013 16:37:02 UTC