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

[Bug 19810] New: Should key IDs be required in content and addKey()'s parameter?

From: <bugzilla@jessica.w3.org>
Date: Thu, 01 Nov 2012 00:43:33 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-19810-2486@http.www.w3.org/Bugs/Public/>

          Priority: P3
            Bug ID: 19810
                CC: mike@w3.org, public-html-media@w3.org
          Assignee: adrianba@microsoft.com
           Summary: Should key IDs be required in content and addKey()'s
        QA Contact: public-html-bugzilla@w3.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: ddorwin@google.com
          Hardware: All
            Status: NEW
           Version: unspecified
         Component: Encrypted Media Extensions
           Product: HTML WG

The draft currently supports content and |key| values (licenses) that do not
use a key ID.

This adds complexity to the addKey() [1] and Encrypted Block Encountered [2]
algorithma. If there are no use cases for this, we should eliminate this
support and simplify the algorithms. The no key behavior is a little confusing

Note that the Potentially Encrypted Stream Encountered [3] algorithm would
still need to deal with key IDs, assuming we want to avoid sending an event
when we already know the key (issue 16553).


You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 1 November 2012 00:43:34 UTC

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