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
- Guidelines for Implementation: DASH-IF Interoperability Points V4.0: UHD Video and other extensions | (Bugtracker) | (diff to v3.3)
- Guidelines for Implementation: DASH-IF Interoperability Points V3.3: Alignment with MPEG-DASH, Guidelines on keys and other corrections| (Bugtracker) | (diff to v3.2)
- Guidelines for Implementation: DASH-IF Interoperability Points V3.2: Addition of Adaptation Set Switching, HTTPS Guidelines, Key Rotation and MPEG-H Audio| (Bugtracker) | (diff to v3.1)
- Guidelines for Implementation: DASH-IF Interoperability Points V3.1: Addition of CEA608/708, IMSC1, AC-4 | (Bugtracker)
- Guidelines for Implementation: DASH-AVC/264 Interoperability Points V3.0: DRM updates, Improved Live, Ad Insertion, Events, HEVC support, Trick Modes, CEA608/708 | (Bugtracker)
- Guidelines for Implementation: DASH-AVC/264 Interoperability Points V2.0: HD and Multi-Channel Audio Extensions | (Bugtracker)
- Guidelines for Implementation: DASH-AVC/264 Interoperability Points V1.0 | (Bugtracker)
DASH-IF Content Protection Information Exchange Format
- 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.
- DASH-IF Implementation Guidelines v1.0: Content Protection Information Exchange Format (CPIX)| (XML)| (Bugtracker)
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.
Robust and Consistent Live Services
- The change request against IOP v3.4 for Community Review is accessible here
- Community review is open until December 9th, 2016. Addition of Robust and Consistent Live Services is expected by December, 2016.
- Comments may be submitted through the public bugtracker. Please use [Live] tag.
- Several issues have been identified with consistent live services. Especially the packager actions in case of errors and program changes needs some detailed recommendations.
- The document provides the following extensions to v3.4:
- Update robust operation to add some more clarity
- detailed deployment guidelines for a packager
Guidelines for Implementation: DASH-IF Interoperability Point for ATSC 3.0
- The document for Community Review is accessible here
- Community review was closed August 21st, 2016. An updated version with publication is expected by November 30th, 2016. The document publication will be aligned with ATSC schedules.
- Comments may be submitted through the public github repository.
- The scope of this document is to provide a DASH interoperability point that is based on DASH-IF 2 IOPs and provides extensions to address use cases and requirements of ATSC 3.0.
Addition of HEVC-based UHD Video to DASH-IF IOP
- The change request against IOP v3.3 for Community Review is accessible here
- Community review was closed August 15th, 2016. Addition of HEVC-based UHD Video to DASH-IF IOP is expected by November 30, 2016.
- Comments may be submitted through the public bugtracker. Please use [UHD] tag.
- UHD is a relevant technology for improved user experience. UHD includes the ability to distribute video signals at higher spatial resolution, higher frame rates, wider color gamut and higher dynamic range. This first set of extensions for UHD focus on HEVC-based technologies to address higher spatial resolution in one case, and in the second case the addition of wide color gamut and high dynamic range. All technologies are based on HEVC decoding and regular display processing technologies. DASH is primarily used as a carriage format.
- The document provides the following extensions to v3.3:
- 4K Extension
- 4K Extension with Higher Dynamic Range and Wider Colour Gamut
DASH-IF Implementation Guidelines: Token-based Access Control for DASH (TAC) v1.0
- The document for Community Review is accessible here
- Community review was closed October 31st, 2016. An updated version with publication is expected by December, 2016.
- 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
- DASH-AVC/264 Online Conformance Tool
- Please use the following bugtracker to submit issues with the conformance software: https://gitreports.com/issue/Dash-Industry-Forum/Conformance-Software
- For detailed description see here: DASH-IF-Conformance-Software-v1.0.pdf
ISO Publicly Available Specification
White Papers and Background
- DASH-IF position Paper: Proposed QoE Media Metrics standardization for segmented media playback (1M PDF)
- DASH-AVC/264: A Baseline Implementation for MPEG-DASH Press Conference Material (2M 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.
- T. Stockhammer: “Dynamic Adaptive Streaming over HTTP-Design Priciples 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.