Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
28 commits
Select commit Hold shift + click to select a range
0a52b90
quest: claim m1/ietf-extension/lite
kixelated Oct 20, 2026
c09f61d
wip(lite): ietf extension carries moq-transport state across lite-07
kixelated Oct 20, 2026
5027bc9
wip(lite): ietf extension carries moq-transport state across lite-07
kixelated Oct 20, 2026
eda446c
wip(lite): ietf extension carries moq-transport state across lite-07
kixelated Oct 20, 2026
d3ed5fa
Merge remote-tracking branch 'origin/main' into quest/m1/ietf-extensi…
kixelated Oct 20, 2026
de33aa7
feat(lite): ietf extension carries moq-transport state between relays
kixelated Oct 20, 2026
07ae45b
quest: retire ietf-extension/lite with its PR
kixelated Oct 20, 2026
4574e36
fix(lite): bound ietf records and TRACK_PROPERTIES by what moq-transp…
kixelated Oct 20, 2026
b0c3bae
fix(net): carry relayed object properties as their encoded block
kixelated Oct 20, 2026
5fbe5d3
test(ietf): compare every FETCH_OK field across the lite hop
kixelated Oct 20, 2026
2426c90
fix(lite): relayed records agree with their frame and their Group State
kixelated Oct 20, 2026
8d5d018
fix(net): a timed object's time lives only in its frame
kixelated Oct 20, 2026
69c9fd7
fix(net): reserve egress headroom at ingress for relayed properties
kixelated Oct 20, 2026
d3d6297
fix(lite): track properties cross in the encoding they arrived in
kixelated Oct 20, 2026
aba8f9b
fix(net): a sealed understood property must match the track info
kixelated Oct 20, 2026
2ad4ae2
fix(lite): refuse undefined datagram statuses and the END record past…
kixelated Oct 20, 2026
7f8369c
fix(net): a status object keeps its timestamp; datagram shapes match …
kixelated Oct 20, 2026
8d17231
fix(lite): a datagram with a STATUS field carries no payload
kixelated Oct 20, 2026
5048ea2
fix(net): a sealed group order is advisory
kixelated Oct 20, 2026
4bbadbc
fix(lite): a block must claim a draft that could send it
kixelated Oct 20, 2026
a5f85e6
feat(lite): name each property encoding by its drafts, without flags
kixelated Oct 20, 2026
3d8398a
fix(net): bound a block's Timestamp headroom once it has a frame
kixelated Oct 20, 2026
1a4a469
Merge remote-tracking branch 'origin/main' into ietf-lite-ready
kixelated Oct 20, 2026
d07c3ff
fix(lite): forward a sealed DYNAMIC_GROUPS across the hop
kixelated Oct 20, 2026
298f8e8
Merge remote-tracking branch 'origin/main' into ietf-lite-merge
kixelated Oct 20, 2026
9408626
fix(lite): refuse a draft-14 block whose IDs descend
kixelated Oct 20, 2026
5aea682
fix(lite): compare a sealed DYNAMIC_GROUPS across the hop
kixelated Oct 20, 2026
d6942e6
quest(m1): keep the ietf hop quest for ingress-version provenance
kixelated Oct 20, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions doc/bin/relay/cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,12 @@ namespace prefix is illegal before draft 16), so a link to a peer without the
MoQ Solicit extension, such as moxygen, learns only what that peer announces
unasked. moxygen announces nothing unasked on draft 14.

A track from a moq-transport publisher keeps its Object IDs, object properties,
and END\_OF\_GROUP status objects across a moq-lite-07 link, since relays
always offer the [ietf extension](/draft/moq-ietf) that carries them. Over an
older moq-lite link they are lost: a moq-transport subscriber behind it sees
consecutive objects with no properties.

When a moq-lite-04 or later peer withdraws a broadcast, the routes relayed
through it go with it at once. A change of best route is announced after
300 ms, so stale paths are retracted once instead of advertised in turn;
Expand Down
1 change: 1 addition & 0 deletions doc/bin/relay/config.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,7 @@ bind = "/run/moq/internal.sock"
allow.uid = [1001]

