Introduction

On top of DASH-IF Interop Guidelines as well as ETSI specifications, DASH also has published a set of other publications guidelines.

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)] (https://dash-industry-forum.github.io/docs/DASH-TAC-v1.0.htm) (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.2 (Feb 24, 2024) (pdf) | License declarations

Comments and Bugs

Comments may be submitted through the github.

Earlier Version

DASH-IF Test cases and Vectors

DASH-IF Position and White Papers

ISO Publicly Available Specifications