W3C home > Mailing lists > Public > public-html-media@w3.org > September 2013

Re: CfC: to publish a Encrypted Media Exstensions" hearbeat Working Draft

From: Mark Watson <watsonm@netflix.com>
Date: Tue, 24 Sep 2013 08:06:32 -0700
Message-ID: <CAEnTvdD18=v4VganXKdUtkcDYnRb=gCOpQvnOEe7MHqY1uRC5g@mail.gmail.com>
To: Mhyst <mhysterio@gmail.com>
Cc: "public-html-media@w3.org" <public-html-media@w3.org>
On Tue, Sep 24, 2013 at 8:01 AM, Mhyst <mhysterio@gmail.com> wrote:

> There are more lines in the text that led me to think like that:
> In the "1.2.1. Content Decryption Module (CDM)" section:
> "Implementations may or may not separate the implementations of CDMs
> and may or may not treat them as separate from the user agent."
> Then, above in the "Goals" section you can read this:
> "Flexibility (and control) for applications and content providers
> without requiring client/user agent updates."
> The documents says the CDM can be implemented in two ways: as separate
> binaries or user-agent's part.
> In any case, I think the user should know.
> Absolutely, the user should know. I don't think anyone has suggested
otherwise. Nothing is intended to be any different from the normal way UA
capabilities / extensions are handled. The user must approve for anything
new to be installed. It's not the intention that CDMs be installed by the
user, but it's not excluded either.

Received on Tuesday, 24 September 2013 15:07:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:33:01 UTC