W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2012

[Bug 16544] Clarify frame handling for frame based encryption

From: <bugzilla@jessica.w3.org>
Date: Sat, 21 Jul 2012 01:10:33 +0000
Message-Id: <E1SsODJ-0004mv-Nl@jessica.w3.org>
To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16544

Mark Watson <watsonm@netflix.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |watsonm@netflix.com

--- Comment #1 from Mark Watson <watsonm@netflix.com> 2012-07-21 01:10:33 UTC ---
The diagram has led to confusion as it shows the "decrypted frames" being
passed back from CDM to the browser.

This is one possibility, but there are other possibilities in which the
decrypted, encoded frames or decrypted encoded and decoded frames remain within
a secure media pipeline provided by the platform.

In these cases the browser may be provided only with a reference to the
decrypted/decoded frames, or some means of controlling the surface on which
they are rendered, but no access to the decrypted media itself.

The details of what is supported and how it is achieved are implementation
dependent and are not expected to be spelled out in the specification. It is
the job of the CDM to communicate, securely, implicitly or explicitly, the type
of security provided to it's peer on the server side as an input to
authorization decisions: i.e. whether the content requested can be played on
the device in question.

-- 
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 Saturday, 21 July 2012 01:10:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 21 July 2012 01:10:36 GMT