Home / Guidelines

Completed DASH-IF Interoperability Documents


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:

  • Guidelines for Implementation: DASH-IF Interoperability Points V4.1: Robust Live, Seek Preview, Content Annotation, New Media Codesc and other extensions | (Bugtracker)
  • This version adds:
    • Guidelines for Robust Live Services in clause 4.11.
    • Updates to W3C Clear Key usage in clause
    • Addition of last segment number signaling in clause and
    • Addition of Dolby Vision dual layer in clause 10.4 and referenced Annexes
    • Seek Preview and Thumbnail Navigation in clause 3.2.9 and clause 6.2.6
    • Clarification on AudioChannelConfiguration element in clause
    • Annotation and client model for content selection defined in clause 3.9.
    • Remote referencing and use of query parameters for ad insertion in clause and 5.3.5, respectively.
    • Default KID Clarifications in clause
    • Addition of VP9 Video to DASH-IF IOP in clause 11.
    • Client and DRM System Interactions in clause 7 and in particular in clause 7.7.9
    • Miscelaneous editorial updates and bug fixes

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


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 MPD Chaining and Fallback MPD

  • The change request against IOP v4.0 for Community Review is accessible here
  • Community review is open until July 31st, 2017. Addition to IOP is expected by Dece2017.
  • Comments may be submitted through the public bugtracker.
  • This addition adds two main features: (i) MPD chaining enables preroll ad for live streaming, (ii) MPD fallback allows the client to play a fallback presentation if it fails to stream the main content

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