Digital Rights Management (DRM) is a technology that enables digital content creators to control how and who has access to their products. Ideally the DRM is completely transparent to the user.
DRM typically has three objectives: to establish copyright for a particular content, to manage the distribution of that content, and to control what the consumer does with that content once it has been distributed.
One of the deficiencies that HTML5 has is a lack of a standard DRM system. Google, Microsoft, Netflix haves made a proposal to include DRM in HTML5.1.
W3C published a draft1 for Encrypted Media Extensions (EME), a platform that would allow the use of DRM directly into HTML5. The standard does not make a DRM itself to decide who can view or copy a video, but provides a standard mechanism that allows the browser to call a plug-in (developed by others) that will handle the job. EME allows using the sites without the additional plug-ins for DRM video playback, which is a benefit for the users.
Netflix is a popular on-demand video streaming with DRM, however, Linux is not supported because Netflix2 use Silverlight to deliver a video streaming, and Silverlight is only officially available in Windows and OS X.
W3C’s Encrypted Media Extensions draft says:
“HTML5 doesn't provide direct support, nor any barrier, to using DRM in video. It currently expects this to be handled by the particular codec/implementation. There are implementations which allow for DRM in HTML5 video.” 4
DRM Browser Support
|Chrome 31||No (Will have in the future)|
|Internet Explorer 11||Yes|
Source: HTML5 Test
Current DRM Solutions
Adobe Access (Adobe)
Supports delivery using dynamic adaptive HTTP streaming (HDS) to Flash and Air based players as well as to IOS & Android apps.3
Microsoft PlayReady (Microsoft)
Microsoft’s PlayReady DRM is a robust DRM solution providing cross platform and device capabilities to desktop, mobile and connected devices.3
Widevine DRM (Google)
A number of third party integrators including Encoding.com do offer custom Widevine implementations to customers and Limelight have a Widevine solution as part of their broader CDN offering.3
In conclusion, there is a lot of discussion about if DRM should be included or not in HTML5, the proposal is still in the stage of "draft", but has a strong support to be included. However any agreement will take time to be reached, and if a consensus is not reached, it is likely that each browser will implement its own separate system. This may mean, that each solution will not be available on all platforms, leaving a significant number of devices without access to video content.