W3C home > Mailing lists > Public > public-html-media@w3.org > June 2017

[encrypted-media] API to add wasm packaged CDM

From: Alexandre Morgaut via GitHub <sysbot+gh@w3.org>
Date: Wed, 07 Jun 2017 13:39:23 +0000
To: public-html-media@w3.org
Message-ID: <issues.opened-234212606-1496842761-sysbot+gh@w3.org>
AMorgaut has just created a new issue for https://github.com/w3c/encrypted-media:

== API to add wasm packaged CDM ==
As of today, serious OTT video providers need either:

* to have back-ends providing different decryption keys for at least one supported Content Decryption Module (CDM) *per browser* (meaning they usually have to support at least Widewine+Playready+Fairplay) 
* to deliver an external player plugin/app using a specific drm technology (Cisco, Verimatrix, Nagra, ...)

It happens that sometimes, such plugin/external app decrypt their video in an HTML5 canvas and either kind of reinvent the wheel by polyfilling the HTML5 video element API or providing a vendor specific API.

With Web Assembly, I'm kind of seing a path to make them provide compiled cross-platform decryption modules. 

They could try to port these whole player app/plugin via EMScripten, potentially via [EGL Support in Emscripten](http://kripken.github.io/emscripten-site/docs/porting/multimedia_and_graphics/EGL-Support-in-Emscripten.html) or something similar, and some will probably do it in the end.

Wouldn't it be way more efficient if we could just have an API to register vendor provided wasm Content Decryption Modules usable directly via the native HTML5 player?

Please view or discuss this issue at https://github.com/w3c/encrypted-media/issues/409 using your GitHub account
Received on Wednesday, 7 June 2017 13:39:29 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 June 2017 13:39:30 UTC