Bugzilla – Bug 20552
Encrypted Block Encountered algorithm should not reference Initialization Data
Last modified: 2013-04-30 01:54:53 UTC
http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html#algorithms-enrypted-block step 4 refers to Initialization Data in the block or its parent and extracts the key ID from it. However, Initialization Data is not always the source of the current block's key identifier. ISO CENC is one such case.
I believe the issue is that initData does not always directly set the key ID for a given block. For example, with ISO CENC, the initData is a PSSH, but the key ID is set with another box.
We should fix this at the same time as bug 19788 and bug 19810, which removes another use of initData. With the combination, we do not need step 4  and we don't need to support the case where there is no key ID. Thus, step 6.2  can become "Let block key ID be the key ID for the current block."
 "If the block (or its parent entity) has Initialization Data, let block initData be that initialization data."
 "If block initData is not null and contains a key ID, let block key ID be that ID."
I removed the last references to Initialization Data in the Encrypted Block Encountered algorithm in https://dvcs.w3.org/hg/html-media/rev/dbfb9104f0ee after removing the uses of it by fixing bug 19788 and bug 19810.