Skip to content

Commit 9aa095e

Browse files
kixelatedclaude
kixelated
and
claude
authored
Add draft-lcurley-moq-largest-group extension (#19)
* Add draft-lcurley-moq-largest-group extension Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Refine joining fetch workaround section Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Combine complexity and split delivery bullet points Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent dfeff06 commit 9aa095e

1 file changed

Lines changed: 140 additions & 0 deletions

File tree

‎draft-lcurley-moq-largest-group.md‎

Lines changed: 140 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,140 @@
1+
---
2+
title: "MoQ Largest Group Extension"
3+
abbrev: "moq-largest-group"
4+
category: info
5+
6+
docname: draft-lcurley-moq-largest-group-latest
7+
submissiontype: IETF # also: "independent", "editorial", "IAB", or "IRTF"
8+
number:
9+
date:
10+
v: 3
11+
area: wit
12+
workgroup: moq
13+
14+
author:
15+
-
16+
fullname: Luke Curley
17+
email: kixelated@gmail.com
18+
19+
normative:
20+
moqt: I-D.ietf-moq-transport
21+
22+
informative:
23+
24+
--- abstract
25+
26+
This document defines a Largest Group subscription filter type for MoQ Transport {{moqt}}.
27+
A subscriber uses this filter to request delivery starting from the first object of the publisher's largest (most recent) group, ensuring a complete group is received.
28+
29+
--- middle
30+
31+
# Conventions and Definitions
32+
{::boilerplate bcp14-tagged}
33+
34+
35+
# Introduction
36+
{{moqt}} Section 5.1.2 defines four subscription filter types that control where delivery begins:
37+
38+
- **Next Group Start (0x1)**: Starts at `{Largest.Group + 1, 0}`, skipping the remainder of the current group entirely.
39+
- **Largest Object (0x2)**: Despite the name, starts at `{Largest.Group, Largest.Object + 1}` — the object *after* the largest, not the largest object itself.
40+
- **AbsoluteStart (0x3)**: Starts at an explicit location specified by the subscriber.
41+
- **AbsoluteRange (0x4)**: Starts and ends at explicit locations specified by the subscriber.
42+
43+
There is no filter that starts from the *beginning* of the current group.
44+
Next Group Start skips the current group entirely, potentially adding latency equal to the group duration.
45+
Largest Object starts mid-group, delivering objects that may depend on earlier objects in the same group.
46+
47+
Objects within a group are typically delta encoded (ex. video GOPs), so arbitrary objects in the middle of a group are undecodable without prior objects.
48+
A subscriber using Next Group Start avoids this problem but must wait for the next group to begin, unnecessarily increasing join latency.
49+
50+
## Joining Fetch Workaround
51+
{{moqt}} does provide a workaround: a subscriber can issue a separate "joining" FETCH request alongside a SUBSCRIBE to retrieve the beginning of the current group.
52+
However, this approach has several drawbacks:
53+
54+
- **Complexity**: Libraries emulate Largest Group by coordinating a FETCH and SUBSCRIBE, splitting the group across multiple streams. This requires merging the results into a single coherent group and handling various edge cases, such as one of the two requests failing independently.
55+
- **Head-of-line blocking**: If the group contains multiple sub-groups, the FETCH delivers them sequentially over a single stream, introducing head-of-line blocking that negates the benefits of sub-group parallelism.
56+
- **Priority**: Everything should be delivered in dependency order to improve startup time and avoid potential flow control deadlocks. This requires prioritizing the FETCH higher than the SUBSCRIBE, which may be non-obvious or unsupported.
57+
58+
This extension avoids these issues by defining a Largest Group filter that starts delivery from the first object of the publisher's most recent group within the SUBSCRIBE itself, ensuring a complete group is delivered over the normal subscription path.
59+
Additionally, the first group of a subscription behaves the same as any other group.
60+
61+
62+
# Setup Negotiation
63+
The Largest Group extension is negotiated during the SETUP exchange as defined in {{moqt}} Section 9.4.
64+
65+
Both endpoints indicate support by including the following Setup Option:
66+
67+
~~~
68+
LARGEST_GROUP Setup Option {
69+
Option Key (vi64) = TBD1
70+
Option Value Length (vi64) = 0
71+
}
72+
~~~
73+
74+
If both endpoints include this option, the Largest Group filter is available for the session.
75+
If a peer receives a SUBSCRIBE containing the Largest Group filter without having negotiated the extension, it MUST close the session with a PROTOCOL_VIOLATION.
76+
77+
78+
# Largest Group Filter
79+
This document defines a new subscription filter type for use in the Subscription Filter field of SUBSCRIBE messages as defined in {{moqt}} Section 5.1.2.
80+
81+
## Filter Type
82+
83+
~~~
84+
Subscription Filter {
85+
Filter Type (vi64) = 0x20
86+
}
87+
~~~
88+
89+
The Largest Group filter uses Filter Type value `0x20`.
90+
No additional fields (Start Location or End Group Delta) are present in the Subscription Filter.
91+
92+
## Semantics
93+
When the publisher receives a SUBSCRIBE with the Largest Group filter, it computes the start location as:
94+
95+
~~~
96+
{Largest.Group, 0}
97+
~~~
98+
99+
Where `Largest.Group` is the group sequence number of the largest object known to the publisher at the time the SUBSCRIBE is processed.
100+
Delivery begins from the first object (object 0) of that group.
101+
102+
The subscription is open-ended: the publisher continues delivering subsequent groups until the subscription is cancelled or the session ends.
103+
This is consistent with the behavior of Next Group Start and Largest Object filters.
104+
105+
The largest group is delivered using normal SUBSCRIBE semantics.
106+
If earlier objects in the group have been evicted from the cache, the publisher MAY attempt to repopulate the cache or simply drop the group as it would for any other subscription.
107+
108+
109+
# Security Considerations
110+
This extension introduces no new security considerations beyond those described in {{moqt}}.
111+
The publisher already tracks group state; this filter uses existing state to compute the start location.
112+
113+
114+
# IANA Considerations
115+
116+
This document requests the following registrations:
117+
118+
## MoQ Setup Option Types
119+
120+
This document registers the following entry in the "MoQ Setup Option Types" registry established by {{moqt}}:
121+
122+
| Value | Name | Reference |
123+
|:------|:-----|:----------|
124+
| TBD1 | LARGEST_GROUP | This Document |
125+
126+
## MoQ Subscription Filter Types
127+
128+
This document registers the following entry in the "MoQ Subscription Filter Types" registry established by {{moqt}}:
129+
130+
| Value | Name | Reference |
131+
|:------|:-----|:----------|
132+
| 0x20 | LARGEST_GROUP | This Document |
133+
134+
135+
--- back
136+
137+
# Acknowledgments
138+
{:numbered="false"}
139+
140+
This document was drafted with the assistance of Claude, an AI assistant by Anthropic.

0 commit comments

Comments
 (0)