SVTA_LOGO_FINAL_revised_2022

DASH-IF Meeting Minutes
January 7th, 2026 9:00am to 10:00am PT</p

Attendees

Thomas Stockhammer (Qualcomm)
Alan Stein (V-Nova)
Thasso Griebel (Castlabs)
Torbjorn Einarsson (Edgeware)
Moshi Elad (Synamedia)
Stephan Schreiner (Dolby)
Mohamad Raad (Unified Streaming)
Nasir Bello (Rogers Communications)
Görkem Güclü (Fraunhofer FOKUS)
Iraj Sodagar (Dolby)
Gwendal Simon (Quortex)
Glenn Deen (Comcast/NBCUniversal)
Yasser Syed (Streaming Video Technology Alliance (SME))
Peter Chave ()
Benjamin Toombs (Warner Bros Discovery)

Minutes

Minutes SVTA DASH-IF WG 26-01-07

Logistics:

Attendance:

  • DASH-IF: Thomas Stockhammer (Qualcomm, Co-Chair), Alan Stein (V-Nova), Thasso Griebel (castLabs), Torbjorn Einarsson (Eyevinn), Moshi Elad (Synamedia), Stephan Schreiner (Dolby), Mohamad Raad (Unified Streaming), Nasir Bello (Rogers Communication), Gorkem Guclu (Fraunhofer), Iraj Sodagar (Dolby), Gwendal Simon (Synamedia), Glenn Deen (Comcast), Yasser Syed (SME), Peter Chave (Akamai), Ben Toombs (WBD), Lindsey Richardson (AMS)
  • DVB:

Agenda:

 

Notes:

Welcome

Tools

  • js
    • js v5.1.0 released.
    • LiveSim2
    • Sponsoring
      • we need to evaluate how we can support sponsoring
      • (Yuriy/Alex/Daniel/Peter/Gwendal) please check what the issue is on sponsoring and give feedback on how to drive this.
      • js sponsoring is terminated by the end of the month.
        • expect that not even maintenance will continue
        • pull requests will not be controlled
        • We need to concretely formulate the issue and send a message to js list.
        • We need to make sure that the communication is not destructive and funding is planned to continue.
        • Letter to js Letter to dash.js
          • A version has been drafted
          • Detailed discussion with SVTA leadership and members
          • Not yet sent
          • Two companies committed to sponsoring
          • SVTA Board will make decisions to move forward
          • Some dissatisfaction from member companies wrt to handling of js – increased membership fee. No commitments yet. Lack of handling.
          • Extension done prior to Christmas
        • same issue applied to livesim2
        • Initial page here: https://www.svta.org/open-source-project/dash-js/
          • needs to be improved.
        • Test Tool Calls

Authoring

  • We do Google Docs and Bikeshed
    • start with Google Docs unless main author wants to do bikeshed –
    • convert to bikeshed in the publication process
  • Document process: Document-Rules
    • Discussion with SVTA Office
  • We did not discuss this during f2f.

IOP Documents

Identifiers

Other Specifications

Content Protection and Security

Notes from f2f meeting June 2025

  • Laurent presents slides
  • CPIX
    • SVTA to ETSI is close to be finalized
    • DASH-IF WG can still publish – will check with Chantal
  • Watermarking API
    • Finalize the spec
    • Publish through SVTA
    • (Laurent) send Watermarking API spec
      • sent to JT today July 8, 2025
      • acknowledge by JT
    • (Thomas/JT) publish through SVTA processes
  • Watermarking spec requires some updates
  • V5 – Part 6
    • Community Review initiated
      • Published – see above
    • LS from CTA WAVE
      • Attached survey results
      • Actions:
        • (Thomas) We respond that we do this for live sim with multiple servers, share infrastructure with them
      • We will review issues in Content Protection and security and address if needed
      • Offering of commercial DRM servers:
        • EZDRM
        • CastLabs
        • Axinom
      • Presentation from Moshi Elad
        • Discussion on different options.
        • No decisions, please join the discussion in the CPS TF
      • Call has changed
        • Back-to-back meetings with Security
        • If not workable or inconvenient, go back to Wednesday.

Media Delivery Architecture

  • Rufael presents slides
  • Thomas presents slides
  • Rufael refers to TM-STREAM activity
  • Discussion at f2f
    • This is NOT complete. It’s missing the ad-tech stack:
    • https://lucid.app/lucidspark/71042dea-0b2e-41ed-b063-4ab14d17a0c6/edit?viewport_loc=-4431%2C-378%2C7297%2C4527%2C0_0&invitationId=inv_ddf19a1c-efef-42b1-8ab5-e168ca2ff9c6
    • I largely focused on streaming but we could easily incorporate non-streaming distribution (I did that a little).
    • Feel free to add comments. Perhaps this needs to be an SVTA-wide project like the Moon project.
  • Bottom-up approach
    • SVTA will potentially create some sort of activity

Features

Overview

Feature Overview

Published Features

Live2VOD

  • Create a pull request and ask for review
  • Community Review issued until March 31, 2025
  • (Daniel/Tobbe) please check
    • to be finalized in next test call.

