W3C home > Mailing lists > Public > public-html-media@w3.org > June 2014

Re: Bug 25269

From: David Dorwin <ddorwin@google.com>
Date: Wed, 4 Jun 2014 10:47:34 -0700
Message-ID: <CAHD2rsjQg9J3qt_PB+OMa__+7x5pJTEAi1WnCwrcZ2xU3_nzJw@mail.gmail.com>
To: Joe Steele <steele@adobe.com>
Cc: "<public-html-media@w3.org>" <public-html-media@w3.org>
Yes, it is just an array of key IDs.

There are a few options to identify the title:

   - The key ID(s) could include the title ID in them, allowing it to be
   easily extracted on the server. (This forces unique key IDs.)
   - The server can look the title up based on the key ID(s). (This assumes
   they are unique.)
   - The application knows the title and can include this in its request.


Why do you say KID isn't generally unique across streams? That should
probably be a best practice for content providers.

David


On Tue, Jun 3, 2014 at 10:42 AM, Joe Steele <steele@adobe.com> wrote:

> https://www.w3.org/Bugs/Public/show_bug.cgi?id=25269
>
> This bug was closed on Saturday. Rather than just re-open it — maybe you
> can give me some clarification.
>
> Your proposal only includes the KIDs in the data that is sent into the CDM
> — correct?
>
> Given that KID is not generally unique across streams, how are you
> planning to support this? I would expect implementations to require a title
> identifier to pass to the server in order to identify the title that the
> KID is associated with. It sounds like you are proposing that the
> application which has this information should send it to the server in some
> out of band communication.
>
> Joe
>
Received on Wednesday, 4 June 2014 17:48:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:33:03 UTC