W3C home > Mailing lists > Public > public-html-media@w3.org > April 2015

Re: Updated eme-generic-protocol with JSON version

From: Joe Steele <steele@adobe.com>
Date: Wed, 29 Apr 2015 20:32:06 +0000
To: "watsonm@netflix.com" <watsonm@netflix.com>
CC: "<public-html-media@w3.org>" <public-html-media@w3.org>
Message-ID: <6DA8D24E-7CD2-4B98-81B5-0A5A6374D4FB@adobe.com>
I am not sure about the specifics, but I agree with the intent. We should have a version of this implementable using clearkey. At a minimum that would mean that decryptionKeyIdentifier would be optional, since clearkey would not use it.

I have never used JWE, JWS or JWK (I prefer ASN.1/DER) so if you have changes to propose for the structure defined that would help. I am reading up on those spec in my spare time. I did spec the message signing to use JWS as best I could.


> On Apr 29, 2015, at 12:39 PM, watsonm@netflix.com wrote:
> Hi Joe,
> Haven't looked at your proposal yet, but it occurred to me that this should just be the clearkey messages appropriately wrapped with JWE and JWS and using JWK for key wrapping. Those can all be implemented with WebCrypto, so then the new protocol could be prototyped in JS on top of clearkey. Adding the features we need to clearkey would help with interoperability.
> ...Mark
> Sent from my iPhone
> On Apr 29, 2015, at 12:14 PM, Joe Steele <steele@adobe.com <mailto:steele@adobe.com>> wrote:
>> I added a JSON version of the protocol to the EME Generic Protocol proposed at the F2F.
>> https://github.com/steelejoe/eme-generic-protocol <https://github.com/steelejoe/eme-generic-protocol>
>> Comments are welcome.
>> Joe

Received on Wednesday, 29 April 2015 20:32:34 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 29 April 2015 20:32:35 UTC