[listen.extensions] # moq-transport SETUP extensions to offer, each on by default.
# The relay always offers ietf, for moq-lite-07 relay links.
auth = false # Decline MoQ Auth (draft 17+).
solicit = false # Decline MoQ Solicit, so peers may announce unasked.
epoch = false # Decline MoQ Epoch, so routes over moq-transport carry no epoch (draft 17+).
Expand Down
7 changes: 6 additions & 1 deletion doc/concept/standard.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ subset drops. What a peer actually observes against this implementation:
- **Strict SETUP and parameters.** Repeated unknown `SETUP` options, GREASE included, are accepted if well-formed; a repeated known option is rejected. On draft 17 and later, a `GROUP_ORDER` other than Ascending (1) or Descending (2) closes the session. Message parameters follow the negotiated draft's lists: drafts 14 and 15 ignore an unknown or misplaced parameter, draft 16 ignores one defined only for another message but closes the session on an unknown one, and draft 17 and later close it on both. Other malformed control input closes the session with the draft's code too, such as a server `SETUP` carrying `PATH` or `AUTHORITY`, a request cut short by FIN, or a second `GOAWAY` on one stream; a first `GOAWAY` on a request stream is legal.
- **One `SETUP` credential**, forwarded to the [auth server](/bin/relay/auth#the-contract) unverified. A second `SETUP` token closes the session. We advertise no token cache, so an alias reference in `SETUP` closes it with `PROTOCOL_VIOLATION`, one on a request with `UNKNOWN_AUTH_TOKEN_ALIAS`, and a registration on a request with `AUTH_TOKEN_CACHE_OVERFLOW`. Where the Rust side authorizes the peer or verifies tokens, a token on a `SUBSCRIBE` or `PUBLISH_NAMESPACE` is verified like an in-band session token and authorizes that one request alone, even where that authorization already covers it; it never widens the session. It is refused with `NOT_SUPPORTED` when nothing verifies it, when it is empty, or when its Token Type is anything but 0 (out of band). A side that does neither, JavaScript included, ignores the token. Rust refuses a request carrying more than one distinct token with `NOT_SUPPORTED`, since it verifies one; JavaScript, which verifies none, ignores them all. A token-authorized `SUBSCRIBE` still stays within the grant the peer gave us. A token-authorized `PUBLISH_NAMESPACE` needs a grant covering everything beneath the namespace, and the tracks we subscribe under it rely on that announce instead of our limit, ending with it. An update renews the token, except on a drafts 14 and 15 `PUBLISH_NAMESPACE`, which has no update, and a refused renewal ends only that request. Rust and JavaScript send the token a route names (`Route::auth`) on its `PUBLISH_NAMESPACE`, including the one drafts 14 and 15 answer a solicited `SUBSCRIBE_NAMESPACE` with, and swapping it renews the request with `REQUEST_UPDATE` from draft 16, or ends and re-sends it before; the inline `NAMESPACE` that answers a solicited `SUBSCRIBE_NAMESPACE` from draft 16 carries no token. The token belongs to the session that added it, so a reconnect means adding it again and re-announcing. A token on any other request is decoded and grants nothing, and a request repeating one is refused with `MALFORMED_AUTH_TOKEN`. `SUBSCRIBE_TRACKS` reads its namespace before refusal; its token is not decoded. On draft 17 and later, the negotiated [MoQ Auth extension](/concept/moq-lite#authorization) accepts additional session tokens in band.
- **Refused, not fatal.** A legal request this stack does not serve is rejected on its own and the session stays up: `FORWARD=0`, `SUBSCRIBE_TRACKS`, and the fetch forms above get `NOT_SUPPORTED`. Range Filters get `INVALID_FILTER` on draft 19 and later because the advertised filter limit is zero. On draft 21 and later, namespaces whose first tuple field is exactly `.` or `.session` get `DOES_NOT_EXIST` before application lookup; other dot prefixes still reach the application. Subscription updates accept priority, negotiated subscriber max age, and delivery timeouts; Rust also renews request tokens and judges `NEW_GROUP_REQUEST` as a join (see dynamic groups below). Other supported-but-unimplemented preferences end that subscription; a `TRACK_PROPERTY_FILTER` there closes the session with `PROTOCOL_VIOLATION`, since it belongs only to `SUBSCRIBE_TRACKS`. On draft 18 and later a namespace update may change its prefix; suffixes after the acknowledgement are relative to that new prefix.
- **Objects and datagrams.** Only subgroup 0 is accepted: a stream for any other subgroup, whether its header gives the ID or takes it from the first Object ID, is stopped and the session stays up. Rust relays preserve Object IDs, gaps, object properties, FIRST\_OBJECT, and END\_OF\_GROUP status objects between moq-transport peers for subgroup 0. Datagrams retain their IDs, properties, priority, and status. Plain Rust readers and moq-lite peers see consecutive frames and normal datagram payloads; JavaScript supports only normal datagrams at Object ID 0. A malformed datagram closes the session; a relayed one the downstream draft cannot carry is dropped. A relayed Timestamp leaves in the units the downstream response declares, and is dropped where it declares none (drafts 14 through 16), as for a plain frame; an immutable one that would change or vanish is refused. Only property 0x10 is read as a Timestamp. Property 0x06 stays opaque and keeps its value regardless of timestamp units; it is dropped across the draft-19 boundary, or refused when immutable, because draft 19 assigns it to SUBGROUP\_DELIVERY\_TIMEOUT. From draft 15, a status object carrying properties is refused, and one relayed from draft 14 leaves without them. Draft 14 allows them, but an END\_OF\_TRACK carrying properties ends the subscription as unsupported, since a track end has nowhere to keep them. A `FETCH` carries the END\_OF\_GROUP object on drafts 14 and 15; later drafts have no FETCH status, so their response ends at the last frame. A group cannot resume across route changes by frame ordinal once Object IDs skip ahead of the ordinals on either route; recovery refuses it instead of splicing different objects.
- **Objects and datagrams.** Only subgroup 0 is accepted: a stream for any other subgroup, whether its header gives the ID or takes it from the first Object ID, is stopped and the session stays up. Rust relays preserve Object IDs, gaps, object properties, FIRST\_OBJECT, and END\_OF\_GROUP status objects between moq-transport peers for subgroup 0, including across a moq-lite-07 hop between two relays that negotiate the [ietf](/draft/moq-ietf) extension. Datagrams retain their IDs, properties, priority, and status. Plain Rust readers and moq-lite peers see consecutive frames and normal datagram payloads; JavaScript supports only normal datagrams at Object ID 0. A malformed datagram closes the session; a relayed one the downstream draft cannot carry is dropped. A relayed Timestamp leaves in the units the downstream response declares, and is dropped where it declares none (drafts 14 through 16), as for a plain frame; an immutable one that would change or vanish is refused. On a timed track the frame holds each object's time, so a mutable Timestamp that only repeats the immutable one is not restated; a status object has no frame, so it keeps its Timestamp among its properties. Only property 0x10 is read as a Timestamp. Property 0x06 stays opaque and keeps its value regardless of timestamp units; it is dropped across the draft-19 boundary, or refused when immutable, because draft 19 assigns it to SUBGROUP\_DELIVERY\_TIMEOUT. From draft 15, a status object carrying properties is refused, and one relayed from draft 14 leaves without them. Draft 14 allows them, but an END\_OF\_TRACK carrying properties ends the subscription as unsupported, since a track end has nowhere to keep them. A `FETCH` carries the END\_OF\_GROUP object on drafts 14 and 15; later drafts have no FETCH status, so their response ends at the last frame. A group cannot resume across route changes by frame ordinal once Object IDs skip ahead of the ordinals on either route; recovery refuses it instead of splicing different objects.
- **Dynamic groups.** A track advertises `DYNAMIC_GROUPS` when its publisher sets a refresh ratio, and a track received with `DYNAMIC_GROUPS` gets a ratio of 0. A `NEW_GROUP_REQUEST` (draft 15 and later) counts as one more subscriber joining, which a `SUBSCRIBE` already is: it asks for a new group only when the newest group's bytes after its first frame exceed the ratio times the first frame. Joins coalesce until the asked-for group arrives. A Rust relay sends `NEW_GROUP_REQUEST` upstream, on the `SUBSCRIBE` or in a `REQUEST_UPDATE`, once a join wants a group past the newest it holds; a relay holding nothing yet asks for none. On a track without a ratio, an update carrying one ends the subscription with `UPDATE_FAILED`. On drafts 15 and 16, whose `TRACK_STATUS` answer has no room for it, a relay copy first learned from `TRACK_STATUS` (a fetch-only reader) does not advertise it to later subscribers. A moq-lite-07 hop (`moq-lite-07-wip`, opt-in) carries the same demand natively: the ratio in `TRACK_INFO` and the asked-for group in `SUBSCRIBE_UPDATE`. Earlier moq-lite versions carry neither, so a track received over one never refreshes.
- **Priority.** Higher is served first. The IETF default of 128 is this stack's 127, and a track that never sets one is 127. A relay's upstream subscription carries the highest priority its subscribers ask for and updates it as they come and go; its group order stays as the `SUBSCRIBE` asked, since no draft lets an update change it.
- **Size.** An object extension block larger than 64 KiB ends that subgroup stream. The session stays up. This cap is ours, not the draft's.
Expand All @@ -51,6 +51,11 @@ its `peek()` or `changed()` methods; session statistics do not request PROBE.
Both libraries offer solicit, auth, and epoch (draft 17 and later) unless a side's
`extensions` setting declines one, which connects it as a peer that does not
speak that extension. The pooled JavaScript `Connection` has no such setting yet.
[ietf](/draft/moq-ietf) goes the other way: it extends moq-lite-07 to carry this
object state between relays. moq-lite-07 is still a work in progress
(`moq-lite-07-wip`), negotiated only when both sides enable it, so a peer that
does not offer it does not carry this state. Only Rust offers the extension, when
`extensions.ietf` is set, and `moq-relay` always does on moq-lite-07.
[moq-e2ee](/draft/moq-e2ee) is not a transport extension. It encrypts
application payloads, so relays still forward named tracks they cannot read.
See [Encryption](/concept/hang#encryption).
Expand Down
Loading
Loading