L3D

  • Google Docs
    • please progress work here initially
    • (recover DASH-IF document)
  • Next Steps (still valid)
    • add the above logic to the introduction of the feature.
    • Start documenting the technology by reference to 6th edition
    • also document client requirements
  • 6th edition available ⇒ expect discussion at the f2f meeting in Berlin.
  • We did not cover this during f2f
  • We need to make sure that we define L3D, it is a combination of content offering and client implementation
  • Summary of offline call November 3, 2025:
  • Introduction: Thomas, Daniel, Khaled, Piers, and Alvaro discussed the implementation and documentation of the L3D feature in Dash JS. They reviewed the current status, identified issues, and planned the next steps.
  • Documentation and Implementation Plan: Thomas explained the need for documenting the L3D feature, including the implementation plan for Dash JS and the work done in ???. The goal is to support the implementation of test tools and ensure proper documentation.
  • Low Latency and New Requirements: Thomas and the team discussed the requirements for low latency, including faster tune-in time, switching latency, and compression efficiency. They also considered new use cases such as ad insertion and LL-HLS compatibility.
  • Challenges with Partial Segments: Daniel highlighted the challenges with partial segments, including manual and automatic quality switches, and playback start issues. The team discussed potential solutions and the need for specific logic in the player to handle these situations.
  • Compatibility with LL-HLS: The team discussed the compatibility of L3D with LLHLS and the issues related to segment availability time offset. They agreed on the need to document these issues and ensure proper handling in the player.
  • Action Items
    • Reference Slides Distribution: Send the slides to all meeting participants to ensure everyone has access to the latest reference material. (Silhavy)
    • IAP Meeting Preparation: Share the slides with the IAP group and coordinate discussion of next steps in the upcoming IAP meeting. (Silhavy)
    • Dynamic Ad Insertion Stream: Provide a stream for dynamic ad insertion to Daniel for testing and development purposes. (Khaled)
    • Availability Time Offset Documentation: Document the usage and impact of availability time offset in reference streams, clarifying its effect on timing calculations in the player. (Thomas)
    • Reference Stream Correction: Fix the issue with the availability time offset in the reference streams to ensure correct timing calculations in the player. (Piers)
  • Thomas Stockhammer shared two reference documents:
  • Thomas – chat with Alex
    • ensure reference content, documentation and js implementation

Content Steering

  • Google docs:
  • Github: https://github.com/Dash-Industry-Forum/Content-Steering/issues
    • please check issues here ⇒ many updates done. expect spec updates
    • We may need to have new features and updates to the ETSI spec
    • Google docs version ts_103998v010101p-revision.docx
  • Thomas will try to update agreements
    • in progress
    • Please feel free to also provide additional comments in spec, please use commenting and/or revision modes.
  • Apple is breaking out the HLS Content Steering
    • Specification is available
    • comparison document started
      • Significant progress
      • Still some open issues – work offline
      • We try to conclude this on Aug 12, 2025
      • Then we decide how to proceed with a message to IETF/HLS-interest
      • Yuriy will finish this week
      • HLS interest meeting is October 26
      • On October 14, we will complete this to be available for HLS interest meeting. Yuriy will attempt to attend. Alex will do an agenda request.
    • We reviewed slide set from Yuriy
      • We also the updated comparison document
        • We would like to complete the comparison document for July to send it to Apple for consideration.
      • We also need to update the ETSI specification eventually
    • Add slides and feedback from HLS interest group
      • Thomas adds link
      • Yuriy writes comments on the draft specification.

MPD Patch

  • Google Docs
  • Tobbe added to bikehed
    • Zach please add your content as well
    • Please contribute on Bikeshed
  • (Thomas) Get a summary on bikeshed and what is missing

CMCD

  • Google docs: CMCD
  • Presentation by Will on CMCDv2
    • Version 2 expected by June 2025.
  • Thomas presents slides during WG meeting December
    • Status of CMCDv2: Nicolas explained that the CMCDv2 specification is nearing completion, with the working group targeting the end of the year for finalization. The group is resolving ambiguities and editorial issues, especially around key definitions and reporting modes. The “response mode” has been merged into the “event mode,” leaving only “request” and “event” modes for implementation.
    • Integration with dash.JS: Daniel confirmed that a pending pull request for CMCDv2 integration exists and is scheduled for Dash JS version 5.2, expected early next year. The team is waiting for the CMCDv2 spec to stabilize before finalizing the implementation.
    • Configuration and Filtering: There was an in-depth discussion about how to configure reporting—specifically, whether filtering should apply to what is reported (e.g., by service location or adaptation set) or where reports are sent. The group noted ambiguity in the current specification and debated whether reporting should be differentiated by service location, adaptation set, or request type. Thasso and Daniel highlighted that most clients aggregate throughput across all service locations, not per-location, and that excessive granularity could complicate implementations.
    • Use Cases and Implementation: The team discussed the practical implications of reporting configuration, including the need for clear guidelines on what clients should report and how to avoid unnecessary data flooding to CDNs. There was consensus that the specification should clarify these behaviors to ensure interoperability and efficiency.
    • Next Steps:
      • Continue refining the configuration model and clarify the intended filtering and reporting logic.
      • Review the CMCDv2 guidelines and use cases to ensure the Dash integration aligns with best practices.
      • Topic will be revisited in the next session, with the possibility of a dedicated meeting to finalize the approach and resolve outstanding ambiguities.
    • MPEG Document
    • Incoming LS from 3GPP
      • S4-251997 [FS_AMD_Ph2] Draft LS to CTA WAVE on CMCD phase, to CTA WAVE, CC: SVTA DASH-IF WG, ISO/IEC SC29 WG03 (MPEG Systems)

