Minutes interim-2025-moq-26: Wed 16:00
minutes-interim-2025-moq-26-202509101600-00
| Meeting Minutes | Media Over QUIC (moq) WG Snapshot | |
|---|---|---|
| Date and time | 2025-09-10 16:00 | |
| Title | Minutes interim-2025-moq-26: Wed 16:00 | |
| State | Active | |
| Other versions | markdown | |
| Last updated | 2025-09-10 |
MoQ Virtual Interim 2025-09-10
Editor slides:
https://datatracker.ietf.org/meeting/interim-2025-moq-26/materials/slides-interim-2025-moq-26-sessa-moqt-prs-for-910-01
PR #949
(Slide 2,3)
- https://github.com/moq-wg/moq-transport/pull/949
-
Priority Not Present complexity worth saving a byte per group?
- Note: some datagram use cases may have 1 object per group
- Alan leans towards proposal b
- Martin has slight preference for the simpler to implement a
- Ye-Kui sees benefit of proposal b compression
-
Use a bit for Object ID=0?
- Suhas: consistency across SUBSCRIBE/FETCH is desireable
- Alan: FETCH is different enough we might not get true
consistency
- Alan: FETCH is different enough we might not get true
- Suhas: consistency across SUBSCRIBE/FETCH is desireable
Summary: 1 b and "no" on 2
PR 1159 consolidate errors (slide 4)
- https://github.com/moq-wg/moq-transport/pull/1159
- Ye Kui in favor
- Suhas to comment on PR
No objections voiced
(Note: this PR is about consolidation, not every error-code issue)
Issue 1182 proposal for REQUEST_OK (slide 5)
- https://github.com/moq-wg/moq-transport/issues/1182
- Looking for more feedback before PR
- general support voiced by a few people (Will, Ye Kui, Martin, ...)
- Suhas describes an alternative approach to consolidation
- question becomes about whether to reorder fields/params
Alan offers to make at least one, mayb two PRs in the next week or so:
- add this
- reordering
PR 1210 - Parameters for Group Order, Subscribe Priority and Subscription Filter (slide 6, 7, 8)
- https://github.com/moq-wg/moq-transport/pull/1210
- Slide 7 show target changes, next targets
-
Questions (slide 8):
1) Should relative Filter Types be allowed in PUBLISH_OK or
SUBSCRIBE_UPDATE (no way to get Largest back)?
2) You can’t change End without changing specifying Start; Is that
a problem?
3) Omitting Group Order is slightly funky
4) Do we feel good about leaving Forward “inline”?
5) Other candidates: Expires and Largest LocationDiscussion (40ish minute mark)
...Conclusions:
- please look at PR and leave comments, it closes a ton of issues
PR 1060 NEW_GROUP_REQUEST (slides 9,10)
- https://github.com/moq-wg/moq-transport/pull/1060
- DoS issues a concern
Mike to make slides for Toronto with alternative proposal, otherwise PR
seems close