W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2012

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 24 Jul 2012 20:27:42 +0000
Message-Id: <E1Stlhm-0005lV-9o@jessica.w3.org>
To: public-html-bugzilla@w3.org

Mark Watson <watsonm@netflix.com> changed:

           What    |Removed                     |Added
                 CC|                            |watsonm@netflix.com

--- Comment #3 from Mark Watson <watsonm@netflix.com> 2012-07-24 20:27:42 UTC ---
I propose the following:

"The format of the initData for the ISO Base Media File Format is dependent on
the Scheme Type indicated in the Protection Scheme Information Box.

When the Scheme Type indicates ISO Common Encryption (ISO/IEC23001-7), "cenc",
the initData shall consist of one or more Protection System Specific Header
("pssh") boxes."

Regarding multiple keys. I think this is up to the CDM and its server-side
peer: if the license comes back without all the keys and the Media Element
actually encounters samples encrypted with a key not in the license then this
would cause a new needKey event, with the same initData again.

Regarding ClearKey: to have this work with CENC indeed requires us to define a
SystemID and PSSH contents for ClearKey. This should contain the keyids of the
required keys. We may wish to say that for the ClearKey/CENC combination the
key request message contains the key ids of the requested keys and the key
message contains the keys. If the key id and key size is known (for example
from the PSSH), then these can both simply be the concatenation of the ids or

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 24 July 2012 20:27:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:30 UTC