[Bug 26401] Key message destinationURL usage is not reflected in examples

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26401

--- Comment #8 from Joe Steele <steele@adobe.com> ---
(In reply to David Dorwin from comment #7)
> (In reply to Joe Steele from comment #6)
> > The CDM would provide the URL and it would base it on either the initData or
> > other information in the CDM itself, either hard-coded or provided at
> > install time. 
> 
> It can't be based on the initData (see bug 25920). If it's hard-coded, that
> wouldn't be per-origin or really need to go through the EME APIs.

I dismissed the argument in bug 25920 when it was made. The initData can and
does contain URL information for some DRM systems. Also, having the URL be
hard-coded does not dismiss the per-origin requirement. I did not say that the
URL was per-origin, merely that the initialization was. In our case this
resulted directly from the requirements in the security section for restricting
the amount of shareable information. 

> 
> > The licenseURL and the initialization URL may have no relationship. For
> > example in the Adobe Access case, the initialization URL is a central Adobe
> > server and the license servers may be Adobe servers or may be customer
> > on-premise servers.
> 
> How can it be a central server or a customer server? How would the CDM know
> which to pick?

If the URL is coming from the initData, the customer who packaged the content
was able to define the URL. The license server that the URL points to may be
run by the CDM provider or may be run by the content provider. I can also
imagine there being policy in the initData to allow the CDM to choose from a
list of URLs provided in the policy, based on the CDM instance (for example CDM
instance 4 of 10 might use a different URL)  for load balancing.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 19 August 2014 14:56:57 UTC