Encrypted Media Extensions

Last updated
EME
Encrypted Media Extensions
AbbreviationEME, encrypted-media
Native name
Encrypted Media Extensions
Status W3C Recommendation
Year started2013 (2013)
First publishedMay 10, 2013 (2013-05-10) [1]
Latest version2017-09-18
September 18, 2017;6 years ago (2017-09-18) [2]
Preview versionEditor's Draft
March 20, 2021;3 years ago (2021-03-20) [3]
Organization
[2] [3]
Committee
Editors
  • Joey Parrish [3]
  • Greg Freedman [3]
Former editors
    • David Dorwin (until September 2019 (2019-09))
    • Jerry Smith (until September 2017 (2017-09))
    • Mark Watson (until September 2017 (2017-09))
    • Adrian Bateman (until May 2014 (2014-05))
[2] [3]
Base standards
Domain Digital rights management
Website

Encrypted Media Extensions (EME) is a W3C specification for providing a communication channel between web browsers and the Content Decryption Module (CDM) software which implements digital rights management (DRM). [2] This allows the use of HTML 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 (both discontinued). The use of a third-party key management system may be required, depending on whether the publisher chooses to scramble the keys.

Contents

EME is based on the Media Source Extensions (MSE) specification, [4] which enables adaptive bitrate streaming in HTML audio and video, e.g. using MPEG-DASH with MPEG-CENC protected content. [5] [6]

EME has been highly controversial because it places a necessarily proprietary, closed decryption component which requires per-browser licensing fees into what might otherwise be an entirely open and free software ecosystem. [7] [8] On July 6, 2017, W3C publicly announced its intention to publish an EME web standard, [9] and did so on September 18. [2] On the same day, the Electronic Frontier Foundation, who joined in 2014 to participate in the decision making, [10] published an open letter resigning from W3C. [11]

Support

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

As of 2016, the Encrypted Media Extensions interface has been implemented in the Google Chrome, [13] Internet Explorer, [14] Safari, [15] Firefox, [16] and Microsoft Edge [17] 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, [18] Firefox introduced EME support on Windows platforms in May 2015, originally using Adobe's Primetime DRM library, later replaced with the Widevine library (CDM). 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. [16] [19] Additionally, it is always possible to disable DRM in Firefox, which then not only disables EME, but also uninstalls the Widevine DRM libraries. [20]

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

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. [31]

Content Decryption Modules

Criticism

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

In July 2020, Reddit started using a fingerprinting mechanism that involves loading every DRM module that browsers can support, and logs what ends up loading as part of the data collected. Users noticed this when Firefox began alerting them that Reddit "required" them to load DRM software to play media, although none of the media on the page actually needed it. [43]

As of 2020, the ways in which EME interferes with open source have become concrete. None of the widely used CDMs are being licensed to independent open-source browser providers without paying a per-browser licensing fee (particularly to Google – for their Widevine CDM, which is used in nearly all recently developed web browsers). [7]

See also

Related Research Articles

<span class="mw-page-title-main">Firefox</span> Free and open-source web browser by Mozilla

Mozilla Firefox, or simply Firefox, is a free and open-source web browser developed by the Mozilla Foundation and its subsidiary, the Mozilla Corporation. It uses the Gecko rendering engine to display web pages, which implements current and anticipated web standards. Firefox is available for Windows 10 or later versions, macOS, and Linux. Its unofficial ports are available for various Unix and Unix-like operating systems, including FreeBSD, OpenBSD, NetBSD, and other platforms. It is also available for Android and iOS. However, as with all other iOS web browsers, the iOS version uses the WebKit layout engine instead of Gecko due to platform requirements. An optimized version is also available on the Amazon Fire TV as one of the two main browsers available with Amazon's Silk Browser.

<span class="mw-page-title-main">Favicon</span> Icon associated with a particular web site

A favicon, also known as a shortcut icon, website icon, tab icon, URL icon, or bookmark icon, is a file containing one or more small icons associated with a particular website or web page. A web designer can create such an icon and upload it to a website by several means, and graphical web browsers will then make use of it. Browsers that provide favicon support typically display a page's favicon in the browser's address bar and next to the page's name in a list of bookmarks. Browsers that support a tabbed document interface typically show a page's favicon next to the page's title on the tab, and site-specific browsers use the favicon as a desktop icon.

