Jump to content

Encrypted Media Extensions

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Citation bot (talk | contribs) at 08:35, 2 April 2020 (Alter: edition. Add: date. Removed URL that duplicated unique identifier. Removed parameters. Some additions/deletions were actually parameter name changes. | You can use this bot yourself. Report bugs here. | Activated by Grimes2 | Category:CS1 maint: extra text | via #UCB_Category). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Encrypted Media Extensions (EME) is a W3C specification for providing a communication channel between web browsers and digital rights management (DRM) agent software.[1] 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 is based on the HTML5 Media Source Extensions specification,[2] which enables adaptive bitrate streaming in HTML5 using e.g. MPEG-DASH with MPEG-CENC protected content.[3][4]

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.[5] On July 6th, 2017, W3C publicly announced its intention to publish EME web standard[6], and did so on September 18th.[1] On the same day, the Electronic Frontier Foundation who joined in 2014 to participate in the decision making[7] published an open letter resigning from W3C.[8]

Support

In April 2013, on the Samsung Chromebook, Netflix became the first company to offer HTML5 video using EME.[9]

As of 2016, the Encrypted Media Extensions interface has been implemented in the Google Chrome,[10] Internet Explorer,[11] Safari,[12] Firefox,[13] and Microsoft Edge[14] browsers.

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,[15] 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.[13][16] Additionally, it is always possible to disable DRM in Firefox, which then not only disables EME, but also uninstalls the CDM Widevine.[17]

Netflix supports HTML5 video using EME with a supported web browser: Chrome, Firefox,[18] Microsoft Edge, Internet Explorer (on Windows 8.1 or newer[19]), or Safari (on OS X Yosemite or newer[20]). YouTube supports the HTML5 MSE.[21] Available players supporting MPEG-DASH using the HTML5 MSE and EME are NexPlayer,[22] THEOplayer[23] by OpenTelly, the bitdash MPEG-DASH player,[24][25] dash.js[26] by DASH-IF or rx-player.[27]

Note that certainly in Firefox and Chrome, EME does not work unless the media is supplied via Media Source Extensions.


Version 4.3 and subsequent versions of Android support EME.[28]

Content Decryption Modules

Criticism

EME has faced strong criticism from both inside[31][32] and outside W3C.[33][34] The major issues for criticism are implementation issues for open-source browsers, entry barriers for new browsers, lack of interoperability,[35] concerns about privacy and accessibility and possibility of legal trouble in the United States due to Chapter 12[36] of the DMCA.[37][38][39][40]

See also

References

  1. ^ a b "Encrypted Media Extensions W3C Recommendation". W3C. 18 September 2017. Retrieved 18 September 2017.
  2. ^ HTML5 MSE
  3. ^ David Dorwin. "ISO Common Encryption EME Stream Format and Initialization Data". W3C. Archived from the original on 2015-02-19.
  4. ^ Lederer, Stefan (February 2, 2015). "Why YouTube & Netflix use MPEG-DASH in HTML5". Bitmovin.
  5. ^ 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.
  6. ^ "W3C Announcement". Retrieved 12 July 2017.
  7. ^ Harcourt, Alison. Global Standard Setting in Internet Governance. Christou, George, 1973-, Simpson, Seamus. (First ed.). Oxford. p. 96. ISBN 978-0-19-257859-4. OCLC 1140150076.
  8. ^ "EFF Open Letter". 18 September 2017. Retrieved 18 September 2017.
  9. ^ Anthony Park and Mark Watson (April 15, 2013). "HTML5 Video at Netflix". Netflix.
  10. ^ Weinstein, Rafael (26 February 2013). "Chrome 26 Beta: Template Element & Unprefixed CSS Transitions". Chromium Blog. Retrieved 31 August 2014.
  11. ^ "Supporting Encrypted Media Extensions with Microsoft PlayReady DRM in web browsers". Windows app development. Retrieved 31 August 2014.
  12. ^ 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.
  13. ^ a b "Firefox 38 arrives with contentious closed-source DRM integrated by default". PC World. IDG. 13 May 2015. Retrieved 12 August 2015.
  14. ^ Mohrland, Jesse; Smith, Jerry (October 27, 2015). "Using Encrypted Media Extensions for interoperable protected media". Microsoft.
  15. ^ Mozilla begrudgingly brings Netflix support to Linux with DRM in Firefox
  16. ^ Jeremy Kirk (May 15, 2014). "Mozilla hates it, but streaming video DRM is coming to Firefox". PCWorld.
  17. ^ "Firefox 52: Adobe Primetime CDM removal - gHacks Tech News". www.ghacks.net. Retrieved 2019-05-31.
  18. ^ Netflix system requirements for HTML5 Player and Silverlight
  19. ^ Anthony Park and Mark Watson (26 June 2013). "HTML5 Video in IE 11 on Windows 8.1". Netflix.
  20. ^ Anthony Park and Mark Watson (3 June 2014). "HTML5 Video in Safari on OS X Yosemite". Netflix.
  21. ^ "The Status of MPEG-DASH today, and why Youtube & Netflix use it in HTML5". bitmovin GmbH. 2 Feb 2015.
  22. ^ NexPlayer: Passion for High Quality Video Services
  23. ^ THEOplayer by OpenTelly: HLS and MPEG-DASH player for HTML5 MSE and EME
  24. ^ bitdash MPEG-DASH player for HTML5 MSE and EME
  25. ^ bitdash HTML5 EME DRM demo area
  26. ^ dash.js
  27. ^ rx-player
  28. ^ 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.
  29. ^ "Firefox 52: Adobe Primetime CDM removal - gHacks Tech News". www.ghacks.net. Retrieved 2019-05-31.
  30. ^ a b "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.
  31. ^ "Boris Zabrasky opposing EME". Retrieved 10 June 2016.
  32. ^ "Ian Hickson opposing EME". Retrieved 10 June 2016.
  33. ^ "Richard Stallman Braved a Winter Storm Last Night to March Against DRM". 21 March 2016. Retrieved 10 June 2016.
  34. ^ Stallman, Richard (Nov 18, 2016). "Can you trust your computer?". Free Software, Free Society. GNU. Retrieved 2018-02-08.
  35. ^ "4K Netflix arrives on Windows 10, but probably not for your PC". 21 November 2016. Retrieved 26 November 2016.
  36. ^ "Title 17, Circular 92, Chapter 12 - Copyright.gov". Retrieved 25 July 2016.
  37. ^ "EFF's Formal Objection to EME". 29 May 2013. Retrieved 10 June 2016.
  38. ^ "Save Firefox". 11 May 2016. Retrieved 10 June 2016.
  39. ^ "Open Letter to W3C". 12 May 2016. Retrieved 10 June 2016.
  40. ^ "Interoperability and the W3C: Defending the Future from the Present". 30 March 2016. Retrieved 10 June 2016.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Encrypted_Media_Extensions&oldid=948660670"