EME

EME

[70] EME (Encrypted Media Extensions) は、 Webブラウザー上で DRM が適用された動画音声を扱うための技術です。

仕様書

開発

[74] W3CHTML WG (の改組以後 HTML Media Extensions Working Group) が開発しています。 仕様書編集者GoogleMicrosoftNetflix の社員です。

EME は DRM ではない (大本営発表)

[71] 開発元の W3C は、 EMEDRM ではない >>36, >>68 と主張しています。 DRM を実現するために使うことはできるが、 DRM そのものではないという(屁)理屈のようです。

[72] W3CDRM を開発・推奨しているのはけしからんとの批判に対して DRM じゃないもんというのは不誠実ではないですかねぇ。 「DRM は必要悪で対応せざるを得ない」という Mozilla のような態度の方がましに思えますが。 W3C としては DRM 推進の会員企業にも DRM 反対の一般利用者にも良い顔をしたくて変な理屈をこねているのでしょうか...

[76] DRM 以外に EME の用途は特にありません。

[77] EME は Open Web にとっての勝利だと主張する人もいます。 Flash のような独自技術を用いずとも Open Web で扱える領域が広がったのだから、 という理論のようです。

[78] あるいは元々 Flash などで存在した DRMEME に移ってきただけで、 新たに DRM が導入されたのではない (から問題はない) と主張する人もいます。


[113] 流石に無理があると気づいたのか、2017年に入ってこの主張は見られなくなり、 かわりに代替技術よりましだ >>111 という点を強調するようになりました。

セキュリティー

[97] DRM に関する法規制で処罰される可能性があるため、 セキュリティーの研究者が萎縮し、 EME が関わる実装上の問題が放置され利用者が危険に晒される危険性があると指摘されています。

[98] EME標準化に当たり、セキュリティー研究を保護するべく業界内で協定を結ぶことが提案されましたが、 W3C はこれを拒否しているようです >>96, >>111

寡占

[135] Request for Position: Web Environment Integrity API · Issue #852 · mozilla/standards-positions · GitHub, https://github.com/mozilla/standards-positions/issues/852

However, I have personal concerns since that while EME in theory is vendor-neutral, in practice there is only three vendors which are widely-recognized: Google Widevine (which is used by Firefox in most platforms plus in Chrome and Android), Microsoft PlayReady (used by Microsoft Edge and Windows plus in some Android devices alongside Widevine), and Apple FairPlay (used in Safari and everything Apple).

利用例

[134] 幅広いユーザーコンテンツを届けることよりも、 特定製品の利用者だけを対象に、セキュリティーリスクに晒しつつ監視しながら限定的に視聴させることを選ぶサイトは、 若干数知られています。

[133] EME を使っているサイト

歴史

[99] Encrypted Media Extensions ( 版) http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html

[1] Perspectives on Encrypted Media Extension Reaching First Public Working Draft - W3C Blog ( ( 版)) http://www.w3.org/QA/2013/05/perspectives_on_encrypted_medi.html

[2] On the Encrypted Media Extensions (EME) document ( (Philippe Le Hegaret 著, 版)) http://lists.w3.org/Archives/Public/public-html-admin/2013Feb/0122.html

[3] MPTF Requirements for Content Protection ( ( 版)) https://dvcs.w3.org/hg/webtv/raw-file/tip/mpreq/cpreq.html

[4] Encrypted Media Extensions ( ( 版)) http://www.w3.org/TR/2013/WD-encrypted-media-20130510/

[5] Encrypted Media Extensions ( ( 版)) http://www.w3.org/TR/2013/WD-encrypted-media-20131022/

[6] The Bridge of Khazad-DRM | Brendan Eich ( ( 版)) https://brendaneich.com/2013/10/the-bridge-of-khazad-drm/

[7] Encrypted Media Extensions ( ( 版)) http://www.w3.org/TR/2014/WD-encrypted-media-20140218/

[8] DRM and the Challenge of Serving Users | The Mozilla Blog ( ( 版)) https://blog.mozilla.org/blog/2014/05/14/drm-and-the-challenge-of-serving-users/