CMSD

Variable Substitution using query and header parameter

  • Alex Giladiwill be lead
  • Google Docs:VarSub
    • agreed the use cases.
  • Update from 6th edition
  • Add to ad discussion

Pattern

  • Pattern
    • skeleton created
  • (Thomas) Create Bikeshed.
  • Thasso presents slides
    • Add information to the above document
      • Use cases
        • Fractional frame rates
        • Segment durations without magic numbers
        • Part of Segment sequences
      • functionality in DASH 6th edition
      • Magic Numbers and examples
    • Live Sim extensions and js support
  • on hold until we close the other issues or get traction, we may look at this a bit when we discuss MPD size reductions.

Server Guided Ad Insertion

  • Google Docs: SGAI
  • f2f meeting in Berlin
    • Thasso presented slides
    • We update the document above with examples
      • Prose description of the use case
      • XML snippet of the event or MPD
      • A diagram that explains
      • Equivalence with HLS
      • (Information exchange in two player implementation)
    • Nicolas also shows some fork
    • Implementation:
      • Qualabs is working on 2 player model for js
      • livesim no implementation yet, Thasso proposes to use the parameters of their implementation example in the liveSim config
    • Virtual meeting December 2025
      • Thasso presents updated slides
      • We stick with the above concept
      • Dedicated calls: Thasso, Daniel, Bertrand, Olivier, Iraj, Thomas
        • Create one template in a call
        • 9:15am cet on Tuesday – inform Jordi.
      • First use cases:
        • Insertion into Static content
        • Insertion into Live Content
      • there is a 2 player model in dash.js
    • Meeting December 16 2025
      • Updates done during the meeting
      • Question – what happens if a new Period is inserted during an ad slot?
    • DVB
      • DVB will start commercial work on SGAI, among others to introduce 6th edition. Idea is to create a survey targeted to broadcasters/content distributors. I would like to involve DASH-IF in the survey generation. Anyone interested to support?
      • (Thomas) will share offer through list
      • Angelo reports that DVB will issue a survey on targeted advertising/addressable TV to identify commercially relevant use cases

LCEVC

  • Google Docs: LCEVC
  • Published on December XX?
    • add information

HDR-Video and Preselections

  • Stephan will prepare some proposed updates to video part
  • Stefan added text on SCTE metadata as well as on mapping to media capability API
    • Informal review until end of August – please
    • Once we finalized the comments, we start formal WG review
  • We need to fix VVC issue: https://github.com/Dash-Industry-Forum/DASH-IF-IOP/issues/441
  • Dedicated call on Dec 17, 5:10pm cet
    • Updates done
    • Remove the incomplete codec table and ensure the document is accurate and not misleading. (Thomas)
    • Check the CTA WAVE specification for detailed mapping of media profiles to parameters. (Stefan)
    • Finalize the document updates and send it out for review over Christmas. (Stefan)
    • Send the document for review and plan to publish it in January if there are no comments. (Thomas)
    • Stephan will do final fixes
    • We send for WG review by end of week Jan 09, 2026.

Preselection

 

Events Update

  • (Thomas) recover
  • 6th edition updates need to be added

 

MoQ and DASH

  • Google Docs: MOQ-DASH
  • Keep it simple – mostly PoC.
  • Updates in doc:
    • (Thomas): We also create a github
    • (Will): add a small scope
    • (All): Add to contributor is interested and look at scope
  • We continue discussion in WG for now, and check how this progresses

 

Robust Operation and Error Handling

Content Annotation and Media Mapping

 

C2PA

  • js supports dispatching emsg to application
  • Unified Streaming demonstrated this
  • Create a document that shows how C2PA can be integrated in DASH, including the usage of js. Support implementations and identify potential open issues.
    • Interested parties: Unified, EZDRM, Fraunhofer, Qualcomm, Qualabs, Dolby (please add your name)
    • (Thomas) create doc and send request to mailing list and announce at SVTA meeting as well for broader members
  • Document is available is here:
  • We do a detailed C2PA discussion next week (30min) in DASH-IF WG!
  • Presentation on 9/23 by Iraj

https://docs.google.com/document/d/1bwiysZLUBS8qQehy-L_57lZWVAdGEqcswJqr4gkg8nE/edit?tab=t.0

  • Agreed to continue studying this topic moving forward.
  • Thasso will ask Michael to organize a joint meeting between SVTA DASH-IF WG and C2PA live WG.
    • Do we have a liaison agreement with SVTA?
    • Do we make it a public session?
    • How can we make sure that discussions are not happen everywhere (DVB, MPEG, C2PA, SVTA) – some sort of collaboration is needed.
    • Introduction has happened, expect more feedback soon.
    • We should have a meeting with WG, but not in November. Maybe some time in December would work. December 15 week may be it. Maybe early in the week.

 

Optimized MPDs

