ISSUE-63: Encrypted Media Extensions (EME) Testing

Encrypted Media Extensions (EME) Testing

State:

CLOSED

Product:

testing

Raised by:

Bin Hu

Opened on:

2013-03-28

Description:

Provide comprehensive test suite for HTML5 Encrypted Media Extensions (EME) specification to enable playback of protected content, and related use cases ranging from simple clear key decryption to high value video.

Specific Areas of Test:

(1) CDM portability: 1 CDM type, 2 browsers, 1 stream

This would be a test of whether two browsers using the same type of CDM can decode the same encrypted stream. For example, if BrowserA and BrowserB both include support for the XYZ CDM, the test would be whether BrowserA and BrowserB can both decode and display the same stream that is meant to be decoded by the XYZ CDM. This could be tested on both clear-key and non clear-key CDMs.

(2) "Common Encryption": 2 CDM types, 2 browsers, 1 stream

This would be a test of whether two browsers using different types of CDM can decode the same encrypted stream. For example, if BrowserA supports XYZ CDM and BrowserB supports UVW CDM and if both XYZ and UVW support the same common encryption format, the test would be whether BrowserA and BrowserB can both decode and display the same stream using two different CDMs. This must be tested on two non clear-key CDMs.

(3) "HTML/CSS transformations": 1 CDM, 1 browser, 1 stream

This would be a test of whether a CDM correctly transforms the video given a variety of HTML and CSS transformations, such as scaling, rotation and occlusion. This could be tested on both clear-key and non clear-key CDMs.

Motivation:

HTML5 EME extends HTMLMediaElement to allow JavaScript to select content protection mechanisms, control license/key exchange, and implement custom license management algorithms.

It supports a wide range of use cases without requiring client-side modifications in each User Agent for each use case. This also enables content providers to develop a single and robust application solution for all devices (TVs / STBs, smart phones, tablets and PCs etc) supporting a range of content decryption and protection technologies.

Supporting EME Testing will accelelate the time-to-market of EME-enabled device, offer the consumers with EME-enabled video services and provide end users with better user experience without dependency on Flash or SilverLight.

Dependencies:
User Agent support is required as the JavaScript library needs to be extended to support EME.

What needs to be standardized:
User Agent needs to be exposed with EME-enabled JavaScript library.

Related Actions Items:

No related actions

Related emails:

1. [testing] minutes - 14 August 2013 (from ddavis@w3.org on 2013-08-14)
2. Re: webtv-ISSUE-63: Encrypted Media Extensions (EME) Testing [testing] (from Mark_Vickers@cable.comcast.com on 2013-04-17)
3. Re: webtv-ISSUE-63: Encrypted Media Extensions (EME) Testing [testing] (from glenn@skynav.com on 2013-04-17)
4. Re: webtv-ISSUE-63: Encrypted Media Extensions (EME) Testing [testing] (from Sheau.Ng@nbcuni.com on 2013-04-10)
5. [testing] minutes - 3 April 2013 (from ashimura@w3.org on 2013-04-04)
6. RE: webtv-ISSUE-63: Encrypted Media Extensions (EME) Testing [testing] (from bh526r@att.com on 2013-04-03)
7. Re: webtv-ISSUE-63: Encrypted Media Extensions (EME) Testing [testing] (from Mark_Vickers@cable.comcast.com on 2013-04-03)
8. Re: webtv-ISSUE-63: Encrypted Media Extensions (EME) Testing [testing] (from giuseppep@opera.com on 2013-04-03)
9. Re: webtv-ISSUE-63: Encrypted Media Extensions (EME) Testing [testing] (from Mark_Vickers@cable.comcast.com on 2013-04-03)
10. webtv-ISSUE-63: Encrypted Media Extensions (EME) Testing [testing] (from sysbot+tracker@w3.org on 2013-03-28)

Related notes:

No additional notes.

Display change log