- From: <bugzilla@jessica.w3.org>
- Date: Fri, 04 Apr 2014 14:00:19 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25200 --- Comment #5 from Joe Steele <steele@adobe.com> --- (In reply to Shinya Maruyama from comment #4) > Re: #2 > I suppose your proposal (bug 25218) is conceptually similar to mine except > that keyId is used to identify key(s)/license(s) whereas initData is used > for mine. > I do not have and could not imagine any usecases to remove/load/query key(s) > or license(s) by keyId because initData including pssh which can contain all > the KIDs in conformance with cenc second edition is enough to identify > necessary key(s). Meaning even when multiple keys/licenses are associated > with a movie (e.g. key per track), it's sufficient to treat a bunch of them > all together. > If you have concrete usecases where keyId-granular handling is useful, it > would be very helpful to understand the advantage of your proposal and get > convinced. However, even if we have a valid usecase for using keyId, I > prefer to keep such feature as optional; e.g. > - removeKey(optional DOMString keyID); > - if keyID is omitted, all the key(s) associated with initData is removed > Because it burdens application to extract keyID from initData(pssh), MPD or > directly media files always even though initData is good enough for the > key(s) identification. I am fine with this being optional. I am also fine with the keyID being an optional parameter of the other remove() call to for a better naming fit. I believe you are correct that all keyIDs referenced in the initData could be released during a release() call. However the point I have raised elsewhere (including this thread -- http://lists.w3.org/Archives/Public/public-html-media/2014Apr/0019.html) is that the key response from the server may contain keys which are not directly referenced by the initData. One example of this is the domain key. So we need the granularity for two reasons -- a) I don't want to release any domain keys as a side effect of releasing the session b) I want to be able to release domain keys directly as part of leaving the domain -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 4 April 2014 14:00:20 UTC