JSON-based MPD and smaller MPDs

  • Questions
    • Functional – how can we easily convert to JSON, are there automatic tools
    • Performance – what is the gain in
      • Size
      • Parsing
    • We could also reduce the options in a JSON-based MPD
  • Additional formats may be looked at as well, including binary
  • We may also work on a document for creating proper MPDs.
  • Binary update channel to client
    • Include all information that terminates in DASH client
    • Does not include media
    • Event Message track may be used
    • Could also include metadata tracks for quality
    • We add this as another option
  • Next steps:
    • Address this conceptually
      • Live Services for which the main content is pretty stable
      • Create a work flow
      • Offering MPD
      • Address conceptually.
    • (Alex) check on the above discussions and initiate work as appropriate
    • Bertrand offered to provide some background
    • Thomas find minutes.

General/New Issues

 

  • SVTA QOE WG MQA reporting
    • currently uses CMSD: https://docs.google.com/document/d/1ncNNitIY-1mpVoWASM_BVe8LL1WUAGU0lUqN2latKpw
    • some discussion
      • accurate metrics definition
      • how does it work for low latency
    • Please check this
    • Some comments:
      • PSNR and SSIM may deserve to be provided in 2 variants: a) computed relative to the resolution of the stream as encoded, and b) computed relative to the full resolution of video (after upscaling)

Partner Organizations

General

  • Liaison Page
    • W3C is formed
    • 18 organizations
    • there will be a liaison@svta.org (could go to WG)
  • Liaison Tracking Page
  • Liaison Committee (Alex Giladi)
  • Working Group playbook will be include information

MPEG (Thomas)

3GPP (Thomas)

  • 3GPP at MWS
  • AMD Phase 2 – see LS above

CTA WAVE (Thomas)

  • Technical Work:
    • Test Suite (ongoing)
    • CMCD (v2 about to complete)
    • CMSD (no v2 started yet)
    • CAT (complete)
    • DASH/HLS Interop (recent update, continuous work)
    • Media Tracing (in progress)
    • Others
  • Specification:
    • Documents are no longer freely available
    • SVTA relies on some specifications

DVB (Thomas)

ATSC (Thomas)

  • see publication.

Ultra HD Forum

  • see Watermarking CPS TF report

HbbTV (Jon/Thomas)

  • See presentation above

W3C

  • MSEv2
  • joint call on presentation of short-comings of MSE
  • We can join as SVTA
  • Minutes include the detailed issues of the short-coming
    • Slides are also available and on ARO
  • Might also be picked in CML
  • Add minutes MEI on DRM

5G-MAG

IETF

  • Lot’s of discussion on Media over QuIC (MOC) for Live Media Ingest and Distribution.

ETSI JTC Broadcast

C2PA

  • keep track of what is happening.

Next Meetings

  • Can we resume on January 7, 2026 (at 6pm CET, 9AM pacific)?
  • We resume on January 13, 2026 (January 6 is national holiday)
    • LS to MPEG
    • Other as this comes up
    • Planning for upcoming calls with specific topics
  • January 27
  • February 3
  • February 10 (3GPP, Yuriy)
  • February 17
  • February 24

 

Meeting Minutes

Key Topics:

  • Introduction: Thomas, Silhavy, and other participants discussed the meeting agenda, including topics such as content steering, ATSC, and CMCDV2. They also addressed the need for better documentation and the status of the Dash JS maintenance contract. 1
  • Content Steering: Yuriy presented an update on content steering, comparing the IETF draft with the Dash IF specification. They identified areas of alignment and proposed changes to harmonize the specifications, including client behavior and steering parameters. 2
  • ATSC Dash IOP: Alan provided a status update on the ATSC Dash IOP, highlighting the need for updates to align with the latest Dash IF specifications. They discussed potential paths forward, including adopting Dash IOP 5.1 or creating a new fork document. 3
  • Dash JS Maintenance: Daniel and Torbjörn discussed the status of the Dash JS maintenance contract, noting that a three-month extension is being considered. They emphasized the importance of securing funding and sponsorship for the project. 4
  • CMCDV2 Integration: Thomas, Nicolas, and other participants discussed the integration of CMCDV2 into Dash JS. They reviewed the current implementation and identified areas for improvement, including configuration and filtering options. 5
  • Documentation Management: Participants discussed the need for better documentation management within the Dash IF working group. They considered the possibility of having a dedicated project manager or librarian to handle document versioning and publication. 6

Action Items:

Content Steering:

  • Send the proposed comments on the IETF draft to the HLS interest group and introduce Gwendal to the group. (Yuriy) 7

Dash JS Maintenance:

  • Wait for the outcome of the SVTA board meeting regarding the three-month extension of the Dash JS maintenance contract. (Daniel) 8

CMCDV2 Integration:

  • Review the CMCD client implementation recommendations and discuss potential updates to the Dash IF specification. (Nicolas, Thasso, Daniel) 9

Documentation Management:

  • Discuss with SVTA staff the possibility of having a dedicated project manager or librarian to handle document versioning and publication. (Thomas) 10

ATSC

