IETF MOQ WG: New draft: Conditional Range Filters for MOQT

Message Snapshot

• List: moq@ietf.org
• Thread subject: New draft: Conditional Range Filters for MOQT
• Message subject: [Moq] New draft: Conditional Range Filters for MOQT
• Author: Yu You (Nokia)
• Published: 2026-08-18T07:40:37.000Z
• Source tag: ietf-mailing-list
• Message URL: Open in IETF Mail Archive

Summary

Yu You (Nokia) posted to the MOQ working group mailing list on August 18, 2026. Hi all, We would like to request comments on a new draft: "Conditional Range Filters for Media over QUIC Transport". Link: https://datatrac…

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 would like to request comments on a new draft: "Conditional Range Filters for Media over QUIC Transport". Link: https://datatracker.ietf.org/doc/draft-yuyou-conditional-filtering/

Plain-Text Body

Hi all,

We would like to request comments on a new draft: "Conditional Range Filters for Media over QUIC Transport".

Link: https://datatracker.ietf.org/doc/draft-yuyou-conditional-filtering/

TL;DR

Currently, MOQT Range Filters are static. Any change to a filter requires a REQUEST_UPDATE round trip, which introduces reaction delays during network congestion. We propose a new RANGE_FILTER_CONDITION parameter that binds a Range Filter SetID to autonomous relay-side evaluation logic.

This allows a relay to dynamically activate or deactivate specific filter sets at group boundaries based on real-time metrics (like throughput thresholds) without requiring further signaling from the subscriber.

Key Technical Points

Compatibility with Range Filter Sets: This proposal is designed to be fully compatible with existing MOQT SetID-based Range Filters. The conditional logic determines only whether a specific SetID participates in the established OR-combination at a given switching point. This preserves the core AND/OR semantics of the base protocol, allowing conditional and unconditional filter sets to coexist naturally within a single subscription.

• Explicit Signaling of Omissions: To help subscribers distinguish between network loss and intentional filtering, the draft introduces a new PRIOR_SUBGROUP_ID_GAP Object Property. This allows the relay to signal when subgroups have been skipped due to active filter conditions.
• Alignment with SSTS: The condition model intentionally reuses the design from Sender-Side Track Switching (SSTS). It applies the same threshold/weight/rank semantics and bandwidth allocation approach at the relay for intra-track filtering.

Implementation and Testing

To facilitate a better understanding of the proposal, we have implemented the conditional range filter feature in our MOQT V19 Relay server, including a simulated bandwidth API for testing.

Technical details and the API spec, plus a demo video can be found here: https://moqt.nokiaresearch.com:8080/static/open/range_filter_condition.html

Feedback is welcome on the list or via the GitHub issue tracker: https://github.com/yuyou/conditional_filtering.

Thanks,

Yu You