[9] Reconciling Mozilla’s Mission and W3C EME ✩ Mozilla Hacks – the Web developer blog ( ( 版)) https://hacks.mozilla.org/2014/05/reconciling-mozillas-mission-and-w3c-eme/

[10] Encrypted Media Extensions ( ( 版)) http://www.w3.org/TR/2014/WD-encrypted-media-20140828/

[11] Intent to deprecate: Insecure usage of powerful features - Google グループ ( 版) https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/2LXKVWYkOus

We want to start applying the concepts in https://w3c.github.io/webappsec/specs/powerfulfeatures/ to features that have already shipped and which do not meet the (new, not present at the time) requirements.

[12] Chromium Blog: Chrome 42 Beta: Push Notifications, Promoting Add to Home Screen and ES6 Classes ( 版) http://blog.chromium.org/2015/03/chrome-42-beta-push-notifications_12.html

This release includes an updated and unprefixed implementation of Encrypted Media Extensions, which allows media sites to discover and interact with digital rights management systems..

[13] Encrypted Media Extensions ( ( 版)) http://www.w3.org/TR/2015/WD-encrypted-media-20150331/

[14] Encrypted Media Extensions ( 版) http://www.w3.org/TR/2015/WD-encrypted-media-20150928/

[15] Encrypted Media Extensions ( 版) http://www.w3.org/TR/2015/WD-encrypted-media-20151009/

[16] Encrypted Media Extensions ( 版) http://www.w3.org/TR/2015/WD-encrypted-media-20151010/

[17] Encrypted Media Extensions ( 版) http://www.w3.org/TR/2015/WD-encrypted-media-20151027/

[18] Encrypted Media Extensions ( 版) http://www.w3.org/TR/2015/WD-encrypted-media-20151102/

[19] Encrypted Media Extensions ( 版) http://www.w3.org/TR/2015/WD-encrypted-media-20151103/

[20] Encrypted Media Extensions ( 版) http://www.w3.org/TR/2015/WD-encrypted-media-20151105/

[21] Encrypted Media Extensions ( 版) http://www.w3.org/TR/2015/WD-encrypted-media-20151110/

[22] Encrypted Media Extensions ( 版) http://www.w3.org/TR/2015/WD-encrypted-media-20151116/

[23] Encrypted Media Extensions ( 版) http://www.w3.org/TR/2015/WD-encrypted-media-20151120/

[24] Encrypted Media Extensions ( 版) http://www.w3.org/TR/2015/WD-encrypted-media-20151130/

[25] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160122/

[26] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160202/

[27] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160204/

[28] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160208/

[29] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160209/

[30] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160216/

[31] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160218/

[32] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160225/

[33] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160227/

[34] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160325/

[35] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160328/

[36] Information about W3C and Encrypted Media Extensions (EME) - March 2016 ( 版) https://www.w3.org/2016/03/EME-factsheet.html

[37] harryhalpin pe Twitter: "I have tonight announced I will resign from #w3c if the W3C decides to recommend EME. DRM is not part of the web we want. @Joi @EFF @fsf" ( 版) https://twitter.com/harryhalpin/status/711791278640517120

[38] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160329/

[39] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160330/

[40] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160404/

[41] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160412/

[42] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160414/

[43] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160416/

[44] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160421/

[45] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160426/

[46] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160428/

[47] Encrypted Media Extensions ( 版) https://www.w3.org/TR/2016/WD-encrypted-media-20160429/

[48] WebM Stream Format ( ()) https://www.w3.org/TR/2016/NOTE-eme-stream-webm-20160510/

[49] ISO Common Encryption ('cenc') Protection Scheme for ISO Base Media File Format Stream Format ( ()) https://www.w3.org/TR/2016/NOTE-eme-stream-mp4-20160510/

[50] Encrypted Media Extensions Stream Format Registry ( ()) https://www.w3.org/TR/2016/NOTE-eme-stream-registry-20160510/

[51] "cenc" Initialization Data Format ( ()) https://www.w3.org/TR/2016/NOTE-eme-initdata-cenc-20160510/

[52] "webm" Initialization Data Format ( ()) https://www.w3.org/TR/2016/NOTE-eme-initdata-webm-20160510/

