IETF MOQ WG: New Version Published: Feedback draft
Yanmei Liu posted to the MOQ working group mailing list on August 3, 2026. Hi all, We have published a new version of the MoQ feedback draft: The draft was renamed from “MoQ Multimodal Feedback” to “MoQ Feedback”
Message Snapshot
- List:
moq@ietf.org - Thread subject: New Version Published: Feedback draft
- Message subject: [Moq] New Version Published: Feedback draft
- Author: Yanmei Liu
- Published: 2026-08-03T04:09:52.000Z
- Source tag:
ietf-mailing-list - Message URL: Open in IETF Mail Archive
Summary
Yanmei Liu posted to the MOQ working group mailing list on August 3, 2026. Hi all, We have published a new version of the MoQ feedback draft: The draft was renamed from “MoQ Multimodal Feedback” to “MoQ Feedback”
Why It Matters
This message came from the public MOQ working group archive and captures active discussion, meeting coordination, or implementation feedback around Media over QUIC.
Message Excerpt
Hi all, We have published a new version of the MoQ feedback draft: The draft was renamed from “MoQ Multimodal Feedback” to “MoQ Feedback”
Plain-Text Body
Hi all,
We have published a new version of the MoQ feedback draft:
https://datatracker.ietf.org/doc/draft-liu-moq-feedback/
The draft was renamed from “MoQ Multimodal Feedback” to “MoQ Feedback” because the mechanism is intended to support a broader range of use cases. In addition to multimodal transport for live-agent systems, it is also intended to support Relay-based architectures, live streaming, video conferencing, cloud rendering, and other interactive media applications.
The main updates in this version include:
- Motivation for using feedback to improve QoE and support source-rate adaptation in Relay-based deployments.
- Two Feedback Types: HOP_FEEDBACK, intended for the Adjacent Media Publisher, and ORIGIN_FEEDBACK, intended for the Media Original Publisher and able to traverse zero or more Relays.
- Rules for generating, establishing, binding, and forwarding Feedback Tracks across cascaded Relays.
- A Relay-visible MMF_FEEDBACK_TYPE Track Property and updated Feedback Track naming.
- Addition of Group ID to the report format so that media Objects are identified by the media Full Track Name, Group ID, and Object ID.
- Corresponding updates to the IANA considerations.
As a draft about feedback, it would naturally benefit from more feedback :)
We welcome comments on all aspects of the proposed mechanism, particularly regarding feedback semantics and Relay behavior in cascaded deployments.
Best regards, Yanmei Liu