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

RE: Oppose DRM ! Re: CfC: to publish Encrypted Media Extensions specification as a First Public Working Draft (FPWD)

From: Adrian Bateman <adrianba@microsoft.com>
Date: Fri, 22 Feb 2013 10:56:29 +0000
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Mark Watson <watsonm@netflix.com>
CC: Henri Sivonen <hsivonen@iki.fi>, "Timothy B. Terriberry" <tterriberry@mozilla.com>, "public-html-media@w3.org" <public-html-media@w3.org>, Andrew Davis <papyromancer@gmail.com>
Message-ID: <b2e38952a7e94522a24ce8a5a3839b5c@BL2PR03MB604.namprd03.prod.outlook.com>
I think it would help if you provided a bit more information about the goal here. I don't think this bug is currently actionable by the editors - there's no proposal made. Since EME isn't a content protection system but a way of abstracting different content protection systems you might usefully contribute by filing bugs for EME if you think it can't support those open source systems.

From: Silvia Pfeiffer [mailto:silviapfeiffer1@gmail.com]
Sent: Thursday, February 21, 2013 11:23 PM
To: Mark Watson
Cc: Henri Sivonen; Timothy B. Terriberry; public-html-media@w3.org; Andrew Davis
Subject: Re: Oppose DRM ! Re: CfC: to publish Encrypted Media Extensions specification as a First Public Working Draft (FPWD)

FYI: I've registered a bug on EME to request these open source systems being analysed and a statement being made about how they compare to EME:

I think it will be useful for the participants of the HTML WG to understand the differences.

On Wed, Feb 13, 2013 at 2:08 AM, Mark Watson <watsonm@netflix.com<mailto:watsonm@netflix.com>> wrote:

Sent from my iPhone

On Feb 12, 2013, at 5:55 AM, "Henri Sivonen" <hsivonen@iki.fi<mailto:hsivonen@iki.fi>> wrote:

> (Moving from -admin to -media.)
> On Tue, Feb 12, 2013 at 5:03 AM, Mark Watson <watsonm@netflix.com<mailto:watsonm@netflix.com>> wrote:
>> There is also this: http://sourceforge.net/projects/openipmp/ ?
> It seems that this is an implementation of OMA DRM. Upon quick
> inspection, it seems to me that OMA DRM depends on a client-side
> secret (private key for a public key) that the user can't read or
> replace and on the DRM-related software on the client device not being
> user-modifiable. Have I understood correctly?
I'm not familiar with how the key provisioning works, but yes, in general DRM relies on there being a non-user-modifiable* component on the client side (this should be obvious based on the goals of DRM).


* of course I mean 'difficult to modify for some formal definition of difficult'.
> --
> Henri Sivonen
> hsivonen@iki.fi<mailto:hsivonen@iki.fi>
> http://hsivonen.iki.fi/
Received on Friday, 22 February 2013 10:58:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:48:32 UTC