[Bug 27093] Support for proprietary/system-specific formats in initData should be discouraged/deprecated

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

--- Comment #9 from Mark Watson <watsonm@netflix.com> ---
(In reply to David Dorwin from comment #8)
> (In reply to Joe Steele from comment #7)
> > One correction I forgot to add. The EME spec does not prohibit
> > KeySystem-specific PSSH boxes as far as I am aware. It merely discourages
> > use of them.
> 
> Correct. However, if embedding keys in the content is something you or
> others want to do and the only way to do it is using proprietary PSSH boxes
> and proprietary behavior, such content will never be available across
> clients and content providers will continue to use the proprietary PSSH
> boxes.

Not necessarily. One keysystem may simple be designed such that it's PSSH
contains an encrypted content key (and the license contains the decryption key
for *thst*) wheras another may put the content key itself in the license.

The externally visible behaviour is identical - there is no interoperability
issue - it's just that the different keysystems made different choices about
information distribution between initData and license.

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

Received on Thursday, 30 October 2014 18:58:58 UTC