Encrypted Media Extensions
Encrypted Media Extensions (EME) is a W3C specification for providing a communication channel between web browsers and digital rights management (DRM) agent software. This allows the use of HTML5 video to play back DRM-wrapped content such as streaming video services without the use of heavy third-party media plugins like Adobe Flash or Microsoft Silverlight. The use of a third-party key management system may be required, depending on whether the publisher chooses to scramble the keys.
EME has been highly controversial because it places a necessarily proprietary, closed component into what might otherwise be an entirely open and free software ecosystem. On July 6 2017, W3C publicly announced its intention to publish EME web standard, and did so on September 18th. On the same day, the Electronic Frontier Foundation published an open letter resigning from W3C.
While backers and the developers of the Firefox web browser were hesitant in implementing the protocol for ethical reasons due to its dependency on proprietary code, Firefox introduced EME support on Windows platforms in May 2015. Firefox's implementation of EME uses an open-source sandbox to load the proprietary DRM modules, which are treated as plug-ins that are loaded when EME-encrypted content is requested. The sandbox was also designed to frustrate the ability for services and the DRM to uniquely track and identify devices.
Netflix supports HTML5 video using EME with a supported web browser: Chrome, Firefox, Microsoft Edge, Internet Explorer (on Windows 8.1 or newer), or Safari (on OS X Yosemite or newer). YouTube supports the HTML5 MSE. Available players supporting MPEG-DASH using the HTML5 MSE and EME are THEOplayer by OpenTelly, the bitdash MPEG-DASH player, dash.js by DASH-IF or rx-player.
Content Decryption Modules
- Adobe Primetime CDM
- Widevine (used in Chrome, Firefox, and Opera among others)
- PlayReady (used in Microsoft Edge or Internet Explorer 11 for Windows 8.1)
- FairPlay (used in Safari in OS X Yosemite)
EME has faced strong criticism from both inside and outside W3C. The major issues for criticism are implementation issues for open-source browsers, entry barriers for new browsers, lack of interoperability, concerns about privacy and accessibility and possibility of legal trouble in the United States due to Chapter 12 of the DMCA.
- Media Source Extensions
- HTML5 § Digital rights management
- World Wide Web Consortium
- Digital rights management
- Defective by Design
- Electronic Frontier Foundation
- Digital Millennium Copyright Act
- "Encrypted Media Extensions W3C Recommendation". W3C. 18 September 2017. Retrieved 18 September 2017.
- HTML5 MSE
- David Dorwin. "ISO Common Encryption EME Stream Format and Initialization Data". W3C. Archived from the original on 2015-02-19.
- Lederer, Stefan (February 2, 2015). "Why YouTube & Netflix use MPEG-DASH in HTML5". Bitmovin.
- Lucian Constantin (24 February 2012). "Proposed Encrypted Media Support in HTML5 Sparks DRM Debate on W3C Mailing List". IT World. IDG News Service. Retrieved 12 October 2015.
- "W3C Announcement". Retrieved 12 July 2017.
- "EFF Open Letter". Retrieved 18 September 2017.
- Anthony Park and Mark Watson (April 15, 2013). "HTML5 Video at Netflix". Netflix.
- Weinstein, Rafael (26 February 2013). "Chrome 26 Beta: Template Element & Unprefixed CSS Transitions". Chromium Blog. Retrieved 31 August 2014.
- "Supporting Encrypted Media Extensions with Microsoft PlayReady DRM in web browsers". Windows app development. Retrieved 31 August 2014.
- Protalinski, Emil (3 June 2014). "Netflix ditches Silverlight for HTML5 on Macs too: Available today in Safari on OS X Yosemite beta". The Next Web. Retrieved 16 October 2014.
- "Firefox 38 arrives with contentious closed-source DRM integrated by default". PC World. IDG. 13 May 2015. Retrieved 12 August 2015.
- Mohrland, Jesse; Smith, Jerry (October 27, 2015). "Using Encrypted Media Extensions for interoperable protected media". Microsoft.
- Mozilla begrudgingly brings Netflix support to Linux with DRM in Firefox
- Jeremy Kirk (May 15, 2014). "Mozilla hates it, but streaming video DRM is coming to Firefox". PCWorld.
- Netflix system requirements for HTML5 Player and Silverlight
- Anthony Park and Mark Watson (26 June 2013). "HTML5 Video in IE 11 on Windows 8.1". Netflix.
- Anthony Park and Mark Watson (3 June 2014). "HTML5 Video in Safari on OS X Yosemite". Netflix.
- "The Status of MPEG-DASH today, and why Youtube & Netflix use it in HTML5". bitmovin GmbH. 2 Feb 2015.
- THEOplayer by OpenTelly: HLS and MPEG-DASH player for HTML5 MSE and EME
- bitdash MPEG-DASH player for HTML5 MSE and EME
- bitdash HTML5 EME DRM demo area
- Ozer, Jan (July–August 2015). "HTML5 Comes of Age: It's Finally Time to Tell Flash Good-bye". Streaming Media Magazine. StreamingMedia.com. Retrieved 2016-01-12.
In mobile markets [...] Android has supported MSE since version 4.1, and EME since version 4.3.
- "THEOplayer Supports All Platforms". theoplayer.com. 2017.
Note that IE10 and IE11 on Windows 7 do not have the MSE/EME API available which is required to playback DRM protected video content in HTML5. As a consequence, it is technically not possible for any HTML5-based video player to playback DRM protected content on these browsers in Windows 7.
- "Boris Zabrasky opposing EME". Retrieved 10 June 2016.
- "Ian Hickson opposing EME". Retrieved 10 June 2016.
- "Richard Stallman Braved a Winter Storm Last Night to March Against DRM". Retrieved 10 June 2016.
- Stallman, Richard (Nov 18, 2016). "Can you trust your computer?". Free Software, Free Society. GNU. Retrieved 2018-02-08.
- "4K Netflix arrives on Windows 10, but probably not for your PC". Retrieved 26 November 2016.
- "Title 17, Circular 92, Chapter 12 - Copyright.gov". Retrieved 25 July 2016.
- "EFF's Formal Objection to EME". Retrieved 10 June 2016.
- "Save Firefox". Retrieved 10 June 2016.
- "Open Letter to W3C". Retrieved 10 June 2016.
- "Interoperability and the W3C: Defending the Future from the Present". Retrieved 10 June 2016.