DASH-IF Logo

DASH-IF IOP v5 Part 1: Overview, Architecture and Interfaces

Living Document,

This version:
https://dashif.org/Guidelines/iop-v5/part01-overview.html
Issue Tracking:
GitHub
Currently open Part 1 issues
File a new Part 1 issue (then assign to Part 1 project)
Editors:
Thomas Stockhammer (Qualcomm)
Mike Dolan (Pearl TV)
Document Status:
Working Draft 0.3.
See Annex A: Document Status for versioning and workflow.
Contributors:
Contributors are maintained via GitHub pull requests to the IOPv5 repository.
Contributing:
See Part 1 §1.4 Contributing and Reviewing.
Key Words:
Overview, Architecture, Interfaces

1. Intellectual Property Rights

1.1. Disclaimer

This is a document made available by DASH-IF. The technology embodied in this document may involve the use of intellectual property rights, including patents and patent applications owned or controlled by any of the authors or developers of this document. No patent license, either implied or express, is granted to you by this document. DASH-IF has made no search or investigation for such rights, and DASH-IF disclaims any duty to do so. The rights and obligations which apply to DASH-IF documents, as such rights and obligations are set forth and defined in the DASH-IF Bylaws and IPR Policy, including but not limited to patent and other intellectual property license rights and obligations. A copy of the DASH-IF Bylaws and IPR Policy can be obtained at https://dashif.org/.

The material contained herein is provided on an "AS IS" basis and, to the maximum extent permitted by applicable law, this material is provided AS IS, and the authors and developers of this material and DASH-IF hereby disclaim all other warranties and conditions, either express, implied, or statutory, including but not limited to any (if any) implied warranties, duties, or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of workmanlike effort, and of lack of negligence.

In addition, this document may include references to documents and/or technologies controlled by third parties. Those third-party documents and technologies may be subject to third-party rules and licensing terms. No intellectual property license, either implied or express, to any third-party material is granted to you by this document or DASH-IF. DASH-IF makes no warranty whatsoever for such third-party material.

Note: IPR declarations relevant to DASH-IF specifications are published at https://dashif.org/ipr-declarations/.

1.2. Modal Verbs Terminology

In the present document, shall, shall not, should, should not, may, need not, will, will not, can, and cannot are to be interpreted as described in the ETSI Drafting Rules (Verbal forms for the expression of provisions). must and must not are NOT allowed in DASH-IF deliverables except when used in direct citation.

2. Scope

The present document provides an overview of the different features in the DASH-IF Interoperability Guidelines (IOP). In particular, it provides a reference architecture together with the relevant interfaces and functional blocks, and describes how the multi-part IOP document set fits together.

Note: DASH-IF IOP v5 is published as a multi-part document set. The parts and their summaries are described in § 5.4 DASH-IF IOP Parts.

3. Terms, Definitions, Symbols and Abbreviations

3.1. Terms and Definitions

For the purposes of the present document, the terms and definitions given in ISO/IEC 23009-1 [MPEGDASH] and the other referenced parts of DASH-IF IOP v5 apply.

3.2. Symbols

For the purposes of the present document, the symbols defined in the individual parts apply where used.

3.3. Abbreviations

For the purposes of the present document, the following abbreviations apply:

Abbreviations used in DASH-IF IOP v5.
Abbreviation Meaning
BMFF Base Media File Format
CMAF Common Media Application Format
DASH Dynamic Adaptive Streaming over HTTP
DRM Digital Rights Management
HTTP HyperText Transfer Protocol
IOP InterOperability Point
ISO International Organization for Standardization
MPD Media Presentation Description
MPEG Moving Picture Experts Group
RFC Request for Comments
TLS Transport Layer Security
URL Uniform Resource Locator
XML Extensible Markup Language

4. Conformance and Style

For detailed guidance on conformance and additional interpretation of the conformance key words (such as "shall"), see DASH-IF IOP v5 Part 12, Conformance and reference tools.

The key words *shall*, *shall not*, *should*, *should not*, *may, *need not, will, will not, can, and cannot are to be interpreted as described in the ETSI Drafting Rules. The words must and must not are not used to express normative requirements.

