[Bug 27124] Add "individualizationrequest" to the MediaKeyMessageType enum

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

--- Comment #10 from Henri Sivonen <hsivonen@hsivonen.fi> ---
(In reply to David Dorwin from comment #2)
> (In reply to Henri Sivonen from comment #0)
> > The spec currently says:
> > "Application- and origin-independent messages related to per-client
> > initialization (or reinitialization) that are sent to a fixed
> > non-application-dependent URL MUST be handled by the user agent and MUST NOT
> > be passed to the application via the APIs."
> > 
> > I think this is inappropriate. As far as I am aware, no rationale has been
> > given for the above-quoted design restriction. As described in
> > http://lists.w3.org/Archives/Public/public-html-media/2014Oct/0006.html ,
> > it's a totally reasonable design that individualization (is there
> > "initialization" of another kind?) requests are made as EME messages and
> > either the JS app knows how to route these to a different server than the
> > license requests or the license server knows how to proxy these to an
> > individualization server.
> 
> Individualization is already explicitly allowed to go through the EME APIs
> by the next paragraph in the spec,

Oops. I had missed that. Sorry.

> but it must be per-origin
> individualization rather than user agent- or system-wide individualization.
> 
> The rationale for not sending non-origini-specific individualization was
> mentioned at the end of [1]:
>   "privacy with respect to whether the device has previously been
> initialized."

As noted on public-html-media, unless origin-independent individualization
happens eagerly ahead of time, the application can deduce the lack of previous
individualization from the latency of the first operation requiring
individualization.

Since PlayReady pricing currently disincents eager ahead-of-time
individualization, I bet there are people who'd be unhappy about the spec
requiring eager ahead-of-time individualization when individualization isn't
origin-dependent...

> I acknowledged this in [1] and "per-origin initialization" via the EME APIs
> is currently explicitly allowed by the spec.

Since it's already explictly allowed, surely the spec should have an enum entry
to go along with it, too.

(Other concerns not quoted here already replied to on public-html-media:
http://lists.w3.org/Archives/Public/public-html-media/2014Oct/0078.html )

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

Received on Friday, 24 October 2014 09:13:54 UTC