[53] "keyids" Initialization Data Format ( ()) https://www.w3.org/TR/2016/NOTE-eme-initdata-keyids-20160510/

[54] Encrypted Media Extensions Initialization Data Format Registry ( ()) https://www.w3.org/TR/2016/NOTE-eme-initdata-registry-20160510/

[55] Encrypted Media Extensions ( ()) https://www.w3.org/TR/2016/WD-encrypted-media-20160514/

[56] 20944 – EME should do more to encourage/ensure CDM-level interop ( ()) https://www.w3.org/Bugs/Public/show_bug.cgi?id=20944

[57] Encrypted Media Extensions ( ()) https://www.w3.org/TR/2016/WD-encrypted-media-20160517/

[58] Encrypted Media Extensions ( ()) https://www.w3.org/TR/2016/WD-encrypted-media-20160518/

[59] Encrypted Media Extensions ( ()) https://www.w3.org/TR/2016/WD-encrypted-media-20160520/

[60] Encrypted Media Extensions ( ()) https://www.w3.org/TR/2016/WD-encrypted-media-20160527/

[61] Encrypted Media Extensions ( ()) https://www.w3.org/TR/2016/WD-encrypted-media-20160531/

[62] Encrypted Media Extensions ( ()) https://www.w3.org/TR/2016/WD-encrypted-media-20160601/

[63] Encrypted Media Extensions ( ()) https://www.w3.org/TR/2016/WD-encrypted-media-20160602/

[64] Encrypted Media Extensions ( ()) https://www.w3.org/TR/2016/WD-encrypted-media-20160603/

[65] Encrypted Media Extensions ( ()) https://www.w3.org/TR/2016/WD-encrypted-media-20160609/

[66] Encrypted Media Extensions ( ()) https://www.w3.org/TR/2016/WD-encrypted-media-20160610/

[67] API Deprecations and Removals in Chrome 50 | Web Updates - Google Developers ( ()) https://developers.google.com/web/updates/2016/03/chrome-50-deprecations?utm_source=feed&utm_medium=feed&utm_campaign=updates_feed

Prefixed encrypted media extensions have been removed in favor of a spec-based, unprefixed replacement.

[68] Perspectives on security research, consensus and W3C Process | W3C Blog () https://www.w3.org/blog/2016/06/perspectives-on-security-research-consensus-and-w3c-process/

[69] Translation from PR-speak to English of selected portions of “Perspectives on security research, consensus and W3C Process” — Anne’s Blog () https://annevankesteren.nl/2016/06/translation-from-w3c-drm-pr-speak-to-english

[75] Issue 241496 - chromium - Implement unprefixed Encrypted Media Extensions - Monorail () https://bugs.chromium.org/p/chromium/issues/detail?id=241496

[79] Encrypted Media Extensions () https://www.w3.org/TR/2016/CR-encrypted-media-20160705/

[80] Encrypted Media Extensions Initialization Data Format Registry () https://www.w3.org/TR/2016/NOTE-eme-initdata-registry-20160831/

[81] "cenc" Initialization Data Format () https://www.w3.org/TR/2016/NOTE-eme-initdata-cenc-20160831/

[82] "webm" Initialization Data Format () https://www.w3.org/TR/2016/NOTE-eme-initdata-webm-20160831/

[83] "keyids" Initialization Data Format () https://www.w3.org/TR/2016/NOTE-eme-initdata-keyids-20160831/

[84] Encrypted Media Extensions Stream Format Registry () https://www.w3.org/TR/2016/NOTE-eme-stream-registry-20160831/

[85] ISO Common Encryption ('cenc') Protection Scheme for ISO Base Media File Format Stream Format () https://www.w3.org/TR/2016/NOTE-eme-stream-mp4-20160831/

[86] WebM Stream Format () https://www.w3.org/TR/2016/NOTE-eme-stream-webm-20160831/

[87] Encrypted Media Extensions Initialization Data Format Registry () https://www.w3.org/TR/2016/NOTE-eme-initdata-registry-20160915/

[88] "cenc" Initialization Data Format () https://www.w3.org/TR/2016/NOTE-eme-initdata-cenc-20160915/

