Guidelines

Home / Guidelines

Completed DASH-IF Interoperability Documents

Disclaimer

The documents below are stable and have undergone a community review. However, the DASH-IF welcomes feedback on these published documents, e.g, request for clarifications or bugs. For this purpose, please use the Github bug tracker cited along with the documents.

DASH-IF Interoperability Points and Extensions

Latest Version:

Previous Versions:

DASH-IF Content Protection Information Exchange Format

Latest Version:

  • DASH-IF Implementation Guidelines v2.0: Content Protection Information Exchange Format (CPIX)| (XML)| (Bugtracker)
  • The scope of this document is to define a Content Protection Information Exchange Format (CPIX). The CPIX document contains keys and DRM information used for encrypting and protecting content, and can be used for exchanging this information among entities needing it in many possibly different workflows for preparing, for example DASH content or HLS content. The CPIX document itself can be encrypted, signed and authenticated so that its receivers can be sure that its confidentiality, source and integrity are also protected.
  • The document provides the following extensions to v1.0:
    • The CPIX document structure has been extensively revised in order to make it more generic so that media formats other than those described in DASH-IF IOPs can be accommodated.
    • It no longer mirrors the structure of an MPD file, but rather contains rules to describe the mapping of streams to content keys.
    • It allows for supporting additional DRM signaling schemes by allowing alternative types of DRM signaling elements.
    • Sets of elements can be authenticated by means of XML element signing.

Previous Versions:

Guidelines for Implementation: DASH-IF Interoperability Point for ATSC 3.0

DASH-IF Test cases and Vectors

DASH-IF Interoperability Documents for Community Review

General

Community Review documents are published on the DASH-IF website in order to get feedback from the industry on tools and features that are documented for improved interoperability. For each of the documents, comments may be submitted on the technologies itself, on specific features, etc. These documents are only published temporarily for community review and will be replaced by a full version after the commenting period has closed and the comments have been addressed.

Addition of Dolby Vision to DASH-IF IOP

  • The change request against IOP v4.0 for Community Review is accessible here
  • Community review is open until April 30th, 2017. Addition to IOP is expected by June 2017.
  • Comments may be submitted through the public bugtracker.
  • This Interoperability Point allows for two interlocked video streams, known as the Base and Enhancement layers, where the Base Layer fully conforms to previous non-UHD or UHD DASH-IF Interoperability point, and the addition of a additional video layer produces a UHD output signal, including Wide Color Gamut, and High Dynamic Range signal at the client.

Annotation and Client Model for Content Selection

  • The change request against IOP v4.0 for Community Review is accessible here
  • Community review is open until April 30th, 2017. Addition to IOP is expected by June 2017.
  • Comments may be submitted through the public bugtracker.
  • DASH supports many different aspects to add Annotation for Adaptation Sets. The reason for this is that different use cases have been defined that may be specific for specific ecosystems. However, for consistent interoperability, DASH-IF IOP misses clear guidelines for the content generation as well as for the client implementation to select audio and video tracks at startup and operations. Therefore, a consistent signalling framework is provided.

Addition of Remote Period timing to DASH-IF IOP

  • The change request against IOP v4.0 for Community Review is accessible here
  • Community review is open until April 15th, 2017. Addition to IOP is expected by June 2017.
  • Comments may be submitted through the public bugtracker.
  • Addition of text explaining preservation of timing throughout XLink dereferencing.

Addition of VP9 Video Extensions to DASH-IF IOP

  • The change request against IOP v4.0 for Community Review is accessible here
  • Community review is open until April 15th, 2017. Addition to IOP is expected by June 2017.
  • Comments may be submitted through the public bugtracker.
  • The VP9 video format is widely used for Internet streaming by Web browsers and other free software because of its open development model. It is efficient in terms of data bandwidth utilization at high special resolutions, and supports 10- and 12-bit High Dynamic Range and Wider Color Gamut, thus providing an improved user experience.  It would be advantageous to specify the application of the VP9 codec in ISO Media Format and DASH Segments, and how this codec is signaled in MPD Adaptation Sets.

Robust and Consistent Live Services

  • The change request against IOP v4.0 for Community Review is accessible here
  • Community review was closed as of December 9th, 2016. Addition of  Robust and Consistent Live Services is expected with the next version of IOP.
  • The document provides the following extensions to v4.0.
    • Update robust operation to add some more clarity
    • detailed deployment guidelines for a packager

DASH-IF Implementation Guidelines: Token-based Access Control for DASH (TAC) v1.0

  • The document for 2nd Community Review is accessible here
  • Community review is open until March 31st, 2017. Publication is expected by June 2017.
  • Comments may be submitted through the public github repository
  • The scope of this document is to define a token-based access control mechanism and enabling the signaling of authentication and authorization (AA) protocols for DASH-based video streaming. An access token is a proof that a DASH client or user of the clients have been successfully authenticated and authorized, respectively, in some pre-determined AA Systems to access a particular DASH resource, e.g. DASH segments or MPDs. This document remains agnostic on what AA Systems and protocols are actually used for DASH clients to obtain AA Tokens but it does define the access token format for accessing DASH resources, hence ensuring interoperability between content providers and content delivery networks.

DASH-IF Conformance Software

ISO Publicly Available Specification

White Papers and Background