5 ms·
Why should DRM be part of a standard? Aren't plug-ins sufficient?
by Zigurd 13y ago
Why should DRM be part of a standard? Aren't plug-ins sufficient?
- duncan_bayne 13y agoThere are several technical reasons why EME is superior to the existing solutions; in particular, usability and ease of implementation are two. However that doesn't address the fundamental problem that EME breaks the Open Web.
- Zigurd 13y agoI could sort of get "ease of implementation" but would trade that on behalf of the implementers to keep their secret bullshit out of standards. Have they got an actual case that says it's easier versus plug-in implementations that would, in real world cases, rely on libraries the content publishers agree to use?
- yk 13y agoYes, malware. EME creates a nice standard compatible way for bidirectional communication with arbitrary servers, for native code run with the privileges of the user. ( By now there is at least a security considerations section in their standard... what could possibly go wrong.)
- gsnedders 13y agoEME essentially defines a wrapper around a module, which can quite easily be a plugin, that implements the DRM. You can view it as a means to require smaller plugins than NPAPI, PPAPI, etc.
- Zigurd 13y agoSo, why have that discussion inside a standards discussion, especially if it brings in confidentiality requirements? Let the publishers talk among themselves and write their plug-ins.
- duncan_bayne 13y agoIn my more paranoid moments, I worry that the answer is: this work is explicitly intended to break the Open Web as we know it. This is why I'm so keen to get all the requirements out in the open and start discussing them transparently.
- eponeponepon 13y agoPersonally, even in my least paranoid moments, I think that's a certainty. Why let things be open when you can charge people for the key? See also: turnpikes.
- robmcm 13y agoThe problem is a normal plugin doesn't allow a browser vendor to write their own version. (iPhone + Flash for example). Perhaps a plugin standard and API would solve it, then a vendor can build their own plugin (Apple) and allow others to use a non shipped third party (Firefox).
- hsivonen 13y agoIf Apple wanted to, they could write their own implementation of the non-DRM parts of swf. Mozilla is doing this in Shumway. Apple did this for PDF. Of course, just like you aren't allowed to interoperate with an EME CDM without permission, you aren't allowed to interoperate with the DRM part of Flash (called Adobe Access) without permission. (Or the DRM part Silverlight called PlayReady, which, unsurprisingly, Moonlight does not clone.)
- robmcm 13y agoSure, but I believe that Adobe didn't really want anyone to clone flash (at least not in the early days). If this was the goal from the outset the DRM parts could be described in the same way the HTML5 ones are being.