[89] "keyids" Initialization Data Format () https://www.w3.org/TR/2016/NOTE-eme-initdata-keyids-20160915/

[90] "webm" Initialization Data Format () https://www.w3.org/TR/2016/NOTE-eme-initdata-webm-20160915/

[91] Encrypted Media Extensions Stream Format Registry () https://www.w3.org/TR/2016/NOTE-eme-stream-registry-20160915/

[92] ISO Common Encryption ('cenc') Protection Scheme for ISO Base Media File Format Stream Format () https://www.w3.org/TR/2016/NOTE-eme-stream-mp4-20160915/

[93] WebM Stream Format () https://www.w3.org/TR/2016/NOTE-eme-stream-webm-20160915/

[94] Fwd: DRM protest timed with TPAC 2016 (Daniel Veditz著, ) https://lists.w3.org/Archives/Public/public-webappsec/2016Sep/0056.html

[95] ANSOL, AEL to lead demonstration against digital handcuffs at World Wide Web Consortium meeting | Associação Nacional para o Software Livre () https://ansol.org/DRM-no-HTML-EN

LISBON, Portugal -- Thursday, September 8th, 2016 -- ANSOL (Associação Nacional para o Software Livre) and AEL (Associação Ensino Livre) will demonstrate against the incorporation of Digital Restrictions Management (DRM) into HTML, the technical standard that defines the Web. ANSOL and AEL invite anyone interested to join them on September 21st at 18:00 at Centro de Congressos de Lisboa, during a meeting of the World Wide Web Consortium (W3C), which sets Web standards like HTML and CSS. W3C members such as Microsoft, Google, and Netflix have been pushing forward the incorporation of Encrypted Media Extensions (EME) into HTML. This would make it no longer an open standard, according to national law. EME in HTML would make it fail three of five criteria in the portuguese law for open standards (36/2011) and would unjustifiably sacrifice freedom on the Web.

[96] The WHATWG Blog — DRM and Web security () https://blog.whatwg.org/drm-and-web-security

[100] On EME in HTML5 | W3C Blog () https://www.w3.org/blog/2017/02/on-eme-in-html5/

[101] 流石に EME は DRM じゃない (大本営発表) は馬鹿っぽいから諦めたのかな。

[102] W3C Security Disclosures Best Practices is a W3C Team Submission | W3C News () https://www.w3.org/blog/news/archives/6179?pk_campaign=feed&pk_kwd=w3c-security-disclosures-best-practices-is-a-w3c-team-submission

[103] Encrypted Media Extensions () https://www.w3.org/TR/2017/PR-encrypted-media-20170316/

[104] Formal objections to Encrypted Media Extensions (Paul Cotton著, ) https://lists.w3.org/Archives/Public/public-html-media/2016Sep/0003.html

[105] Encrypted Media Extensions is a W3C Proposed Recommendation (Philippe Le Hégaret著, ) https://lists.w3.org/Archives/Public/public-html-media/2017Mar/0016.html

[106] EME and accessibility () https://www.w3.org/2017/03/eme-accessibility.html

[107] Deprecations and Removals in Chrome 58  |  Web  |  Google Developers ( ()) https://developers.google.com/web/updates/2017/03/chrome-58-deprecations

[108] () https://en.unesco.org/sites/default/files/eme_letter_frank_la_rue.pdf

[109] Be careful about proposed technical change to the Web, says UNESCO’s La Rue () http://en.unesco.org/news/be-careful-about-proposed-technical-change-web-says-unesco-s-rue

[110] W3C responds to UNESCO concerns about Encrypted Media Extensions | W3C News () https://www.w3.org/blog/news/archives/6225?pk_campaign=feed&pk_kwd=w3c-responds-to-unesco-concerns-about-encrypted-media-extensions

[111] EME and accessibility () https://www.w3.org/2017/03/eme-accessibility.html

[112] W3C responds to UNESCO concerns about Encrypted Media Extensions | W3C News () https://www.w3.org/blog/news/archives/6225?pk_campaign=feed&pk_kwd=w3c-responds-to-unesco-concerns-about-encrypted-media-extensions

