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

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

          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
                    parameter?
        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
anyway.

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).

[1]
http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html#dom-addkey
[2]
http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html#algorithms-enrypted-block
[3]
http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html#algorithms-encrypted-stream

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Thursday, 1 November 2012 00:43:34 UTC