Mark Watson 3/14/2016
Private. Collaborators only.
It’s worth noting that the Encrypted Media Extensions specification and its implementations have evolved significantly during the several years we have been working on them in W3C. DRMs under EME are now rather commoditized: having common features and using common, standard, encrypted files. They can be sandboxed, as Chrome and Mozilla have done, such that the DRM has no network access and is permitted to persist data or otherwise access the machine only as allowed by the (open source) sandbox. There are strict rules for privacy-sensitive identifiers and user consent. Users can completely disable the DRM, clear its storage, reset any identifiers. Sites using EME will be required to deploy HTTPS.
These changes in how DRM is integrated with the web (because it was, as has been mentioned, very much there before all of this) likely would not have happened without the W3C’s involvement.
I think it’s fair to say that few in the content industry share the view, expressed here, that the business risk of removing DRM is low making the likelihood of a “quiet death” any time soon very small.