- From: <bugzilla@jessica.w3.org>
- Date: Thu, 27 Sep 2012 19:14:55 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19096
Mark Watson <watsonm@netflix.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |watsonm@netflix.com
--- Comment #1 from Mark Watson <watsonm@netflix.com> 2012-09-27 19:14:55 UTC ---
(In reply to comment #0)
>
> Since ISO BMFF + CENC is a container-level encryption specification, it should
> be sufficient to identify the container format in the call to 'createSession()'
> without regard to the codecs or media types contained, and therefore I propose
> that the ISO BMFF Container Guidelines indicate that the value of the 'type'
> parameter will always be the string "video/mp4", regardless of what codecs may
> be used by the container.
Common Encryption is one encryption scheme which can be used with ISO BMFF. The
use of Common Encryption is signalled by the "cenc" value appearing in the
Scheme Type.
In theory there could be other encryption schemes for ISO BMFF, though it is to
be hoped that people will standardize on CENC. Other schemes could have a
different format for the InitData.
In the absence of actual examples of other schemes, though, I think we could
reasonably require that all ISO BMFF encryption schemes provide initData in the
form of a sequence of ISO BFMM boxes. An application that supports both CENC
and some other hypothetical ISO BMFF encryption scheme can then parse the
initData to see if it contains PSSH boxes or whatever boxes the other
(hypothetical) scheme provides.
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 27 September 2012 19:15:02 UTC