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: https://www.w3.org/Bugs/Public/show_bug.cgi?id=21081 I think it will be useful for the participants of the HTML WG to understand the differences. Regards, Silvia. On Wed, Feb 13, 2013 at 2:08 AM, Mark Watson <watsonm@netflix.com> wrote: > > > Sent from my iPhone > > On Feb 12, 2013, at 5:55 AM, "Henri Sivonen" <hsivonen@iki.fi> wrote: > > > (Moving from -admin to -media.) > > > > On Tue, Feb 12, 2013 at 5:03 AM, Mark Watson <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). > > ...Mark > > * of course I mean 'difficult to modify for some formal definition of > difficult'. > > > > -- > > Henri Sivonen > > hsivonen@iki.fi > > http://hsivonen.iki.fi/ > > >
Received on Friday, 22 February 2013 07:23:40 UTC