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

Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals)

From: Henri Sivonen <hsivonen@iki.fi>
Date: Wed, 29 Feb 2012 10:41:53 +0200
Message-ID: <CAJQvAufMO0SvtfE=TzB+wLWz23+7jGqHDTakqPg2qwO_0+FjzA@mail.gmail.com>
To: Mark Watson <watsonm@netflix.com>
Cc: Kornel LesiƄski <kornel@geekhood.net>, "HTML WG (public-html@w3.org)" <public-html@w3.org>, Adrian Bateman <adrianba@microsoft.com>, David Dorwin <ddorwin@google.com>
On Tue, Feb 28, 2012 at 1:27 AM, Mark Watson <watsonm@netflix.com> wrote:
> It's not as clear as it could be, but the intention is that all three of the following are possible, depending on the CDM:
>
> (1) The CDM returns the decrypted frame to the browser
> (2) The CDM handles decryption and decoding and returns the decoded (raw pixels) frame to the browser
> (3) The CDM handles decryption, decoding and rendering and (possibly) returns some kind of reference to the decoded frame to the browser

Cases 1 and 2 don't treat the browser as an adversary while case 3
does. Is Netflix willing to target movies to CDMs that are of type 1
or 2? Does the answer to this question depend on whether the browser
is Open Source? If a CDM of type 1 or 2 is delivered as a
separate-from-browser component on an operating system that allows the
installation of non-system-bundled browser engines, do you expect
there to be a mechanism for the CDM to check who is calling into it?
What kind of mechanism?

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/
Received on Wednesday, 29 February 2012 08:42:28 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:30 UTC