Alan’s Presentation on ATSC DASH IOP Status

  • Background & Status: Alan explained that the ATSC DASH IOP profile was forked from the main DASH IOP in 2018 due to ATSC 3.0-specific requirements and incompatibilities. This profile is normatively referenced by both the ATSC signaling specification and the Brazilian SBTVD DTV+ transport spec, making it significant for deployed broadcast systems. 1
  • Technical Incompatibilities: He highlighted several incompatibilities, such as support for interlaced HEVC video, unique temporal layering requirements for 4K120 content, SHVC two-layer scalability, and stagger cast audio. Some of these features are not supported or are handled differently in the main DASH IOP. Alan noted that while these features are referenced, their actual deployment in the field is limited or unclear. 2
  • Document Updates & Challenges: The ATSC profile has not been updated since 2018, while ATSC has since added support for VVC and MPEG-H audio, which are not reflected in the current IOP. There is uncertainty about how to proceed with aligning or updating the profile, especially as ATSC and SBTVD standards evolve. 3
  • Potential Paths Forward: Alan outlined three possible next steps:
    • ATSC could adopt DASH IOP 5.1 and deprecate incompatible technologies, possibly via a recommended practice.
    • A new forked document could be created to address ongoing incompatibilities (though Alan expressed reluctance for this approach).
    • The current state could be maintained, though Alan believes this is problematic. 4
  • Discussion & Implications: Thomas and others discussed that many of the incompatibilities may not be critical in practice and that the DASH IOP should ideally allow ATSC to add codecs without requiring DASH IF updates, unless new features go beyond codec signaling. There was consensus that ATSC should lead any profile updates, with DASH IF providing support as needed. 5
  • Administrative Considerations: It was noted that the ATSC DASH IOP document also references an outdated MPEG DASH specification, which may require review and cleanup. There was discussion about better integration with CMF and alignment with receiver testing efforts. 6

Next Actions/Steps

  • No immediate action was assigned to DASH IF; the group agreed that ATSC should initiate any updates or changes to the profile and request support from DASH IF as needed. 7
  • Alan will share his presentation slides as a PDF for reference. 8
  • The group will monitor developments and remain open to supporting ATSC, with a focus on cleaning up documentation and ensuring alignment with evolving standards. 9

dash.js, Live Sim, and Open Source Tools – Status & Discussion

  • Contract & Maintenance Uncertainty: The current maintenance contract for dash.js was set to expire, creating uncertainty about ongoing support. JT from SVTA requested a three-month extension to bridge the gap, and a board meeting was scheduled to decide on this extension. The expectation is that maintenance will continue at least through the next three months, but as of the meeting, no final contract was in place. 1
  • Live Sim Status: Similar uncertainty applies to Live Sim, with hopes that the board meeting would also address its maintenance. There was optimism that the contract extension would cover both dash.js and Live Sim, but confirmation was pending. 2
  • Future Funding & Sponsorship: The group discussed challenges in securing sustainable funding for these open source tools. Several participants noted that internal company processes make direct sponsorship difficult, and there was a preference for SVTA membership fees to cover tool maintenance rather than seeking additional sponsorships. The idea of a dedicated SVTA budget for these tools was favored. 3
  • Awareness & Engagement: Suggestions included increasing visibility for sponsorship opportunities, such as adding notices to the GitHub landing page and NPM installation, and creating a sponsor web page listing contributing companies. There was consensus that the sponsor page should clearly explain the importance of sponsorship and provide an easy way for companies to contribute. 4
  • Recognition & Marketing: Participants recommended that the sponsor page be more marketing-friendly, including company logos, descriptions, and possibly testimonials, to help advocates within companies justify sponsorship. The idea of providing “supporter” badges or stickers for company websites was also raised. 5
  • Technical Status: Daniel confirmed that dash.js will continue to receive updates, and maintenance will proceed as usual unless explicitly told to stop. The next release is planned to include pending features, such as CMCDv2 integration, once the contract situation is clarified. 6
  • Action Items: The group agreed to wait for the outcome of the SVTA board meeting before sending any formal communications or making further decisions about tool maintenance and sponsorship strategy. 7

Yuriy’s Presentation on Content Steering: Summary, Conclusions, and Next Steps

  • Overview & Objectives
    • Yuriy presented an updated comparison of the IETF Content Steering draft with DASH-IF and HLS approaches, focusing on terminology mapping, feature alignment, and integration strategies. The goal was to identify harmonization opportunities and clarify differences for future specification alignment. 1
  • Key Discussion Points
    • Mapped terms between IETF, DASH, and HLS (e.g., CDP, content description, pathway ID, query parameters). 2
    • Highlighted areas of alignment (marked green) and divergence (marked red), especially in client behavior, query parameter handling, and error management. 3
    • Emphasized the need to harmonize query parameters to avoid duplicating logic for clients supporting both DASH and HLS. 4
    • Discussed client behavior differences, such as when to fetch the steering manifest (“before start”), penalization delays, and error handling (e.g., 410/429 responses). 5
    • Noted that some behaviors (e.g., penalization, error handling) should ideally be consistent across protocols for better server optimization and client predictability. 6
  • Proposed Comments/Recommendations
    • Delegate “before start” logic to the protocol (CDP) for clarity.
    • Add explicit error handling for initial manifest fetch failures.
    • Harmonize penalization delay logic (prefer DASH’s TTL-based approach).
    • Advocate for unified query parameter naming to simplify client/server implementations.
    • Allow comma-separated lists and clarify CMCD carriage. 7
  • Integration Approach
    • Plan to reference the IETF spec in DASH-IF, with a mapping section to clarify terminology and behavior.
    • DASH-IF will define clarifications and extensions as needed, especially for DASH-specific features like adaptation set switching. 8
  • Conclusions & Next Steps
    • Yuriy will submit the identified comments to the HLS Interest Group and as a reviewer to the IETF draft, prioritizing essential changes (e.g., “before start” logic, error handling) and suggesting harmonization where feasible. 9
    • Gwendal requested to be included in the HLS Interest Group discussions for greater transparency and participation. 10
    • The group agreed to focus on a minimal, high-impact set of change requests to maximize the likelihood of adoption by IETF/HLS. 11
    • The DASH-IF spec will be updated to reference and clarify integration with the IETF content steering standard once it is finalized. 12

