- From: <bugzilla@jessica.w3.org>
- Date: Mon, 29 Apr 2013 19:17:32 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21869 Bug ID: 21869 Summary: Need clarity on stored keys for CDMs Classification: Unclassified Product: HTML WG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Encrypted Media Extensions Assignee: adrianba@microsoft.com Reporter: steele@adobe.com QA Contact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-media@w3.org We have a few bugs which touch on the subject of retaining keys beyond the life of a session. Primarily bug 17750 "Define the behavior MediaKeySession close() and clearing the keys attribute" but 19788 and 16616 also mention this. We should provide some guidance to EME implementors as to how they can expect to store these keys. For example -- following normal UA guidelines I would expect this data to be per domain and per page URL. But is this based on the domain hosting the player (my preference) or on the domain for the key servers, or is it an entirely independent store? Or is it entirely up to the UA? This is important for maintaining clean separation between players and allowing the user to clear state when they want to. BTW -- I could not find an exact match for this bug although it has commonalities with some existing bugs. If you would prefer to close it as a dup, I can just continue the conversation in the dup bug. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 29 April 2013 19:17:33 UTC