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

[Bug 17672] New: Define Initialization Data for implementations that choose to support the WebM Container

From: <bugzilla@jessica.w3.org>
Date: Mon, 02 Jul 2012 23:39:08 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-17672-2486@http.www.w3.org/Bugs/Public/>

           Summary: Define Initialization Data for implementations that
                    choose to support the WebM Container
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Encrypted Media Extensions
        AssignedTo: adrianba@microsoft.com
        ReportedBy: ddorwin@google.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org

v0.1 of the proposal says "Initialization Data is... container-specific data" 
[1]. To help ensure implementations that choose to support a given format are
interoperable and provide examples for the reader, we should define
Initialization Data along with its use and behavior for common formats. This is
similar to how the Media Source proposal has provided guidance for containers

This bug tracks this task for the WebM Container [3].

Below is a non-exhaustive list of items to address:
* Files should specify encryption parameters per [4] or its successor.
* What are the contents of initData? Likely the key ID for the current Track.
* Such initData would result in a license containing a single key.
* A needkey event would be fired for each key encountered/needed.
* Are the contents of the needkey event fired when an encrypted block is
encountered and no key is available [5] the same as the initial needkey event?
* Are needkey events fired for each Track even if they use the same key in the
same file/stream/source?

Note: As currently written, the proposal would result in each key ID being a
separate session and possibly a separate object (bug 16613). This applies to
different keys for audio and video as well as more complex scenarios.

[3] http://www.webmproject.org/code/specs/container/
[4] http://wiki.webmproject.org/encryption/webm-encryption-rfc

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 Monday, 2 July 2012 23:39:09 UTC

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