CMCD Presentation & Discussion Summary

  • Status of CMCDv2: Nicolas explained that the CMCDv2 specification is nearing completion, with the working group targeting the end of the year for finalization. The group is resolving ambiguities and editorial issues, especially around key definitions and reporting modes. The “response mode” has been merged into the “event mode,” leaving only “request” and “event” modes for implementation.
  • Integration with Dash JS: Daniel confirmed that a pending pull request for CMCDv2 integration exists and is scheduled for Dash JS version 5.2, expected early next year. The team is waiting for the CMCDv2 spec to stabilize before finalizing the implementation.
  • Configuration and Filtering: There was an in-depth discussion about how to configure reporting—specifically, whether filtering should apply to what is reported (e.g., by service location or adaptation set) or where reports are sent. The group noted ambiguity in the current specification and debated whether reporting should be differentiated by service location, adaptation set, or request type. Thasso and Daniel highlighted that most clients aggregate throughput across all service locations, not per-location, and that excessive granularity could complicate implementations.
  • Use Cases and Implementation: The team discussed the practical implications of reporting configuration, including the need for clear guidelines on what clients should report and how to avoid unnecessary data flooding to CDNs. There was consensus that the specification should clarify these behaviors to ensure interoperability and efficiency.
  • Next Steps:
    • Nicolas, Daniel, and Thasso will continue refining the configuration model and clarify the intended filtering and reporting logic.
    • The group will review the CMCDv2 guidelines and use cases to ensure the Dash integration aligns with best practices.
    • The topic will be revisited in the next session, with the possibility of a dedicated meeting to finalize the approach and resolve outstanding ambiguities.

Thasso’s presentation on SGAI

Summary of Thasso’s Presentation: Slide-by-Slide Overview

  • Introduction & Use Cases
    • Thasso introduced alternative MPD events in DASH 6th edition, aligning with HLS interstitials, and explained two main modes: insert (extends user timeline) and replace (keeps timeline unchanged). Use cases include ad insertion and alternative content playback. 1
  • Insert Presentation Event
    • Explained how insert events work: branching out to alternative MPD (e.g., ad), then returning to main content. Point events (duration 0) trigger only when played linearly; duration events allow seeking into the ad slot. 2
  • Comparison with HLS
    • Highlighted semantic differences: DASH event duration marks execution window, while HLS date range duration refers to ad duration. 3
  • Event Re-triggering & Attributes
    • Discussed event re-triggering on seek, and attributes controlling ad execution frequency. 4
  • Earliest Resolution Time Offset
    • Introduced this attribute to allow clients to pre-fetch alternative MPDs within a time window, mainly to avoid request peaks and support ad server preparation. Discussed randomization within the window to avoid simultaneous requests. 5
  • Max Duration Attribute
    • Explained how max duration can cap ad playback, ensuring the player returns to main content after a set time, regardless of ad length. 6
  • Event Duration & Timeline
    • Clarified that event duration is on the main timeline, not ad duration, and discussed implications for seeking and execution. 7
  • Use Cases for Nonzero Duration
    • Explored scenarios for nonzero duration insert events, such as mid-roll ads triggered by seeking, and pre-rolls for both VOD and live. 8
  • Additional Attributes
    • Covered execute once (limits event execution), no jump (controls skipping behavior), and skip after (enables ad skipping after a set time). 9
  • Ad Pods & List MPD
    • Presented the list MPD type for ad pods (multiple ads in sequence), with imported static MPDs for each ad. Discussed handling mismatched durations and the precedence of period times over content times. 10
  • Handling Gaps & Timeline Integrity
    • Addressed what happens if imported MPD is shorter than period duration, emphasizing that period times control playback and gaps are managed by the client (e.g., black frames or timeline adjustment). 11
  • Return Offset & Replace Events
    • Explained replace events: after ad playback, return to a specific offset on the main timeline. Attributes like return offset and clip control alignment and playback duration. 12
  • DVR Window & Pausing
    • Discussed implications for live playback, such as falling out of the DVR window if paused during ad playback, and client behavior in such cases. 13
  • Start with Offset
    • Introduced start with offset attribute for replace events, allowing playback to start in the middle of an ad if tuning in late, mirroring some HLS implementations. 14
  • Request Param (Annex I)
    • Showed how request param enables forwarding query parameters (e.g., user ID) from main manifest to ad requests, supporting static manifests with user/session-specific data. 15
  • Dynamic Ad Decisioning
    • Demonstrated using request param to inform ad server of remaining ad slot time, enabling dynamic ad selection or skipping if insufficient time remains. 16
  • Event Updates
    • Presented event updates, allowing events to be modified (e.g., aborting ad playback by setting max duration to zero), supporting dynamic scenarios like aborting ads or shifting event timing. 17
  • Implementation & Normative Details
    • Discussed implementation details, such as matching event updates by ID and the importance of status for normative compliance. 18
  • Closing
    • Thasso concluded the presentation and offered to share slides. 19

 

