Introduction

DASH-IF publishes primarily three types of documents:

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

Scope

The scope of the DASH-IF InterOperability Points (IOPs) defined in this document is to provide support for high-quality video distribution for over the top services using H.264/AVC and H.265/HEVC. Both live and on-demand services are supported. The specified features enable relevant use cases including on-demand, live services, ad insertion, trick modes, seek preview, content protection and subtitling. Extensions for multi-channel audio and next generation audio with different codecs as well as extensions to video different codecs and Ultra High Definition are defined.

Any identified bugs or missing features may be submitted through the DASH-IF issue tracker at https://github.com/Dash-Industry-Forum/DASH-IF-IOP/issues.

Note that version 4.3 is published as an add on to v4.2, but with the next version it is expected that a either a multipart version or a restructured version will be generated, with a major editorial updates. The new version is expected to be available by spring of 2020.

Latest Version

Agreed Additions for Next Version

This clause lists a set of agreed additions that will be added to the next revision of the IOP Guidelines. They are typically documented as “Change Requests” documenting only the difference from the previous versions.

Previous Versions

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.2: Content Protection Information Exchange Format (CPIX) | (PDF) | (XSD) | (Bugtracker) | (Test vectors)

The document provides the following extensions to v2.1:

Previous Versions

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:

Previous Versions

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

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.

Next Generation Audio Alignment with ATSC3.0

SPEKE-CPIX alignment

Ad Insertion in DASH

Updated Timing Model for v5

Content Protection and Security

DASH Player’s Application Events and Timed Metadata Processing Models and APIs

WebIDL DASH Event Metadata API

DASH-IF Position and White Papers

ISO Publicly Available Specifications