- From: <bugzilla@jessica.w3.org>
- Date: Wed, 03 Dec 2014 16:21:33 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27055 --- Comment #19 from Sergey Konstantinov <twirl-team@yandex.ru> --- (In reply to Mark Watson from comment #18) > The CDM has no control or visibility of caching or storage of encrypted > media performed by the UA or application. The CDM decrypts, decodes and > possibly renders the media at playback time. Yes, it is. But UA and/or webapp may cache encrypted frames, and they should be able to know if CDM rejects those frames. > > > * terms for replaying content; > > * terms for using content offline; > > The CDM likely does not generally know whether the device is online or > offline (the CDM may not access the network directly for playback-specific > operations). So, the primary issue is whether the license is still valid at > the time of playback. > > We already expose an "expiration" time to the application, but there could > be other properties of the license which make it not so useful for offline > playback. Another obvious case is a possibility to purge cache via license response. I'd prefer this sort of behavior to be somehow formalized. > > > * operations requiring internet connection. > > The specification is clear that direct network access by the CDM is > restricted to origin-independent initialization (e.g. individualization). > Okay, let me say it another way: we need to understand cases when CDM may reject to render content. One case is license expiration, but there are others. For example, in #13 Henry mentioned that seeking backwards needs new license to be somehow obtained. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 3 December 2014 16:21:39 UTC