Explicit Overview of Functionalities Discussed

  • Alternative MPD Events (Insert & Replace):
    • Insert events allow branching out from main content to play alternative content (e.g., ads), extending the user timeline; replace events swap a segment of the main timeline with alternative content without extending the timeline. 1
    • Both modes support point-in-time (duration 0) and range-based (nonzero duration) triggers, affecting how seeking and event execution behave. 2
    • Insert events can be configured with a duration to allow seeking into the event window, while replace events align playback with the main timeline. 3
  • Earliest Resolution Time Offset:
    • Defines a window before the event when clients may prefetch alternative MPDs, helping to avoid request peaks and allowing backend ad preparation. 4
    • Clients can randomize request timing within this window to distribute load. 5
  • Max Duration & Clipping:
    • Max duration attribute caps how long alternative content can play, ensuring return to main content even if the ad is longer. 6
    • The “clip” property determines whether to strictly enforce event duration or allow the ad to play fully, even if it slightly overruns. 7
  • Execute Once & No Jump:
    • Execute once limits how many times an event is triggered per session. 8
    • No jump (with options like execute all/last) controls ad playback when users seek over events, ensuring required ads are played. 9
  • Skip After:
    • Allows specifying when a skip button becomes available during ad playback, either for entire pods or individual ads. 10
  • List MPD (Ad Pods):
    • Supports grouping multiple static ads into a pod, with each ad as a single-period MPD; period durations can be set, and gaps are handled per DASH rules. 11
    • Only static, single-period MPDs are allowed as imports. 12
  • Request Param (NXI):
    • Enables forwarding query parameters from the main MPD to alternative MPDs, supporting user/session-specific ad requests without manifest manipulation. 13
  • Event Updates:
    • Events can be updated (e.g., to abort an ad or shift timing), with status updates ensuring clients recognize and process changes. 14
  • Start With Offset:
    • Determines whether playback of an ad starts at the beginning or at the seeked offset when tuning into an event mid-way. 15
  • Implementation Guidance:
    • The group is preparing documentation with use cases, XML snippets, diagrams, HLS equivalence, and implementation notes to support adoption. 16

Real-world use cases discussed for each functionality

Insert Presentation Event

  • Used for inserting alternative content such as advertisements into the main content timeline, extending the user’s timeline by the ad duration. Real-world use cases include mid-roll ads in VOD, where seeking into a defined range triggers ad playback, and scenarios where business logic requires users to watch a mid-roll ad upon seeking near the end of content. Pre-rolls are also possible but not recommended as the primary method. 1
  • In live streaming, insert events can be used to insert ads at specific points, with mechanisms to pre-announce ad slots and manage ad server preparation time. 2

Replace Presentation Event

  • Used to replace a segment of the main content with alternative content (e.g., an ad), keeping the overall timeline unchanged. This is relevant for live streams where the user remains on the live edge, and for cases where the ad duration may slightly differ from the slot, with options to clip or allow slight overruns. 3
  • Supports scenarios where tuning in during an ad break should start playback at the corresponding offset within the ad, aligning with some HLS player behaviors. 4

List MPD (Ad Pods)

  • Enables serving multiple consecutive ads (ad pods) by importing a list of static MPDs, each representing an ad. Used when an ad server decides to fill a slot with multiple ads, as in broadcast TV ad pods or digital ad breaks. 5
  • Handles cases where ad durations may not perfectly match the slot, with the player responsible for managing gaps or truncation. 6

Earliest Resolution Time Offset

  • Allows clients to prefetch ad content ahead of the event trigger, mainly to avoid request peaks and give ad servers time for bidding, transcoding, and packaging. Especially relevant for live events with dynamic ad decisioning. 7

Execute Once, No Jump, Skip After

  • Execute Once: Ensures an ad is only played once per user session, even if the user seeks back into the event range. 8
  • No Jump/Execute All/Execute Last: Controls ad playback when users seek over multiple ad events, ensuring required ads are played even if skipped over. 9
  • Skip After: Allows users to skip ads after a defined time, supporting user-friendly ad experiences similar to those on major streaming platforms. 10

Request Parameters (NXI)

  • Forwards user/session-specific parameters from the main manifest to ad requests, enabling static manifests while supporting personalized ad delivery and beaconing. Used for user-specific ad targeting and analytics. 11

Event Updates

  • Allows dynamic updates to scheduled events, such as aborting an ad if something changes on the main stream, or shifting ad events to optimize cache prefetching in low-latency live scenarios. 12

 

Meeting Summary

