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

[Bug 20338] New: Explicitly specify whether initData is required for Clear Key

From: <bugzilla@jessica.w3.org>
Date: Tue, 11 Dec 2012 07:25:21 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-20338-2486@http.www.w3.org/Bugs/Public/>

            Bug ID: 20338
           Summary: Explicitly specify whether initData is required for
                    Clear Key
    Classification: Unclassified
           Product: HTML WG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Encrypted Media Extensions
          Assignee: adrianba@microsoft.com
          Reporter: ddorwin@google.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org

The type and initData parameters to createSession() are optional [1]. The Clear
Key section [2] says what initData should be but not whether it is required.
This section should explicitly state that it is required or optional.

While there is no real reason to require it, it may make implementations easier
if they can just return an error immediately rather than having to implement
handle the case where initData is not provided. In addition, Clear Key is
unlikely to be used in scenarios where initData may not be desired. The only
real use case would seem to be to create a session without any knowledge of the
media and then immediately call addKey() with a key, possibly without
contacting a server.

See also bug 19810, which proposes requiring key IDs, which are related to
initData, in the licenses provided to addKey().

To be most compatible, maybe the text should say initData is required for
containers that support it.


You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 11 December 2012 07:30:16 UTC

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