Introduction
Beyond the DASH-IF Interoperability Guidelines, DASH-IF also publishes specifications and reports. Those are collected in this clause.
- Completed Specifications and Guidelines: The documents below are stable and have undergone a community review.
- Documents for community review: These documents are technically solid, but public is asked for comments in order to improve details.
- Position and White Papers: These documents provide background and initial studies
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 Guidelines
For DASH-IF Interoperability Guidelines, refer to
DASH-IF Content Protection Information Exchange Format
Scope
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.
Latest Version
DASH-IF Implementation Guidelines v2.3: Content Protection Information Exchange Format (CPIX) | (XSD) | (PDF) | (Bugtracker) | (Test vectors) | (ETSI)
Changes from 2.2 are
- Addition of the
commonEncryptionSchemeelement with the CENC protection scheme value - Addition of the
versionelement - Addition of a section on using the same content key with different encryption schemes
- Clarification on the
explicitIVelement encoding - Typos corrections
Previous Versions
- DASH-IF Implementation Guidelines v2.2: Content Protection Information Exchange Format (CPIX) | (PDF) | (XSD) | (Bugtracker) | (Test vectors)
- DASH-IF Implementation Guidelines v2.1: Content Protection Information Exchange Format (CPIX) | (PDF) | (XSD) | (Bugtracker)
- DASH-IF Implementation Guidelines v2.0: Content Protection Information Exchange Format (CPIX)| (XML)| (Bugtracker)
- DASH-IF Implementation Guidelines v1.0: Content Protection Information Exchange Format (CPIX)| (XML)| (Bugtracker)
Guidelines for Implementation: DASH-IF Interoperability Point for ATSC 3.0
Scope
The scope of this document is to provide a DASH interoperability point that is based on DASH-IF-IOPs and provides extensions to address use cases and requirements of ATSC 3.0.
Comments and bugs may be submitted through the public github repository.
Latest Version
Version 1.1: Guidelines for Implementation: DASH-IF Interoperability Point for ATSC 3.0 (pdf | diff to v1.0)
This updated version adds the following aspects:
- Update of references to refer to the latest correct versions
- Clarification on track selection in clause 3.3 and addition of a new clause 2.7.5
- Addition of a placeholder for a non-real time profile in clause 1.3
- Updates to the ROUTE protocol constraints when used with $TIME$ in clause 2.2
- Clarification on the usage of @r=-1 with the Segment timeline in clause 3.1.
- Reference to DASH-IF IOP for joining, initial buffering and playout in clause 4.
- Addition of High Dynamic Range (HDR) video in clause 3.3.
- Clarification on ATSC events and DASH events in clause 6.3
- Update to xlink behavior in clause 5.1
- Miscellaneous editorial updates
Previous Versions
- Version 1.0: Guidelines for Implementation: DASH-IF Interoperability Point for ATSC 3.0 | License declarations
Guidelines for Implementation: DASH-IF SAND Interoperability
Scope
The scope of this document is to address interoperability aspects and deployment guidelines for Server and Network Assisted DASH (SAND). More specifically, the following aspects of SAND are covered: • Modes defining subsets of SAND messages and mandatory SAND protocols to use for specific deployment environments • Capability exchange procedures for DASH clients and DANEs • Security guidelines for SAND messages delivery • Procedures on DANE discovery for SAND
Comments and bugs may be submitted through the public github repository
Latest Version
Guidelines for Implementation: DASH-IF SAND Interoperability Version 1.0 (pdf) | License declarations
DASH-IF Implementation Guidelines: Token-based Access Control for DASH (TAC)
Scope
The scope of this document is to define a token-based access control mechanism and to enable the signaling of Authentication and Authorization (AA) protocols for DASH-based streaming. An Access Token is a proof that a DASH client or user of the client have been successfully authenticated and authorized in some pre-determined AA Systems to access a particular DASH resource, e.g. DASH segments or MPDs. This document defines an Access Token format for accessing DASH resources and its transport between a DASH client and a server, hence ensuring interoperability between content providers and content delivery networks. The document focuses on the signaling and exchange mechanisms to facilitate Access Token-protected requests for the delivery of MPDs, licenses, keys and segments. This document can be used in addition to the general DASH-IF Interoperability Points.
Comments and bugs may be submitted through the public github repository
Latest Version
DASH-IF Implementation Guidelines: Token-based Access Control for DASH (TAC) (pdf) | License declarations
DASH-IF Technical Specification: Live Media Ingest
Scope
This document presents the DASH-IF Live Media Ingest Protocol Specification. Two protocol interfaces are defined. The first, interface 1, CMAF ingest, is based on fragmented MPEG-4 as defined in the common media application track format (CMAF). The second interface is based on MPEG DASH and HLS as defined by ISO SC29 WG 11 and IETF. Both Interfaces use the HTTP POST Method to transmit media objects from the ingest source to the receiving entity. Examples of live streaming workflows using these protocol interfaces are also presented. The protocol interfaces also support carriage of timed metadata and timed text. Guidelines for redundancy and failover are also included.
Latest Version
DASH-IF Live Media Ingest Protocol v1.0 (pdf) | License declarations
Comments and Bugs
Comments may be submitted through the github or public bugtracker
DASH-IF Test cases and Vectors
- Guidelines for Implementation: Test cases and Vectors V1.0 | (Bugtracker)
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.
DASH-IF Interoperability Specification: Watermarking
- A initial version for community review for the DASH-IF IOP Watermarking specification is available here (pdf)
- This document is about so-called A/B watermarking techniques for ABR content where a series of A and B variants of segments are consumed by devices. It introduces an end-to-end architecture supporting service-side forensic watermarking when delivered on an OTT system. It defines:
- a format for a token carrying a series of A/B decision unique for every device. This token is used at the edge for delivering the right variant.
- Metadata and mechanisms for carrying this metadata from a transcoder to the edge. This is used for synchronizing the series on the same timeline for all devices.
- It supports any forensic watermarking technique, any encoder and any CDN. This is the result of the work in the Content Protection and Security task force in DASH-IF and has been done in collaboration between watermarking technology providers (NAGRA, Synamedia, Irdeto, Verimatrix), CDN providers (Akamai, AWS) and others.
- Community review is open until May 31st, 2022. Publication is expected by August 31, 2022.
- Comments may be submitted through the github.
DASH-IF Position and White Papers
- DASH-IF position Paper: DASH-IF Position Paper: Server and Network Assisted DASH (SAND) (500k PDF)
- DASH-IF position Paper: Proposed QoE Media Metrics standardization for segmented media playback (1M PDF)
- DASH-IF/DVB Report on Low-Latency Live Service with DASH (2M PDF)
- DASH-AVC/264: A Baseline Implementation for MPEG-DASH Press Conference Material (600k PDF)
- DASH-AVC/264: A Baseline Implementation for MPEG-DASH Press Conference (Streaming recording)
- Survey of European Broadcasters on MPEG-DASH
- Reinventing multimedia delivery with MPEG-DASH, SPIE Applications of Digital Image Processing XXXIV, Sept 2011.
ISO Publicly Available Specifications
- MPEG-DASH 2nd Edition Specification (ISO/IEC 23009-1:2014)
- MPEG-DASH 4th Edition Specification (ISO/IEC 23009-1:2020)
- T. Stockhammer: “Dynamic Adaptive Streaming over HTTP-Design Principles and Standards” In: MMSys ’11: Proceedings of the second annual ACM conference on Multimedia systems New York, NY, USA: ACM Press , Feb 2011,S. 133-144.
- MPEG-DASH Tutorial at Mile High Video