Key Topics:

  • Introduction: Thomas, Silhavy, Alan, Bertrand, David, Davide, Stefan, Daniel, and Tasso participated in the meeting to discuss various topics including server-guided ad insertion, C2PA authentication, and planning for 2026. 1
  • Server-Guided Ad Insertion: Thomas and Tasso discussed the implementation of server-guided ad insertion in DASH, focusing on the use of insert and replace presentation events. They reviewed the current status, including the need for a detailed guideline document and the importance of handling live content and ad insertion scenarios. 2
  • C2PA Authentication: Iraj presented the current status of C2PA authentication in DASH workflows, highlighting the need for a joint meeting with C2PA to discuss updates and integration. The discussion covered the workflow interfaces, the role of the authentication verifier, and the importance of secure pipelines on both the client and server sides. 3
  • Implementation and Testing: Daniel and Tasso discussed the implementation of the two-player model in DASH.js for ad insertion, noting that the pull request is open but not yet merged. They also highlighted the need for further testing and validation, particularly for live content scenarios. 4
  • Planning and Scheduling: Thomas proposed scheduling additional meetings to focus on specific topics, including server-guided ad insertion and C2PA authentication. The group agreed to meet next week to create a template for documenting use cases and to continue discussions on these topics. 5

Action Items:

Server-Guided Ad Insertion:

  • Send the updated slides and document to Thomas for inclusion in the guideline document. (Thasso Griebel (Castlabs)) 6

C2PA Authentication:

  • Reach out to the C2PA team to schedule a joint meeting to discuss updates and integration. (Thomas) 7

Implementation and Testing:

  • Review and merge the pull request for the two-player model in DASH.js. (Daniel) 4

Planning and Scheduling:

  • Send out an invite for the next meeting to create a template for documenting use cases. (Thomas) 8

Details on Media Authentication

AI-generated content. Be sure to check for accuracy.

Media Authentication (C2PA) Discussion Summary

  • Status & Workflow Overview
    • Iraj presented the current status: a guideline template exists for deploying C2PA in DASH workflows, but it mainly outlines structure and needs more detail, especially on workflow interfaces and live use cases. 1
    • The workflow covers content creation, editing, encoding, manifest generation, and the need for authentication/verification at each stage. Special attention was given to how manifest manipulations (e.g., ad insertions, alternative MPDs) impact verification on the client and what restrictions or signaling are needed. 2
    • The group noted that C2PA did not originally consider the complexities of manifest manipulation in streaming, which is critical for DASH. 2
  • Technical Challenges & Open Questions
    • Discussion focused on how the DASH client (e.g., dash.js) should interact with C2PA: whether it only exposes segment data or also integrates the validator module, and how to handle timing and interface details. 3
    • Daniel and Mohammed clarified that dash.js can expose all network-fetched segments to the application, which can then pass them to the C2PA validator (currently a WebAssembly module). 4
    • Tasso and others highlighted that for secure validation, the validator should ideally be implemented in a secure/native environment, similar to EME, to prevent tampering and ensure the validated content matches playback. 5
    • There was debate about the need for explicit signaling in the MPD to indicate which adaptation sets or periods are subject to authentication, and whether a CPX-like interface is needed for exchanging certificates/keys. 6
    • Mohammed and Iraj discussed that, for C2PA, if a segment lacks the relevant box, the validator simply skips it; explicit signaling may be needed for discovery/selection but not for validation itself. 7
    • The group agreed that all segments should be forwarded to the validator for security, and that the validator should handle cases where no authentication data is present. 8
  • Strategic Considerations
    • The group discussed the need for a Media Authentication Extension (MAE), analogous to EME, to standardize the interface between DASH clients and authentication modules, with the goal of eventually proposing this to W3C. 9
    • There was consensus that the content protection security group (CPS) should be involved, especially regarding a CPX-like interface for certificate/key exchange, but only after the workflow and requirements are clearer. 10
    • The group recognized that C2PA is the primary focus, but the framework should be extensible to other authentication systems. 11
  • Next Actions
    • Thomas will reach out to the C2PA group to arrange a joint meeting for updates and to discuss integration points, aiming for early next year. 12
    • The team will refine the architecture, clarify interfaces (especially MAE and a CPX-like exchange), and involve the content protection security group as requirements solidify. 13
    • Work will continue on drafting the guidelines, focusing on concrete use cases, workflow details, and technical requirements, with regular dedicated calls proposed to accelerate progress. 14

 

Upcoming Meeting Scheduling Agreements

  • A dedicated call will be organized for L3D and low latency small MPDs, with Bertrand and Alex confirming their availability for the next week. 1
  • The test tool meeting will be extended to 90 minutes and will include SGIA topics; the start time will be shifted earlier to accommodate participants. 2
  • Weekly calls related to DRM and MPEG/DVB will be held on Wednesdays, starting half an hour earlier than before, and extended to 90 minutes. 3
  • The regular IOP call will resume after the holiday break, with the next session planned for early January, avoiding national holidays. 4
  • The December 23 meeting is canceled due to low expected attendance; the year-end wrap-up will occur in the first IOP call of the new year. 5
  • A call will be scheduled with C2PA representatives as soon as possible, potentially before the next MPEG meeting, to discuss integration and guidelines. 6

 

Have A Question ABout Membership?

Schedule A Meeting

[hfcm id="18"]

Send An Email

Don’t want to schedule a face-to-face meeting just now? No problem. Simply send your membership question to info@streamingvideoalliance.org or fill out the form below and someone will get back to you as soon as possible.