[Bug 17673] Define Initialization Data for implementations that choose to support the ISO Base Media File Format

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

--- Comment #21 from David Dorwin <ddorwin@google.com> ---
(In reply to comment #15)
> (In reply to comment #14)
> > If we returned to just reporting |pssh| boxes, we could always fire a
> > needkey event with the |pssh|
> 
> What's the use case for exposing even pssh? It, too, looks like an avenue
> for defeating the interop story of EME by introducing vendor lock-in.

If we decide to surface PSSHes, we could improve interop while also solving the
Clear Key issue by defining a default/EME system ID and PSSH format. We could
recommend including it in all files, and Clear Key as well as any other key
system could use it. Even key systems that support their own system ID could
support it, especially if that ID is not present.

This would allow legacy devices to be supported while moving towards a more
interoperable future.

(In reply to comment #16)
> (In reply to comment #15)
> > (In reply to comment #14)
> > > It appears that trying to support any scheme type (not just CENC) has led us
> > > to include the entire |sinf| box along with |pssh| boxes. This may be adding
> > > complexity and overhead that are otherwise unnecessary.
> > 
> > What's the use case for non-CENC schemes? Since the interoperability story
> > of EME hinges on CENC, supporting non-CENC schemes looks like an avenue for
> > vendor lock-in.
> 
> I would not be opposed to including only CENC schemes.

I think we should at least start here and try to solve the CENC case, which is
already very complex.

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

Received on Tuesday, 20 August 2013 01:11:10 UTC