[Bug 25092] Need a way to inform script that resolution restrictions are applied

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

--- Comment #27 from Mark Watson <watsonm@netflix.com> ---
We need to differentiate. In the downscaling case, the app will switch to
downloading a lower quality stream but will probably play out all the content
it has already downloaded. In the not-allowed case, there's no option to play
out the already downloaded content.

As noted above, though, I still feel this mechanism for indicating restrictions
is a hack, since there is an assumed architecture behind it that distinct
policies require distinct key ids. In practice we have a single key / key id
and the downscaling policy is triggered by a property of the content (its
resolution).

So, this solution forces us to associate multiple key ids with the same key in
order to express the distinct policies. Worse, the association of policy to key
ids is done in a completely undefined way (which will thus probably differ
between CDMs).

It would be cleaner, now that the CSS discussion has concluded this is not a
subset of a more generic requirement, to simply have explicit output protection
events.

Another approach would be to make the key status more detailed: so that the
downscaling / non-allowed status would specify the maximum resolution not
subject to that policy. This would also avoid the awkward additional key ids.

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

Received on Tuesday, 13 January 2015 15:54:40 UTC