EFF has, as a member of the Consortium, initiated a move to get the members of the working group developing EME to agree to a covenant that they would not sue under the DMCA, but the proposal was rejected by the Members.

[114] TAG comments on EME (Mark Watson著, ) https://lists.w3.org/Archives/Public/www-tag/2017Apr/0004.html

[115] Disposition of Comments for Encrypted Media Extensions and Director's decision (Philippe Le Hégaret著, ) https://lists.w3.org/Archives/Public/public-html-media/2017Jul/0000.html

[116] Encrypted Media Extensions () https://www.w3.org/2017/07/eme-rec-draft.html

[117] Backgrounder on Encrypted Media Extensions (EME) () https://www.w3.org/2017/07/EME-backgrounder.html

[118] Encrypted Media Extensions () https://www.w3.org/2017/07/eme-diff.html

[119] >>116

Together with MSE, EME is just one piece of W3C’s larger vision for media tuning which includes HTML5 as well as TTML (for which W3C won an Emmy Award in 2016) as well as other specifications. The Open Web Platform, of which HTML5 is a cornerstone, also includes CSS, DOM, SVG and Web APIs.

... とすごく不自然に挟み込まれた TTML の宣伝。 TTMLIE が一部のみ実装しているが、 他の Webブラウザー事業者の支持を得られていない。しかし Web 以外の業界では使われていて、 W3C で現在も開発が進められている (周知の通り、 W3C会員企業Web に関係ない会社が多い)。 聞くところによるとからくりは単純で、 EMETTML も推進しているのはハリウッドW3CEmmy Award を受賞したのも自作自演みたいなもののわけなのに、 つい嬉しくて書いちゃったのか。

[120] Disposition of Comments for Encrypted Media Extensions and Director's decision (Philippe Le Hégaret著, ) https://lists.w3.org/Archives/Public/public-html-media/2017Jul/0000.html

[121] Tim Berners-Lee approves Web DRM, but W3C member organizations have two weeks to appeal | Defective by Design () https://defectivebydesign.org/blog/tim_bernerslee_approves_web_drm_w3c_member_organizations_have_two_weeks_appeal

[122] Notice to the W3C of EFF's appeal of the Director's decision on EME | Electronic Frontier Foundation () https://www.eff.org/deeplinks/2017/07/notice-w3c-effs-appeal-directors-decision-eme

[123] Update on HTML5 Video for Netflix – Netflix TechBlog – Medium () https://medium.com/netflix-techblog/update-on-html5-video-for-netflix-fbb57e7d7ca0

[124] W3C EME is not DRM (nor other fear-mongering TLAs) | Adrian Roselli () http://adrianroselli.com/2014/01/w3c-eme-is-not-drm-nor-other-fear.html

Note: I am a participant in the W3C HTML Working Group (as an invited expert).

[125] DRM in HTML5 is a victory for the open Web, not a defeat | Ars Technica () https://arstechnica.com/information-technology/2017/03/drm-in-html5-is-a-victory-for-the-open-web-not-a-defeat/

[126] Encrypted Media Extensions (EME) is a W3C Recommendation | W3C News () https://www.w3.org/blog/news/archives/6521

[127] Encrypted Media Extensions () https://www.w3.org/TR/2017/REC-encrypted-media-20170918/

[128] W3C Publishes Encrypted Media Extensions (EME) as a W3C Recommendation () https://www.w3.org/2017/09/pressrelease-eme-recommendation.html.en

[129] W3CがEMEを標準化、EFFはW3C脱退を発表 | スラド IT () https://it.srad.jp/story/17/09/22/0523202/

[130] Audio/Video Updates in Chrome 63/64  |  Web  |  Google Developers () https://developers.google.com/web/updates/2017/12/chrome-63-64-media-updates

[131] Audio/Video Updates in Chrome 69  |  Web  |  Google Developers () https://developers.google.com/web/updates/2018/08/chrome-69-media-updates

[132] Safari 12.1 Release Notes | Apple Developer Documentation () https://developer.apple.com/documentation/safari_release_notes/safari_12_1_release_notes

Enabled cross-browser Encrypted Media Extensions (EME) by adding APIs without the webkit prefix.