DRM: ECCP with dashif:Authzurl and single key

[dsilhavy]

A short description of the use case for the new test content.

This test content is supposed to demonstrate the Enhanced Clearkey Protection (ECCP) mechanism. In this case we are using a single key for both audio and video AdaptationSets and the license request requires an auth token.

Test content requirements

General description and requirements

• A single period MPD
• One video and one audio AdaptationSets.
• The content shall be encrypted with Clearkey and the cbcs encryption scheme.
• Both AdaptationSets use the same cenc:default_KID and consequently share the same key
• Both AdaptationSets define dashif:Laurl
• Both AdaptationSets define dashif:Authzurl
• The server component linked in dashif:Authzurl shall return an auth token to be added as a header to the license request.
• The server component linked in dashif:Laurl shall return the valid key. As an example:
  • Request: {"kids":["nrQFDeRLSAKTLifXUIPiZg"],"type":"temporary"}
  • Response: {"keys":[{"kty":"oct","k":"FmY0xnWCPCNaSpRG-tUuTQ","kid":"nrQFDeRLSAKTLifXUIPiZg"}],"type":"temporary"}
• If no valid auth token is provided as part of the license request the license server shall return an error

DASH-IF documents and links

• DASH-IF Interoperability Points; Part 6: Content Protection
• Clear key license format: https://www.w3.org/TR/encrypted-media/#clear-key-license-format

[haudiobe]

Requirements:

• same as DRM: ECCP with dashif:Laurl and single key #9
• in addition an auth token is needed

@rbouqueau please check if you understand the details.