[danjones]

It's great to see Netflix pushing for HTML 5 media encryption, it's one of the things the orignal spec for these elements lacked. Once it becomes standard across the browsers we'll hopefully see more media publishers come onboard supporting HTML 5.

[wmf]

Because EME makes the DRM pluggable, it's never going to be standard across browsers. Different browsers will have incompatible DRM plugins.

[notatoad]

As i understand it, it's a standard API that the browser exposes to external processes. The browser doesn't have any DRM plugins, just EME. the decryption happens outside the browser, and any decryption modules installed on the system will be available to all browsers.

[wmf]

You can say it any way you want, but Apple devices will only support FairPlay (which will not be available on any non-Apple platform) and I would expect Chrome OS to only support Widevine. There will not be interoperability.

[likeclockwork]

And frankly, I don't want any of that crap on my machine.

[hsivonen]

No, EME is an API that the browser exposes to site-supplied JavaScript code. The JavaScript code uses EME to talk with a Content Decryption Module (CDM) whose exact characteristics (including the protocol you talk with it; EME sees byte buffers) is unspecified and out of the scope of the EME spec. The interface between the browser and the CDM is not being standardized.

The CDM is basically a new kind of proprietary component that exposes a CDM-specific protocol to the Web and that is annexed to the side of the browser. You should not assume the distribution model to be the same as with traditional plug-ins: E.g. in the case of Chrome OS, the CDM comes from Google itself.

[ihsw]

It's a binary blob loaded on-demand with hardware access, what's the worst that could happen?