- From: Karl Dubost <karl@la-grange.net>
- Date: Wed, 16 Oct 2013 12:39:16 +0200
- To: "public-restrictedmedia@w3.org List" <public-restrictedmedia@w3.org>
- Message-Id: <95246995-4F39-487E-AC75-D1F75D3C5220@la-grange.net>
This time, more on the technical side, to clearly understand what is EME. > What is EME? > > It was suggested at the Mozilla Summit that there isn’t good information around about what Encrypted Media Extensions (EME) actually is. Since I’m on the HTML working group and have been reading the email threads about EME there, I thought that I could provide an introduction that explains things that may not be apparent from the specification itself. > > TL;DR > > EME is a JavaScript API that is part of a larger system for playing DRMed content in HTML <video>/<audio>. EME doesn’t define the whole system. EME only specifies the JS API that implies some things about the overall system. A DRM component called a Content Decryption Module (CDM) decrypts, likely decodes and perhaps also displays the video. A JavaScript program coordinating the process uses the EME API to pass messages between the CDM and a server that provides decryption keys. EME assumes the existence of one or more CDMs on the client system but it doesn’t define any or even their exact nature (e.g. software vs. hardware). That is, the interesting part is left undefined. — Read more at http://hsivonen.fi/eme/ -- Karl Dubost http://www.la-grange.net/karl/
Received on Wednesday, 16 October 2013 10:39:19 UTC