The following naming conventions apply in this document set:

5. Architecture and Interfaces

5.1. DASH-IF Baseline Architecture

A baseline architecture for DASH content distribution is provided in the figure below. Content is provided in any format and then encoded and prepared following the DASH Segment formats defined in ISO/IEC 23009-1 [MPEGDASH], in particular based on ISO BMFF (ISO/IEC 14496-12 [ISOBMFF]) and CMAF (ISO/IEC 23000-19 [MPEGCMAF]).

%%{init: {'theme':'neutral','themeVariables':{'fontSize':'16px','fontFamily':'system-ui, Segoe UI, Arial, sans-serif','lineColor':'#333'},'flowchart':{'curve':'linear','nodeSpacing':40,'rankSpacing':70,'padding':20,'htmlLabels':true,'useMaxWidth':true,'wrappingWidth':180}}}%%
flowchart TB
    CP[Contribution Link] --> ENC[ABR Encoder]
    ENC --> PKG["CMAF Packager    
(Encryption)"] PKG -- Ingest 1-IF --> MPG["MPD Generator /
DASH Packager"] MPG -- Ingest 2-IF --> CDN[("CDN:
Segment + MPD Server")] CDN -- DASH-IOP-IF --> AC["DASH Access
Client"] AC -- Playback-API --> RPP["Reference Playback
Platform"] APP[Application] -- Application-IF --> AC APP -- Client-API --> AC SC["Service
Configuration"] -- Service-Config-API --> MPG DRM["DRM
System"] -- CPIX-IF --> PKG DRM -- CPIX --> MPG classDef box fill:#eef3f8,stroke:#33475b,stroke-width:1.4px,color:#1a2733; class CP,ENC,PKG,MPG,CDN,AC,RPP,APP,SC,DRM box;
DASH-based distribution architecture.

The following major components are identified:

ABR Encoder

Adaptive Bitrate Encoder providing multiple equivalent versions of the same content in different qualities.

ISO BMFF/CMAF Packager

Encapsulation and packaging that creates segmented media content that can be distributed through DASH and played back on a reference platform through well-defined APIs. This specification assumes an ISO BMFF/CMAF Packager.

DASH Packager and MPD Generator

An operation that adds DASH formats and MPD signalling to create a DASH Media Presentation.

CDN

A scalable distribution network supporting the delivery and caching of DASH resources.

DASH Access Client

A client that uses the MPD and the referenced resources to create a streaming experience for a user by using a reference playback platform.

Application

An application that controls the DASH access client through a set of well-defined APIs.

5.2. Interfaces

The architecture defines a set of reference points (interfaces), explained below.

Reference points of the DASH-based distribution architecture.
Reference Point Explanation
Ingest 1-IF The first interface of the DASH-IF Live Media Ingest Specification: CMAF ingest, based on fragmented MPEG-4 (CMAF). It uses the HTTP POST method to transmit media objects from the ingest source to the receiving entity, and supports carriage of timed metadata and timed text, with guidelines for redundancy and failover.
Ingest 2-IF The second interface of the DASH-IF Live Media Ingest Specification, based on MPEG DASH and HLS. It uses the HTTP POST method to transmit media objects, and supports timed metadata and timed text with redundancy and failover guidelines.
CPIX-IF The Content Protection Information Exchange (CPIX) interface, defined in a separate specification. A CPIX document carries keys and DRM information used to encrypt and protect content, and may itself be encrypted, signed, and authenticated for confidentiality, source, and integrity.
DASH-IOP-IF The main interface defined in the DASH-IF IOP guidelines, providing interoperability between a content provider offering DASH-based services on a CDN and a DASH client.
Application-IF An interface, typically in an application, that provides the entry point to the DASH service by supplying a URL to an MPD.
Playback-IF A reference interface between a DASH access client and a playback and decryption platform, modelled on the HTML5 video element and Media Source Extensions, with the restrictions of the CTA WAVE device playback API.
Service-Config-API A network-side API that allows an application provider to configure parameters of a DASH-based streaming service, used to statically and dynamically create MPDs and manage segment data generation and distribution.
Client-API An API between the application and the DASH client (both access client and playback platform) to configure, control, and monitor the service.

5.3. DASH Reference Client

To develop the interoperability guidelines, a reference client for playback is assumed, as shown below. The reference client is not a mandatory implementation but serves as a reference for developing the IOP guidelines and for service offerings. The following basic workflow is assumed:

%%{init: {'theme':'neutral','themeVariables':{'fontSize':'15px','fontFamily':'system-ui, Segoe UI, Arial, sans-serif','lineColor':'#333'},'flowchart':{'curve':'linear','nodeSpacing':55,'rankSpacing':85,'padding':18,'htmlLabels':true,'useMaxWidth':true,'wrappingWidth':200}}}%%
flowchart TB
    APP[Application] -->|"Client-API (config / notifications / status)"| MGMT
    subgraph Player [DASH Player]
      direction TB
      subgraph AC [DASH Access Client]
        direction TB
        MGMT[Management] --- MPD[MPD Processing]
        MPD --- ASS[Adaptation Set Selection]
        ASS --- ABR[ABR Controller and Dynamic Switching]
        ABR --- TP[Download / Throughput Estimation]
        MGMT --- EV[Event Processing]
        MGMT --- MET[Metrics]
        MGMT --- MPM[Media Playback Management and Protection Controller]
      end
      MPM -->|Playback-API| MPP["Media Playback Platform and Content Decryption Module"]
    end
    SRV[("Segment Server / MPD Server")] -->|"DASH-Interface (request scheduling)"| TP
    classDef box fill:#eef3f8,stroke:#33475b,stroke-width:1.4px,color:#1a2733;
    class APP,MGMT,MPD,ASS,ABR,TP,EV,MET,MPM,MPP,SRV box;
DASH reference client.

The following functions are part of the reference client:

Detailed APIs and methods to communicate with a DASH reference client are implemented in the DASH-IF reference client (see § 5.4 DASH-IF IOP Parts and Part 12). DASH players typically rely on CMAF-capable playback platforms and decryption modules rather than a specific implementation; more detail on a CMAF-capable playback platform is given in Part 2.

Content security is accomplished in a device by two functions:

Received DASH events are processed for client consumption; see Part 10.

5.4. DASH-IF IOP Parts

The following summarises each part of DASH-IF IOP v5. Each part is published as a separate document; links point to the current published version.

Note: Issues for any part should be filed at the single IOPv5 issue tracker: https://github.com/Dash-Industry-Forum/IOPv5/issues. Use the label Part N or the title prefix [Part N]: to identify the relevant part (e.g. [Part 2]: Clarify @timescale requirement).

6. DASH-IF Registries

6.1. Overview

DASH-IF maintains two publicly accessible registries that serve as authoritative references for identifiers and codecs used in DASH-IF compliant services. These registries are living documents, continuously updated as new values are registered and existing entries are refined.

Services and clients shall use only identifiers and codec strings that are registered in the respective DASH-IF registry or explicitly defined in the applicable IOP v5 part.

6.2. DASH-IF Identifier Registry

6.2.1. General

The DASH-IF Identifier Registry at https://dashif.org/identifiers/introduction/ provides the canonical @schemeIdUri values and other string identifiers used across DASH MPD elements. The registry covers:

The registry source data is maintained at https://github.com/Dash-Industry-Forum/Identifiers.

6.2.2. Identifier Types in ISO/IEC 23009-1

ISO/IEC 23009-1 [MPEGDASH] defines several mechanisms for extensible identification in DASH MPDs. The following identifier types are used throughout the IOP v5 document set:

Key identifier types in ISO/IEC 23009-1 and their use in IOP v5.
Identifier type MPD attribute/element Purpose IOP v5 part(s)
@schemeIdUri + @value Role, Accessibility, AudioChannelConfiguration, EventStream, ContentProtection, SupplementalProperty, EssentialProperty Extensible scheme identification for descriptors and event streams Parts 2, 6, 7, 8, 9, 10
@codecs Representation, AdaptationSet Codec and profile identification string (RFC 6381 format) Parts 7, 8, 9
@mimeType Representation, AdaptationSet MIME type of the media container Parts 7, 8, 9, 10
Profile URI MPD@profiles, AdaptationSet@profiles, Representation@profiles URI identifying a DASH profile or interoperability point Parts 2, 3, 4
@id Period, AdaptationSet, Representation, Event Local identifier within the MPD for cross-referencing Parts 2, 4, 5

6.2.3. Using Identifiers in IOP v5

When an IOP v5 part requires a specific @schemeIdUri value, it shall reference the DASH-IF Identifier Registry as the authoritative source. Services shall use only registered @schemeIdUri values for the applicable scheme. Clients shall ignore descriptors with unrecognised @schemeIdUri values unless the descriptor is marked as EssentialProperty.

Note: The DASH-IF Identifier Registry is a living document. Services and clients should consult the current version of the registry rather than relying solely on the static tables in individual IOP v5 parts.

6.3. DASH-IF Codec Registry

6.3.1. General

The DASH-IF Codec Registry at https://dashif.org/codecs/introduction/ provides the canonical @codecs strings and CMAF profiles for video and audio codecs supported in DASH-IF compliant services. The registry source data is maintained at https://github.com/Dash-Industry-Forum/Codecs.

Detailed codec requirements are defined in:

6.4. Registering New Identifiers and Codecs

6.4.1. General

DASH-IF welcomes proposals for new identifiers and codec registrations from the community. The registration process ensures that new values are reviewed for technical correctness, uniqueness, and alignment with the DASH-IF IOP v5 framework.

6.4.2. Registering a New Identifier

To propose a new @schemeIdUri value or other identifier for the DASH-IF Identifier Registry:

  1. Submit a registration request using the DASH-IF Identifier Registration Form at https://docs.google.com/forms/d/e/1FAIpQLSfoMH4BL-1VwEpnVrYSnlvzwdO_7VAFeP1OfifxKW7nXVeWjg/viewform.

  2. Alternatively, file an issue at the Identifiers repository: https://github.com/Dash-Industry-Forum/Identifiers/issues.

  3. The DASH-IF Technical Working Group reviews the proposal and, if approved, adds the identifier to the registry.

Note: The Google Forms submission workflow is the current recommended entry point. A more streamlined GitHub-based workflow is planned for a future update.

6.4.3. Registering a New Codec

To propose a new codec for the DASH-IF Codec Registry:

  1. File an issue or pull request at the Codecs repository: https://github.com/Dash-Industry-Forum/Codecs.

  2. The registration requires: a defined @codecs string, a CMAF media profile or equivalent container format specification, demonstrated interoperability with at least one DASH client and one DASH packager, and alignment with the DASH-IF IOP v5 framework.

7. Change History

Part 1 change history.
Version Date Change
0.1 Initial Migrated from DASH-IF IOP-1 v5.0.0 (2022-06); references modernised (HTTP RFC 9110/9111/9112, TLS 1.3 RFC 8446); issue-tracker URL updated to the IOPv5 repository.
0.2 Initial Ported clause 5 (Architecture and Interfaces: baseline architecture, interfaces, reference client, part descriptions); added editors, contributors, and shared IPR boilerplate.
0.3 Enhancement Added Document Status section explaining Living Document status, Working Draft versioning, publication workflow (Working Draft → WG Review → Community Review → Approved), and issue reporting guidance (single IOPv5 tracker with Part N labels). Added hyperlinks to all part descriptions. Added Codec Registry links for Parts 7 and 8.
0.4 Enhancement Added DASH-IF Registries section covering the Identifier Registry (schemeIdUri values, profile URIs, ISO/IEC 23009-1 identifier types) and Codec Registry, with registration workflow (Google Forms, GitHub issues). Added DASHIF-IDENTIFIERS and DASHIF-CODECS biblio entries. Updated all 12 .bs files: replaced Repository: with !Repository:, added !Issue Tracking: and !Document Status: custom metadata entries.

Annex A: Document Status

A.1 Living Document

This document is published as a Living Document (LD). A Living Document is continuously updated as new content is added, issues are resolved, and the technical community provides feedback. It does not represent a final, approved specification.

The current status of each part is indicated by its version number in the Change History table:

A.2 Document Workflow

The DASH-IF IOP v5 document set follows this publication workflow:

  1. Working Draft: Editors draft content in the main development branch. Issues and pull requests are tracked at https://github.com/Dash-Industry-Forum/IOPv5/issues. Use the label or title prefix [Part N] (e.g. [Part 2]) to associate an issue with a specific part.

  2. WG Review: The Working Group reviews the draft and resolves open issues. A release candidate is tagged on the main branch.

  3. Community Review: The release candidate is published for public comment. A stable branch is created to maintain the approved version independently of ongoing development.

  4. Approved: After community review, the document is formally approved and published as a stable release. The stable branch is updated; the main branch continues development of the next version.

A.3 Stable and Development Versions

DASH-IF IOP v5 uses a two-branch model to allow simultaneous maintenance of a stable approved version and ongoing development of the next version:

Typical workflow for a new version:

  1. Development continues on main (Working Draft, version 0.x).

  2. When ready for WG Review, a release candidate is tagged on main (e.g. v1.0-rc1).

  3. After WG and Community Review, the approved version is tagged (e.g. v1.0) and the stable branch is fast-forwarded to that tag.

  4. The official publication is updated from stable.

  5. Development of the next version (0.x → 2.0-wip) continues on main.

Working on a new major version while maintaining a stable one:

If a new major version (e.g. v2) needs to be developed while v1 remains stable:

  1. Create a v2-dev branch from main for the new major version.

  2. The stable branch continues to track the approved v1 content.

  3. When v2 is approved, stable is updated to the v2 tag.

This model ensures that the official publication always reflects the latest approved content, while editors can freely develop the next version without affecting the stable publication.

A.4 Issue Reporting

All issues, bugs, and feature requests for DASH-IF IOP v5 shall be submitted through the single DASH-IF IOPv5 issue tracker at https://github.com/Dash-Industry-Forum/IOPv5/issues.

To associate an issue with a specific part, use one of the following conventions:

A.5 Contributing and Reviewing

A.5.1 General

DASH-IF IOP v5 is developed openly on GitHub. Contributions and reviews are welcome at all stages of the publication workflow. The primary mechanisms are GitHub issues (for feedback and discussion) and pull requests (for editorial contributions).

A.5.2 During the Working Draft Phase

While a part is at Working Draft status:

A.5.3 During WG Review

When a part reaches WG Review status (release candidate tagged on main):

A.5.4 During Community Review

When a part reaches Community Review status:

A.5.5 How to Submit a Pull Request

  1. Fork the IOPv5 repository at https://github.com/Dash-Industry-Forum/IOPv5.

  2. Create a branch from main with a descriptive name (e.g. fix-part2-timescale-clarification).

  3. Make your changes to the relevant .inc.md or .bs files in the rag-authoring-starter/specs/ directory.

  4. Build locally (optional but recommended) using python tools/publication/build_all.py --out ../dist to verify the changes compile without errors.

  5. Submit a pull request against the main branch of the IOPv5 repository. Reference the issue(s) the PR addresses in the PR description.

  6. Assign the related issue(s) to the appropriate per-part GitHub Project under the Dash-Industry-Forum organization.

  7. The DASH-IF Technical Working Group reviews and merges approved pull requests.

Index

Terms defined by this specification

References

Normative References

[ISOBMFF]
Information technology - Coding of audio-visual objects - Part 12: ISO base media file format. 2024. URL: https://www.iso.org/standard/83102.html
[MPEGCMAF]
Information technology - Multimedia application format (MPEG-A) - Part 19: Common media application format (CMAF) for segmented media. 2024. URL: https://www.iso.org/standard/85623.html
[MPEGDASH]
Information technology - Dynamic adaptive streaming over HTTP (DASH) - Part 1: Media presentation description and segment formats. 2022. URL: https://www.iso.org/standard/83314.html

Non-Normative References

[DASHIF-CODECS]
DASH-IF Codec Registry. URL: https://dashif.org/codecs/introduction/
[DASHIF-IDENTIFIERS]
DASH-IF Identifier Registry. URL: https://dashif.org/identifiers/introduction/