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. Introduction
Early draft — work in progress. This part is at a very early, exploratory stage. The feature model, the taxonomy, the inventory tables, and the tool/example lenses below are preliminary placeholders intended to establish structure and to seed discussion. Nothing in this part is stable, complete, or agreed. Feature names, groupings, granularity, references, and support claims are expected to change substantially, and entries may be added, merged, split, or removed without notice. Do not treat this part as an authoritative statement of DASH-IF feature support or of IOPv5 scope.
This part provides an editorial inventory of DASH interoperability features used across DASH-IF IOP v5.
The inventory is intended to connect feature definitions to:
-
the relevant IOPv5 parts;
-
DASH-IF-IOP extension specifications in Dash-Industry-Forum/DASH-IF-IOP;
-
MPD, inband, and HTTP signalling;
-
content offering requirements and recommendations;
-
client requirements and recommendations;
-
reference implementations and tools such as dash.js and livesim2;
-
executable examples.
This part is initially non-normative and editorial. It is expected to evolve as the feature taxonomy is reviewed by the DASH-IF community.
3. Feature model
A feature is a named interoperability capability that can be described by one or more of:
-
MPD signalling;
-
inband signalling;
-
HTTP signalling;
-
content offering requirements and recommendations;
-
client requirements and recommendations;
-
reference-tool support;
-
executable examples;
-
conformance or validation coverage.
Features are not examples. Examples instantiate one or more features.
3.1. Granularity
The inventory distinguishes three levels.
- Feature
- A recognizable interoperability capability, such as Low-Latency Live DASH, MPD Patching, CMCD, Content Steering, Content Protection, Multi-Period, Multi-Audio, Text Tracks, Events, LCEVC, or Variable Substitution.
- Sub-feature
- A feature component with independent signalling or client behavior, such as ServiceDescription latency signalling, ProducerReferenceTime, Resync, SegmentTimeline addressing, CMCD header mode, ClearKey, WebVTT, MPD EventStream, or inband
emsg. - Option
- A parameterization of a feature or sub-feature, such as a specific target latency, chunk duration, codec, language, role, or DASH-IF-IOP extension mode.
4. Feature sources
4.1. IOPv5 parts
Features may be defined, constrained, or referenced by the following IOPv5 parts:
| Part | Scope |
|---|---|
| Part 2 — Core Principles and CMAF Mapping | Core DASH timing, addressing, CMAF mapping, UTCTiming, and MPD structure. |
| Part 3 — On-demand Services | On-demand service features and content offering constraints. |
| Part 4 — Live and Low-Latency Services | Dynamic MPDs, live timing, low-latency live, availability timing, ServiceDescription, and related client behavior. |
| Part 5 — Ad Insertion and Content Replacement | Period-based ad insertion, SGAI, SSAI, ad signalling, and content replacement. |
| Part 6 — Content Protection and Security | ContentProtection signalling, CENC, key rotation, Enhanced Clear Key, and security guidance. |
| Part 7 — Video | Video profiles, codec signalling, representation constraints, and DASH/CMAF video interoperability. |
| Part 8 — Audio | Audio profiles, multi-audio, language, role, accessibility, and channel signalling. |
| Part 9 — Text | Subtitles, captions, WebVTT, IMSC/TTML, and related text-track signalling. |
| Part 10 — Events | MPD events, inband events, timed metadata, and application event handling. |
| Part 11 — Additional Functionalities | Thumbnails, query/token mechanisms, metadata tracks, and additional feature areas. |
| Part 12 — Conformance and Reference Tools | Validator, dash.js, livesim2, reference assets, and conformance interpretation. |
4.2. DASH-IF-IOP extension specifications
Some features are currently defined as standalone DASH-IF-IOP extension specifications. Until those features are incorporated or profiled directly in IOPv5, this inventory references the corresponding folders in Dash-Industry-Forum/DASH-IF-IOP.
| DASH-IF-IOP folder | Feature inventory candidate |
|---|---|
specs/cmcd
| Common Media Client Data (CMCD). |
specs/content-steering
| Content Steering. |
specs/l3d
| L3D-related distribution feature, pending closer mapping. |
specs/lc-evc
| MPEG-5 Part 2 LCEVC carriage. |
specs/live2vod
| Live-to-VoD transition. |
specs/mpd-patch
| MPD Patching. |
specs/varsub
| MPD Variable Substitution. |
4.3. dash.js perspective
The dash.js sample catalog provides a client-oriented view of feature support. The inventory uses dash.js as a support lens for:
-
client implementation status;
-
relevant player settings and APIs;
-
sample availability;
-
player-observable behavior;
-
features requiring a custom application rather than only the reference player.
Major dash.js sample areas include live playback, low latency, ABR, buffering, DRM, multi-period playback, subtitles and captions, multi-audio, thumbnails, audio-only playback, SCTE/emsg events, CMCD, MPD patching, MediaCapabilities filtering, MPD anchors, and LCEVC.
4.4. livesim2 perspective
The livesim2 live source simulator provides a content/offering-oriented view of feature support. The inventory uses livesim2 as a support lens for:
-
generated MPDs;
-
URL-parameter-controlled feature combinations;
-
live and low-latency test streams;
-
SegmentTemplate and SegmentTimeline modes;
-
generated subtitles;
-
UTC timing;
-
CMAF chunking and ingest-related behavior.
5. Initial feature inventory
The machine-readable source for the seed inventory is maintained at:
rag/features/feature-inventory.yaml
The current seed is intentionally incomplete. It is included here to establish the publication structure and to support review of feature granularity.
| Feature ID | Feature | Category | IOPv5 reference | DASH-IF-IOP reference | Current tool/example lens |
|---|---|---|---|---|---|
dynamic-mpd-live
| Dynamic MPD / Live DASH | Live | Part 4 | — | dash.js Live samples; livesim2 dynamic live streams. |
segmenttemplate-number
| SegmentTemplate Number Addressing | Core | Part 2 | — | livesim2 default addressing mode. |
segmenttimeline-time
| SegmentTimeline Time Addressing | Core | Part 2 | — | livesim2 segtimeline_1; executable Part 4 example.
|
utc-timing
| UTCTiming | Core | Part 2, Part 4 | — | livesim2 utc_direct; executable Part 4 example.
|
availability-time-offset
| Availability Time Offset | Live | Part 4 | — | dash.js Live sample; livesim2 ato; executable Part 4 examples.
|
low-latency-live
| Low-Latency Live DASH | Low latency | Part 4 | — | dash.js low-latency test player; livesim2 chunkdur, ato, ltgt.
|
service-description-latency
| ServiceDescription Latency Signalling | Low latency | Part 4 | — | dash.js ServiceDescription settings; livesim2 ltgt.
|
cmaf-chunked-delivery
| CMAF Chunked Delivery | Low latency | Part 4 | — | dash.js low-latency playback; livesim2 chunkdur.
|
mpd-patching
| MPD Patching | Live | Part 4 | specs/mpd-patch
| dash.js MPD patching sample. |
cmcd
| Common Media Client Data | Reporting | Part 12 | specs/cmcd
| dash.js CMCD samples; HTTP request observability. |
content-steering
| Content Steering | Delivery | Part 12 | specs/content-steering
| dash.js Content Steering support. |
content-protection
| Content Protection | Protection | Part 6 | — | dash.js DRM samples; browser/CDM dependent. |
text-tracks
| Text Tracks | Media | Part 9 | — | dash.js subtitle/caption samples; livesim2 generated time subtitles. |
multi-audio
| Multi-Audio | Media | Part 8 | — | dash.js multi-audio samples; source asset dependent in livesim2. |
inband-emsg-events
| Inband emsg Events
| Events | Part 10, Part 5 | — | dash.js SCTE/emsg sample; usually requires app event handling. |
lcevc
| MPEG-5 Part 2 LCEVC Carriage | Video | Part 7 | specs/lc-evc
| dash.js LCEVC sample; requires LCEVC-capable pipeline. |
6. Executable examples
Executable examples are maintained separately from feature definitions and point back to the features they cover.
The current example registry is maintained at:
rag/examples/executable-examples.yaml
The initial examples focus on Part 4 low-latency livesim2 streams.
| Example ID | Covered feature IDs |
|---|---|
part04-ll-basic
| dynamic-mpd-live, low-latency-live, service-description-latency, cmaf-chunked-delivery, availability-time-offset
|
part04-ll-ultra
| dynamic-mpd-live, low-latency-live, service-description-latency, cmaf-chunked-delivery, availability-time-offset
|
part04-ll-segtimeline
| dynamic-mpd-live, low-latency-live, service-description-latency, cmaf-chunked-delivery, availability-time-offset, segmenttimeline-time
|
part04-ll-utc
| dynamic-mpd-live, low-latency-live, service-description-latency, cmaf-chunked-delivery, availability-time-offset, utc-timing
|
7. Maintenance workflow
The feature inventory is maintained editorially using the following workflow:
-
Add or update feature records in
rag/features/feature-inventory.yaml. -
Link executable examples to feature IDs using
covers_features. -
Use dash.js and livesim2 references as support lenses rather than as normative feature definitions.
-
Reference DASH-IF-IOP extension folders until the corresponding functionality is incorporated into IOPv5 text.
-
Periodically regenerate or update the published Part 13 summary from the machine-readable registry.
The dash.js sample catalog can be normalized using:
python tools/features/extract_dashjs_samples.py
The executable example registry can be URL-validated using:
python tools/validation/check_executable_examples.py rag/examples/executable-examples.yaml
8. Related feature-review activities
Feature inventories and feature-selection reviews are being carried out in other organizations as well. These are valuable inputs for scoping Part 13 and for deciding which DASH features are relevant for interoperable deployment. They are summarized here as editorial context only; none of the assessments below are DASH-IF positions.
8.1. DVB feature review of MPEG DASH editions
DVB has begun a systematic review of what has been added to MPEG DASH (ISO/IEC 23009-1) from the 3rd edition onward, with the aim of deciding which additions are relevant for DVB-DASH. This is directly useful for Part 13 because it frames each DASH feature in terms of concrete use cases, HLS equivalence, reference-tool support, and deployment relevance.
Key observations from the DVB review that are relevant to this inventory:
-
ISO withdraws older DASH editions when a new one is published (e.g. the 4th edition was withdrawn when the 5th was published), which complicates stable referencing and argues for a curated, editorially-maintained feature view such as Part 13.
-
Investment in reference tools and unit tests for additions after the 3rd edition is still limited, so tool/example support is an important dimension when assessing a feature’s readiness.
-
Each added feature is best characterized by: a short summary, a use case or scenario, an HLS equivalent (if any), the relevant DASH clause references, the closest existing DVB-DASH functionality, and open-source support status (dash.js, livesim2, Shaka, hls.js, and others).
The following table summarizes DASH features highlighted by the DVB review, grouped by the edition in which they were introduced. The "DVB relevance" column reflects the DVB review’s own preliminary assessment and is included here purely as external context.
| Feature / clause | Introduced | Summary | DVB relevance (per DVB review) |
|---|---|---|---|
| Producer Reference Time (5.12) | 4th edition | Signalling and mapping of media time to wall-clock time, including capture/encoding context. | Relevant |
| Leap seconds (5.13) | 4th edition | Support for client timing calculations when leap seconds occur. | Relevant |
| Service Description (Annex K) | 4th edition | Provider signalling on how a service is expected to be consumed. | Relevant |
| Missing Content Segment (6.2.6) | 4th edition | Signals that content is missing while conveying the media duration of the gap. | Probably (live) |
| Location and reference resolution (Annex A.11) | 4th edition | Consistent URL/reference resolution for MPD updates, segments, and other MPD resources. | Probably |
| Failover Content Signalling (5.3.9.7/5.3.9.8) | 4th edition | Offering failover content in place of properly-encoded main content on ingest/encoding errors. | Uncertain |
| Initialization Set / Group / Presentation (5.3.12) | 4th edition | Simplifies playback across Period boundaries. | Uncertain |
| Resynchronization (5.3.13, 6.3.2.5, Annex A.12) | 5th edition | In-segment resynchronization and early access; fast tune-in, loss recovery, seek accuracy. | Uncertain |
| MPD Patch framework (5.15) | 5th edition | Transmit only changed parts of a dynamic MPD to reduce bandwidth/processing overhead. | Perhaps (currently recommended against in DVB) |
| DASH profile for CMAF content (8.12) | 5th edition | Prescriptive mapping of CMAF structures/timelines to DASH. | Partial |
| Output protection / robustness signalling (5.8.4.12, 5.8.5.14) | 5th edition | Efficient content-protection signalling, robustness levels, and HDCP output-protection descriptor. | Relevant |
| Event/timed-metadata client reference model (Annex A.13) | 5th edition | Timing and processing model for MPD/inband event streams and timed metadata tracks. | Uncertain |
| Variable bitrate bandwidth signalling (5.3.5.6) | 5th edition | More flexible bandwidth signalling for VBR encoding. | Uncertain |
| Alternative Media Presentation (5.16, 8.14, Annex A.14) and Media Presentation Insertion events | 6th edition | Switching between main and alternative presentations (e.g. preroll/midroll ads, blackouts); enables SGAI. | Not yet; potential broadband ad-insertion alternative |
| Content Steering (K.3.6) | 6th edition | Interoperable server-centric multi-CDN steering (HLS-equivalent exists). | Overlaps with DVB multiple BaseURLs (client-centric) |
| Enhanced segment sequences / fast tune-in (5.3.5.7, 5.3.9.7, "L3D") | 6th edition | Faster time-to-first-video on join; relevant for ultra-low-latency services. | Relevant |
| Segment duration patterns (5.3.9.6.5) | 6th edition | Compact MPDs for fractional frame rates and when audio/video durations differ. | Relevant outside 50 Hz markets |
| CMCD reporting via service description (K.3.7) | 6th edition | In-manifest CMCD (v1) configuration without a bespoke application. | Relevant (relates to DVB metrics) |
| Event and playback restrictions via service description (K.3.8) | 6th edition | Signals ff/seek restrictions (e.g. no skipping during ads). | Relevant for ad insertion |
| Improved query parameters and header extensions (Annex I.3.6, I.4) | 6th edition | Token pass-through and richer URL parameterization; CDN authorization tokens. | Uncertain |
| Addressable Resource Index (ARI) Tracks (Annex M) | 6th edition | Exact quality/bitrate and inband-message presence for segments/chunks. | Uncertain |
| Alternative codecs via preselection (G.30) | 6th edition | A track decodable by more than one codec (e.g. HEVC / MV-HEVC / LCEVC). | Uncertain |
| Nonlinear playback / interactive storylines (Annex L) | 6th edition | User-driven nonlinear Period selection (Bandersnatch-style experiences). | Not relevant to DVB (app-level) |
| Multi-key encryption (G.25) | 6th edition | Different keys across CMAF-aligned switching sets (e.g. HD vs UHD). | Uncertain |
| ISO BMFF Advanced Linear / List / Single-Period Static profiles (8.13–8.15) | 5th/6th edition | Profiles for long-running linear content and imported/list MPDs supporting SGAI and blackouts. | Potential input for feature selection |
Additional editorial context from the DVB review:
-
MPD Chaining (5.11) and Flexible Insertion of URL Parameters (Annex I) were noted as, respectively, largely unused and only beginning to see adoption; Annex I is relevant for CDN authorization tokens (e.g. Common Access Token) and has partial dash.js support.
-
The DVB review draws on the DASH-IF April 2024 special presentation on the 6th edition (SpecialPresentation-6thEdition.pdf) as background material.
8.2. DASH core feature timeline (ISO/IEC 23009-1 editions)
This subsection collects the DASH features added in successive editions of ISO/IEC 23009-1, extracted from clause 4 (Overview) and clause 5 (Media Presentation Description) of the 6th edition, using the authoritative per-edition schema-addition list in subclause 5.2.3 ("Elements and Attributes added in revisions and amendments") as the backbone. Clause numbers use the 6th-edition numbering and should be re-verified against the final published text.
The full extraction, including the per-edition element/attribute lists and the mapping
from each feature to its defining clause, is maintained as a working report:
rag/reports/iso-23009-1-6th-edition-feature-extraction.md.
| Feature ID | Feature | Edition introduced | Primary clause (6th ed.) |
|---|---|---|---|
utc-timing
| UTCTiming | 3rd | 5.8.5 |
preselections
| Preselections | 3rd | 5.3.11 |
random-access-signalling
| RandomAccess signalling | 3rd | 5.3.5 |
switching-signalling
| Switching signalling | 3rd | 5.3.5 |
labels-group-labels
| Labels and Group Labels | 3rd | 5.3.10 |
service-description
| Service Description | 4th | Annex K |
initialization-set-group-presentation
| Initialization Set / Group / Presentation | 4th | 5.3.12 |
producer-reference-time
| Producer Reference Time | 4th | 5.12 |
leap-seconds
| Leap seconds | 4th | 5.13 |
content-popularity-rate
| Content Popularity Rate | 4th | 5.14 |
failover-content
| Failover Content Signalling | 4th | 5.3.9.7 |
availability-time-offset
| Availability Time Offset | 2nd/4th | 5.3.9.5 |
mpd-content-protection
| MPD/Period-level ContentProtection | 5th | 5.8.4 |
mpd-patching
| MPD Patch Framework | 5th | 5.15 |
resync
| Resynchronization | 5th | 5.3.13 / 6.3.2.5 |
extended-bandwidth
| Extended / variable bitrate bandwidth signalling | 5th | 5.3.5 |
output-protection
| Output protection + robustness | 5th | 5.8.4 |
container-profiles
| Container profile signalling | 5th | 5.3.5 |
content-steering
| Content Steering | 6th | Annex K.3.6 (+ 5.6.5) |
segment-sequences
| Segment Sequences | 6th | 5.3.9.7 |
duration-patterns
| Duration Patterns | 6th | 5.3.9.6.5 |
cmcd-reporting
| CMCD reporting via Service Description | 6th | Annex K.3.7 |
playback-restrictions
| Event & playback restrictions | 6th | Annex K.3.8 |
request-params
| Improved query parameters / header extensions | 6th | Annex I |
alternative-media-presentation
| Alternative Media Presentations + insertion/replacement events | 6th | 5.16 |
supplementary-video
| Supplementary video services + descriptor | 5th/6th | 5.8.5.16 |
edrap-esr
| Main and External Stream Representations (EDRAP/ESR) | 6th | 5.8.x |
This timeline is derived from a merged 6th-edition working draft and is itself an early extraction. Segment-format and profile additions (clauses 6–8, e.g. ISO BMFF Advanced Linear, List, and Single-Period Static profiles), Addressable Resource Index (ARI) tracks (Annex M), nonlinear playback (Annex L), and multi-key encryption are outside clause 4/5 and are tracked separately via the DVB feature review above.
8.3. Features beyond IOPv5
A separate, longer-term "features beyond IOPv5" exploration collects candidate features and technologies that are not (yet) in scope for IOPv5 but may become relevant in future guidelines. It is maintained as a living document:
The "features beyond IOPv5" document has not been updated recently, so some entries may be stale. It is nonetheless a useful source of candidate features and open questions when extending this inventory.
9. Open editorial issues
The following issues require review:
-
Whether DASH-IF-IOP extensions should remain external references or become IOPv5 feature definitions.
-
Whether feature granularity should be finer for codec, DRM, audio, and text options.
-
Whether Part 13 should eventually become a generated document from
rag/features/feature-inventory.yaml. -
Which features require conformance validator checks, executable examples, or custom test applications.