- From: <bugzilla@jessica.w3.org>
- Date: Wed, 30 Apr 2014 21:19:44 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25217 --- Comment #6 from Joe Steele <steele@adobe.com> --- (In reply to Joe Steele from comment #5) > (In reply to Mark Watson from comment #4) > > (In reply to Joe Steele from comment #3) > > > (In reply to Mark Watson from comment #2) > > > > Joe, can you explain what a "domain" is, in terms that are independent of > > > > any particular DRM system ? > > > > > > In DRM-generic terms, a domain (or "license domain") is a group of players > > > for which a single content license can be issued. A domain key is a key that > > > is used to encrypt content keys for delivery to players in the same domain. > > > > So, the idea would be that a player from one origin gets a domain key and > > (possibly) licenses for the domain and then this information can be used by > > players from other origins that are part of the same domain ? > > No. > > > > > How would this fit into the 'same origin' web security model ? What would be > > the mechanism for origins to prove that they are allowed access to keys / > > licenses associated with a specific domain ? > > Per our resolution to bug 17202, I am not expecting keys to be shared across > origins. On re-reading - I think I see the confusion. There are two different meanings to "sharing" in this case. A content license issued to a domain is implicitly "shared" between players by virtue of being in the same domain. However I do not mean to imply that the copy of that content license downloaded to a particular player is shared with other players. The players in the domain may all have their own copies of the same license, and in the case of EME they would. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 30 April 2014 21:19:45 UTC