- From: <bugzilla@jessica.w3.org>
- Date: Tue, 18 Feb 2014 16:14:50 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24025 --- Comment #9 from Mark Watson <watsonm@netflix.com> --- My use-case for this is to provide a server certificate to the CDM. A given CDM may be used with multiple servers, for example servers maintained by different service providers. In general, such servers will be running under license agreements from the CDM provider and can be provided with certificates signed by the CDM provider. This enables the CDM to authenticate servers i.e. determine that they are indeed approved by the CDM provider though the receipt of a server certificate. Additionally, a server certificate can be used for the CDM to encrypt data sent to that server (in the keymessages). Such encryption may be useful to ensuring that the encrypted keymessage does not contain anything which could be used as a permanant user identifier by a site which does not have its own server certificate. Such a server certificate will likely not change frequently and so may be cached by the site's client-side code and provided to the CDM when the MediaKeys is constructed. This approach avoids the provision of the server certificate requiring a round-trip to the server. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 18 February 2014 16:14:52 UTC