This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16549 - Remove initData parameter from addKey()
Summary: Remove initData parameter from addKey()
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Encrypted Media Extensions (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: David Dorwin
QA Contact: HTML WG Bugzilla archive list
Depends on: 16548 16613 16614
  Show dependency treegraph
Reported: 2012-03-28 00:18 UTC by David Dorwin
Modified: 2012-08-17 06:01 UTC (History)
6 users (show)

See Also:


Description David Dorwin 2012-03-28 00:18:39 UTC
This depends on the proposal in issue 16548 being accepted. If it is not accepted, then initData is required.

From v0.1:
It has been proposed that the initData parameter, which would most likely contain inforamation identifying the key or keys needed, be removed from addKey() because any association can be done within the CDM using sessionId. (However, see Session Correlation <>.) Such a change depends on requiring that generateKeyRequest() always be called before addKey(). Assuming that change is made, removing the parameter simplifies the API but hides all association between a key identifier and key. See this example <> for an illustration of the impact of this change.
Comment 1 David Dorwin 2012-05-25 22:31:13 UTC
We should prioritize resolving this since it affects the basic API.
Comment 2 David Dorwin 2012-06-12 00:23:59 UTC
I think this could be addressed by 16613, and if not, we should address it in the context of 16614.
Comment 3 Yang Sun 2012-06-12 09:03:38 UTC
Mostly agree on this.
I have review the spec and below text.
It seems generateKeyRequest will be called each time the specified page is loaded, so addkey can get key related seesionId from event cast by generateKeyRequest.

And reduce parameter in addKey is ok, due to sessionId can cover it.

And I am not sure what other usage of initData will be used in addKey or other event capture function?

One question, if we do not call generateKeyRequest each time loading, how we can get key before addKey is called? The key will be stored in CDM?

One more question, how long is the key life time? until page reloaded? or persistent before you close the browser?
Comment 4 David Dorwin 2012-08-17 06:01:40 UTC
Addressed by the object-oriented API (bug 16613). addKey() now only has a |key| parameter. We need to figure out how to associate key IDs and keys for Clear Key, which does not currently have a "license format" (bug 17682), but can close this bug.