- From: <bugzilla@jessica.w3.org>
- Date: Thu, 15 Jan 2015 19:49:28 +0000
- To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27054 --- Comment #10 from David Dorwin <ddorwin@google.com> --- (In reply to Henri Sivonen from comment #9) > (In reply to David Dorwin from comment #7) > > Good point. What restrictions do we need to place on the media? > > As long as the spec e.g. allows non-CENC encryption inside MP4, I think it's > not useful to band the theoretical possibility of instead putting the > encryption outside MP4. In other words, pretending that restricting > encryption to inside the container would in itself be an interop win when > there remain multiple ways to do encryption inside the container seems > illusory. If I understand correctly, you are saying we should NOT restrict encryption to inside the container because the spec theoretically allows MP4 protection schemes other than CENC. (The same applies to the potential to support any other container.) Is that right? This is not about increasing interoperability - it is about stating assumptions about the media that the spec, as written, supports. The assumption that the container is not encrypted is currently fundamental to some of the spec algorithms. The most obvious case is initData extraction, which would not be possible if the container is encrypted (ignoring some type of nested containers). The processing of the media data, including the Encrypted Block Encountered algorithm, also make this assumption. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Thursday, 15 January 2015 19:49:30 UTC