<span class="mw-page-title-main">Browser wars</span> Competition between web browsing applications for share of worldwide usage

A browser war is a competition for dominance in the usage share of web browsers. The "first browser war" (1995–2001) consisted of Internet Explorer and Netscape Navigator, and the "second browser war" (2004-2017) between Internet Explorer, Firefox, and Google Chrome.

This is a comparison of both historical and current web browsers based on developer, engine, platform(s), releases, license, and cost.

<span class="mw-page-title-main">HTML5</span> Fifth and previous version of HyperText Markup Language

HTML5 is a markup language used for structuring and presenting hypertext documents on the World Wide Web. It was the fifth and final major HTML version that is now a retired World Wide Web Consortium (W3C) recommendation. The current specification is known as the HTML Living Standard. It is maintained by the Web Hypertext Application Technology Working Group (WHATWG), a consortium of the major browser vendors.

<span class="mw-page-title-main">Microsoft Silverlight</span> Application framework for writing and running rich Internet applications

Microsoft Silverlight is a discontinued application framework designed for writing and running rich internet applications, similar to Adobe's runtime, Adobe Flash. While early versions of Silverlight focused on streaming media, later versions supported multimedia, graphics, and animation, and gave support to developers for CLI languages and development tools. Silverlight was one of the two application development platforms for Windows Phone, but web pages using Silverlight did not run on the Windows Phone or Windows Mobile versions of Internet Explorer, as there was no Silverlight plugin for Internet Explorer on those platforms.

<span class="mw-page-title-main">Internet Explorer 9</span> Web browser for Windows released in 2011

Internet Explorer 9 or IE9 is the ninth major version of the Internet Explorer web browser for Windows. It was released by Microsoft on March 14, 2011, as the successor to Internet Explorer 8. Microsoft released Internet Explorer 9 as a major out-of-band version that was not tied to the release schedule of any particular version of Windows, unlike previous versions. It is the first version of Internet Explorer not to be bundled with a Windows operating system, although some OEMs have installed it with Windows on their PCs. Internet Explorer 9 was the last version to be called Windows Internet Explorer. The software was rebranded simply as Internet Explorer starting with the release of Internet Explorer 10.

Web storage, sometimes known as DOM storage, is a standard JavaScript API provided by web browsers. It enables websites to store persistent data on users' devices similar to cookies, but with much larger capacity and no information sent in HTTP headers. There are two main web storage types: local storage and session storage, behaving similarly to persistent cookies and session cookies respectively. Web Storage is standardized by the World Wide Web Consortium (W3C) and WHATWG, and is supported by all major browsers.

The HTML5 draft specification adds video and audio elements for embedding video and audio in HTML documents. The specification had formerly recommended support for playback of Theora video and Vorbis audio encapsulated in Ogg containers to provide for easier distribution of audio and video over the internet by using open standards, but the recommendation was soon after dropped.

HTTP Live Streaming is an HTTP-based adaptive bitrate streaming communications protocol developed by Apple Inc. and released in 2009. Support for the protocol is widespread in media players, web browsers, mobile devices, and streaming media servers. As of 2022, an annual video industry survey has consistently found it to be the most popular streaming format.

<span class="mw-page-title-main">WebGL</span> JavaScript bindings for OpenGL in web browsers

WebGL is a JavaScript API for rendering interactive 2D and 3D graphics within any compatible web browser without the use of plug-ins. WebGL is fully integrated with other web standards, allowing GPU-accelerated usage of physics, image processing, and effects in the HTML canvas. WebGL elements can be mixed with other HTML elements and composited with other parts of the page or page background.

HTML video is a subject of the HTML specification as the standard way of playing video via the web. Introduced in HTML5, it is designed to partially replace the object element and the previous de facto standard of using the proprietary Adobe Flash plugin, though early adoption was hampered by lack of agreement as to which video coding formats and audio coding formats should be supported in web browsers. As of 2020, HTML video is the only widely supported video playback technology in modern browsers, with the Flash plugin being phased out.

Modern HTML5 has feature-parity with the now-obsolete Adobe Flash. Both include features for playing audio and video within web pages. Flash was specifically built to integrate vector graphics and light games in a web page, features that HTML5 also supports.

