Thanks to visit codestin.com
Credit goes to github.com

Skip to content
This repository was archived by the owner on Apr 23, 2025. It is now read-only.

Addressing comments by @hsivonen in http://lists.w3.org/Archives/Public/www-tag/2014Feb/0057.html #1

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Addressing comments by @hsivonen in http://lists.w3.org/Archives/Public/www-tag/2014Feb/0057.html #1

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c00d12c
rephrasing characterisation of EME
Feb 22, 2014
11ba5d1
calling DRM DRM
Feb 22, 2014
d16633d
mechanism for getting keys must be open & platform independent too
Feb 22, 2014
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 13 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,19 +84,26 @@ The Technical Architecture Group recommends an architecture for the web platform

## Applying the Principles to EME

The Encrypted Media Extensions defined in [the Encrypted Media Extensions Working Draft](http://www.w3.org/TR/encrypted-media/) aim to provide a common, platform independent interface to enable sharing of encrypted content on the web. The common interface encapsulates a "black box" of encryption technologies and very little has been specified about the way in which these technologies operate.
The Encrypted Media Extensions in [the Encrypted Media Extensions Working Draft](http://www.w3.org/TR/encrypted-media/) "define a common API that may be used to discover, select and interact with [content protection or Digital Rights Management] systems as well as with simpler content encryption systems" as part of the [HTML Working Group's chartered aim of "supporting playback of protected content"](http://www.w3.org/2013/09/html-charter.html).

The approach taken within the EME specification is to provide a common, platform independent interface to support playback of content that has been protected through encryption. But this common interface encapsulates a "black box" (the Digital Rights Management system) and very little has been specified about the way in which the technologies inside this black box operate.

### Platform Independence

We have seen, in the use of the `<object>` tag, that standard interfaces over platform-dependent technologies do not turn the platform-dependent technologies into platform-independent ones. So when considering encrypted media on the web, we have to ensure that the "black box" of encryption technologies is platform independent, as well as the interface that surrounds it.
We have seen, in the use of the `<object>` tag, that standard interfaces over platform-dependent technologies do not turn the platform-dependent technologies into platform-independent ones. So when considering protected content on the web, we have to ensure that the DRM "black box" is platform independent, as well as the interface that surrounds it.

Platform dependence in DRM arises from two main sources:

* using proprietary encryption algorithms
* requiring the use of proprietary methods to access keys

Platform-dependent encryption technologies use private/secret/proprietary algorithms to encrypt and decrypt content. Because these technologies are private/secret/proprietary, a user's ability to use them will depend on their use of a particular platform. A content publisher may come to a deal with the owners of a particular platform to provide that content exclusively through that platform. They would then use the proprietary algorithm to encrypt the content, which could then only be decrypted on the proprietary platform.
When aspects of a DRM system are private/secret/proprietary, a user's ability to use them will depend on their use of a particular platform. A content publisher may come to a deal with the owners of a particular platform to provide that content exclusively through that platform. They would then use the proprietary methods of encrypting the content or providing the keys to decrypt the content, knowing that decryption could only occur on the proprietary platform.

Platform-independent encryption technologies use a combination of public, standard algorithms to perform the de/encryption of content, and private/secret keys that are only known by those who are authorised to access the content.
Platform-independent DRM would have to use a combination of public, standard algorithms to perform the de/encryption of content, and private/secret keys that are only known by those who are authorised to access the content but that can be accessed regardless of platform.

A mechanism for ensuring that encrypted media could be used on the web without undermining the principle of platform independence would be to define a standard set of public, standard, encryption algorithms that can be used, coupled with a standard mechanism for accessing a key to decrypt encrypted media.
A mechanism for ensuring that encrypted media could be used on the web without undermining the principle of platform independence would be to define a standard set of public, open, standard, encryption algorithms that can be used, coupled with a public, open, standard mechanism for accessing a key to decrypt encrypted media.

**The EME specification must ensure platform independence, for example by specifying the use of open standard encryption algorithms.**
**The HTML Working Group must ensure that playback of protected content is supported in a platform independent way.**

### Accessibility

Expand Down