[Bug 17673] Define Initialization Data for implementations that choose to support the ISO Base Media File Format from bugzilla@jessica.w3.org on 2013-08-20 (public-html-bugzilla@w3.org from August 2013)

From: <bugzilla@jessica.w3.org>
Date: Tue, 20 Aug 2013 20:35:58 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-17673-2486-AUbuXciAzx@http.www.w3.org/Bugs/Public/>

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

--- Comment #23 from Mark Watson <watsonm@netflix.com> ---
If in our "ISO BMFF with Common Encryption" we simply say the initData is a
sequence of PSSH boxes then that is sufficient, IMO.

The problem of how to add other schemes doesn't need to be addressed until
sections for other schemes are proposed. We know that there are several ways
another scheme could be added in a backwards compatible fashion:
- put some different boxes in the initData
- put something which is not a box in the initData, provided bytes 4-7 don't
read p.s.s.h.
- use PSSH boxes but define separate system ids

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 20 August 2013 20:36:00 UTC