Dynamic Adaptive Streaming over HTTP (DASH), also known as MPEG-DASH, is an adaptive bitrate streaming technique that enables high quality streaming of media content over the Internet delivered from conventional HTTP web servers. Similar to Apple's HTTP Live Streaming (HLS) solution, MPEG-DASH works by breaking the content into a sequence of small segments, which are served over HTTP. An early HTTP web server based streaming system called SProxy was developed and deployed in the Hewlett Packard Laboratories in 2006. It showed how to use HTTP range requests to break the content into small segments. SProxy shows the effectiveness of segment based streaming, gaining best Internet penetration due to the wide deployment of firewalls, and reducing the unnecessary traffic transmission if a user chooses to terminate the streaming session earlier before reaching the end. Each segment contains a short interval of playback time of content that is potentially many hours in duration, such as a movie or the live broadcast of a sport event. The content is made available at a variety of different bit rates, i.e., alternative segments encoded at different bit rates covering aligned short intervals of playback time. While the content is being played back by an MPEG-DASH client, the client uses a bit rate adaptation (ABR) algorithm to automatically select the segment with the highest bit rate possible that can be downloaded in time for playback without causing stalls or re-buffering events in the playback. The current MPEG-DASH reference client dash.js offers both buffer-based (BOLA) and hybrid (DYNAMIC) bit rate adaptation algorithms. Thus, an MPEG-DASH client can seamlessly adapt to changing network conditions and provide high quality playback with few stalls or re-buffering events.

Content Security Policy (CSP) is a computer security standard introduced to prevent cross-site scripting (XSS), clickjacking and other code injection attacks resulting from execution of malicious content in the trusted web page context. It is a Candidate Recommendation of the W3C working group on Web Application Security, widely supported by modern web browsers. CSP provides a standard method for website owners to declare approved origins of content that browsers should be allowed to load on that website—covered types are JavaScript, CSS, HTML frames, web workers, fonts, images, embeddable objects such as Java applets, ActiveX, audio and video files, and other HTML5 features.

HTML audio is a subject of the HTML specification, incorporating audio input, playback, and synthesis, all in the browser.

<span class="mw-page-title-main">VP9</span> Open and royalty-free video coding format released by Google in 2013

VP9 is an open and royalty-free video coding format developed by Google.

Media Source Extensions (MSE) is a W3C specification that allows JavaScript to send byte streams to media codecs within web browsers that support HTML video and audio. Among other possible uses, this allows the implementation of client-side prefetching and buffering code for streaming media entirely in JavaScript. It is compatible with, but should not be confused with, the Encrypted Media Extensions (EME) specification, and neither requires the use of the other, although many EME implementations are only capable of decrypting media data provided via MSE.

Bitmovin is a multimedia technology company which provides services that transcode digital video and audio to streaming formats using cloud computing, and streaming media players. Founded in 2013, the Austrian company contributes to MPEG-DASH, an open standard that allows streaming video to be played in HTML video and Flash Video web players.

Widevine is a proprietary digital rights management (DRM) system developed by Google. It provides content protection for media. Widevine is divided into three security levels with differing levels of protection depending on the hardware present on the device. Widevine is included in most major web browsers and in Android and iOS.

