Re: [NEW] Media Task Force Wiki

Yes, #2 supports that model. It's also possible that the license will be
persisted and used for immediate playback. For example, the user might
start watching while the movie downloads in the background.

Can you provide more details on an implementation for which this would be a
problem? Wouldn't expensive cryptographic operations have already been
initiated to generate the license request?

David


On Wed, May 21, 2014 at 11:34 PM, Maruyama, Shinya <
Shinya.Maruyama@jp.sony.com> wrote:

>  Additional questions.
>
>
>
> The Application models #2 seems like the ‘to-go’ use case where license is
> acquired just to persist for later use.
>
> In the persisting step, it would be better to suppress making keys
> available because it requires cryptographic operations but it’s not
> possible because the algorithm of createSession does not specify that way
> (persisting license(s) always happens in conjunction with deriving keys).
>
>
>
> I’m not sure if I understand the intent of the application model #2 but I
> wonder if some implementer might want to support the case above.
>
>
>
> Thanks,
>
> Shinya
>
>
>
> *From:* Maruyama, Shinya [mailto:Shinya.Maruyama@jp.sony.com]
> *Sent:* Monday, May 19, 2014 2:55 PM
> *To:* David Dorwin; Joe Steele
> *Cc:* <public-html-media@w3.org>
> *Subject:* RE: [NEW] Media Task Force Wiki
>
>
>
> Thank you for adding use cases and application models.
>
> They looks like great step in order to proceed to discussions for several
> open/pending issues.
>
>
>
> Looking through the use cases, I just have a question whether we should
> have a separate use case of removing persisted license.
>
> Removal of the license is mentioned in Application Models #2 but it is the
> use case where the license is removed with/after viewing the content.
>
>
>
> Assuming the case of removing the persisted license without viewing, it
> might be better to support just loading license as separate step from
> making keys available, which requires cryptographic operations.
>
>
>
> If we support this use case, a possible option is, for example, to add a
> separate method ‘run()’ to run the session;
>
> - loadSession() just load persisted licenses
>
> - run() make keys available to content decryption
>
> - remove() can be called before run()
>
>
>
> Thanks,
>
> Shinya
>
>
>
> *From:* David Dorwin [mailto:ddorwin@google.com <ddorwin@google.com>]
> *Sent:* Wednesday, May 14, 2014 11:32 AM
> *To:* Joe Steele
> *Cc:* <public-html-media@w3.org>
> *Subject:* Re: [NEW] Media Task Force Wiki
>
>
>
> As I said I would do in the telecon this morning, I documented the primary
> application models on the wiki. Since the Media_Task_Force wiki may
> eventually have other EME and non-EME information, I created a separate
> page for the EME use cases:
> https://www.w3.org/wiki/HTML/Media_Task_Force/EME_Use_Cases. I left the
> existing use cases as is, but they should probably be moved to the new
> page. (I believe the first two are covered by the first application model.)
>
>
>
> David
>
>
>
> On Tue, Apr 22, 2014 at 8:10 AM, Joe Steele <steele@adobe.com> wrote:
>
> We setup a new wiki page to capture use cases, external references and
> other useful information: https://www.w3.org/wiki/HTML/Media_Task_Force
>
>
>
> David pointed out on the call this morning this may have been
> automatically archived by folks as it was part of the last minutes email.
>
>
>
> The goal is to list use cases for EME and categorize them. This way we can
> have a clearer idea of what is supported and what is NOT supported. I have
> added a few use cases up there already you may recognize.
>
>
>
> Please take a few minutes to review and contribute.
>
>
>
> Joe Steele
>
>
>