Introduction

Beyond the DASH-IF Interoperability Guidelines, DASH-IF also publishes specifications and reports. Those are collected in this clause.

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 Technical Specification (ETSI TS 104 002): DASH-IF Forensic A/B Watermarking

Scope

The scope of this work is the definition of an architecture and an Application Programming Interface (API) for supporting A/B forensic watermarking for Over-The-Top (OTT) on content that is delivered in an Adaptive Bitrate (ABR) format. To the possible extend, the proposed solutions do not make assumptions on the ABR technology that is being used, it can be for example, DASH or HLS. A/B forensic watermarking means that at least two watermarked versions of content (variant A and variant B) are delivered up to a CDN edge server from the encoder. The edge server is responsible for delivering either the A or B variant of every segment to the device.

While digital watermarking can be used for different use cases, this work will focus on forensic use cases. In this context, it is used to define the origin of content leakage. The watermarking technology modifies media content in a robust and invisible way in order to encode a unique identifier, e.g., a unique session ID. The embedded watermark provides means to identify where the media content, that has been redistributed without authorization, is coming from. In other words, the watermark is used to forensically trace the origin of content leakage.

Disclaimer

ETSI published this specification under the Publicly Available Specifications (PAS) agreement. For details on the PAS process, please refer to ETSI PAS Process Guide: https://www.etsi.org/images/files/ETSI_PAS_Process_Guide.pdf.

In addition, in case of any identified issues or bugs, please file issues here: https://github.com/Dash-Industry-Forum/Watermarking/issues.

Latest Version

DASH-IF Candidate Technical Specification: Content Steering for DASH

Scope

Content distributors often use multiple Content Delivery Networks (CDNs) to distribute their content to the end-users. They may upload a copy of their catalogue to each CDN, or more commonly have all CDNs pull the content from a common origin. Alternate URLs are generated, one for each CDN, that point at identical content. DASH players may access alternate URLs in the event of delivery problems. Content steering describes a deterministic capability for a content distributor to switch the content source that a player uses either at start-up or midstream, by means of a remote steering service.

Disclaimer

This document is a candidate Technical Specification. DASH-IF is publishing this specification initially, but the document has been submitted to ETSI and ETSI is asked to publish this document under the Publicly Available Specifications (PAS) agreement. For details on the PAS process, please refer to ETSI PAS Process Guide: https://www.etsi.org/images/files/ETSI_PAS_Process_Guide.pdf. Note that the ETSI specification may be different, addressing editorial updates. In addition, in case of any identified issues or bugs, please file issues here: https://github.com/Dash-Industry-Forum/Content-Steering/issues.

Latest Version

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

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.

Currently, no documents are under Community Review.

DASH-IF Position and White Papers

ISO Publicly Available Specifications