References

  1. ↑ "Encrypted Media Extensions Publication History – W3C". W3C. n.d. Retrieved 2021-04-20.
  2. 1 2 3 4 5 6 HTML Media Extensions Working Group (18 September 2017). Dorwin, David; Smith, Jerry; Watson, Mark; Bateman, Adrian (eds.). "Encrypted Media Extensions W3C Recommendation". W3C. Retrieved 2021-04-20.
  3. 1 2 3 4 5 6 Media Working Group; et al. (Media Working Group) (2021-03-20). Parrish, Joey; Freedman, Greg; Dorwin, David; Smith, Jerry; Watson, Mark; Bateman, Adrian (eds.). "Encrypted Media Extensions". w3c.github.io. Editor's Draft. Retrieved 2021-04-20.
  4. ↑ "Media Source Extensions™". w3c.github.io. Retrieved 2020-08-18.
  5. ↑ David Dorwin. "ISO Common Encryption EME Stream Format and Initialization Data". W3C. Archived from the original on 2015-02-19.
  6. ↑ Lederer, Stefan (February 2, 2015). "Why YouTube & Netflix use MPEG-DASH in HTML5". Bitmovin.
  7. 1 2 "Three years after the W3C approved a DRM standard, it's no longer possible to make a functional indie browser". Boing Boing. 2020-01-08. Retrieved 2020-08-18.
  8. ↑ 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.
  9. ↑ "W3C Announcement" . Retrieved 12 July 2017.
  10. ↑ Harcourt, Alison (31 January 2020). Global Standard Setting in Internet Governance. Christou, George, 1973–, Simpson, Seamus. (First ed.). Oxford. p. 96. ISBN   978-0-19-257859-4. OCLC   1140150076.{{cite book}}: CS1 maint: location missing publisher (link)
  11. ↑ Doctorow, Cory (18 September 2017). "An open letter to the W3C Director, CEO, team and membership". Electronic Frontier Foundation. Retrieved 18 September 2017.
  12. ↑ Anthony Park and Mark Watson (April 15, 2013). "HTML5 Video at Netflix". Netflix.
  13. ↑ Weinstein, Rafael (26 February 2013). "Chrome 26 Beta: Template Element & Unprefixed CSS Transitions". Chromium Blog. Retrieved 31 August 2014.
  14. ↑ "Supporting Encrypted Media Extensions with Microsoft PlayReady DRM in web browsers". Windows app development. Retrieved 31 August 2014.
  15. ↑ 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.
  16. 1 2 "Firefox 38 arrives with contentious closed-source DRM integrated by default". PC World . IDG. 13 May 2015. Retrieved 12 August 2015.
  17. ↑ Mohrland, Jesse; Smith, Jerry (October 27, 2015). "Using Encrypted Media Extensions for interoperable protected media". Microsoft.
  18. ↑ Mozilla begrudgingly brings Netflix support to Linux with DRM in Firefox
  19. ↑ Jeremy Kirk (May 15, 2014). "Mozilla hates it, but streaming video DRM is coming to Firefox". PCWorld.
  20. 1 2 "Firefox 52: Adobe Primetime CDM removal – gHacks Tech News". www.ghacks.net. Retrieved 2019-05-31.
  21. ↑ Netflix system requirements for HTML5 Player and Silverlight
  22. ↑ Anthony Park and Mark Watson (26 June 2013). "HTML5 Video in IE 11 on Windows 8.1". Netflix.
  23. ↑ Anthony Park and Mark Watson (3 June 2014). "HTML5 Video in Safari on OS X Yosemite". Netflix.
  24. ↑ "The Status of MPEG-DASH today, and why Youtube & Netflix use it in HTML5". bitmovin GmbH. 2 Feb 2015. Archived from the original on 3 April 2016. Retrieved 9 February 2015.
  25. ↑ NexPlayer: Passion for High Quality Video Services
  26. ↑ THEOplayer by OpenTelly: HLS and MPEG-DASH player for HTML5 MSE and EME
  27. ↑ "bitdash MPEG-DASH player for HTML5 MSE and EME". Archived from the original on 2016-07-10. Retrieved 2015-02-09.
  28. ↑ bitdash HTML5 EME DRM demo area
  29. ↑ dash.js
  30. ↑ rx-player
  31. ↑ 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.
  32. 1 2 "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.
  33. ↑ "Boris Zabrasky opposing EME" . Retrieved 10 June 2016.
  34. ↑ "Ian Hickson opposing EME" . Retrieved 10 June 2016.
  35. ↑ "Richard Stallman Braved a Winter Storm Last Night to March Against DRM". 21 March 2016. Retrieved 10 June 2016.
  36. ↑ Stallman, Richard (Nov 18, 2016). "Can you trust your computer?". Free Software, Free Society . GNU . Retrieved 2018-02-08.
  37. ↑ "4K Netflix arrives on Windows 10, but probably not for your PC". 21 November 2016. Retrieved 26 November 2016.
  38. ↑ "Title 17, Circular 92, Chapter 12 - Copyright.gov" . Retrieved 25 July 2016.
  39. ↑ "EFF's Formal Objection to EME". 29 May 2013. Retrieved 10 June 2016.
  40. ↑ "Save Firefox". 11 May 2016. Retrieved 10 June 2016.
  41. ↑ "Open Letter to W3C". 12 May 2016. Retrieved 10 June 2016.
  42. ↑ "Interoperability and the W3C: Defending the Future from the Present". 30 March 2016. Retrieved 10 June 2016.
  43. ↑ "Reddit's website uses DRM for fingerprinting". smitop.com. 8 July 2020. Retrieved 2020-07-12.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.