Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
38 commits
Select commit Hold shift + click to select a range
6c0caa3
chore(quest): claim quest/m2/time-addressing/lite07.md
kixelated Nov 16, 2026
9183a6c
Merge commit '6c0caa357e' into worktree-agent-af21bd8081fa415bc
kixelated Nov 16, 2026
538ec28
Merge commit '6c0caa357e' into worktree-agent-acb87873da274e136
kixelated Nov 16, 2026
58cb48b
Merge commit '6c0caa357e' into worktree-agent-a018aa35b3cf08ad6
kixelated Nov 16, 2026
9f11f03
Merge commit '6c0caa357e' into worktree-agent-aff247ab10fda170d
kixelated Nov 16, 2026
19879a2
docs(drafts)!: lite-07 addresses groups by start
kixelated Nov 16, 2026
8808700
feat(lite)!: lite-07 drops the Padding stream and datagram
kixelated Nov 16, 2026
ca2c190
feat(lite)!: lite-07 SUBSCRIBE says no max age, one inclusive time an…
kixelated Nov 16, 2026
28c5f03
feat(net)!: lite-07 drops and skips carry a span, and stale drops are…
kixelated Nov 16, 2026
d262d4e
feat(net)!: a track listing carries each track's kind, so datagram tr…
kixelated Nov 16, 2026
b7731cc
Merge branch 'worktree-agent-a018aa35b3cf08ad6' into quest/m2/time-ad…
kixelated Nov 16, 2026
f77a102
feat(js/lite)!: lite-07 SUBSCRIBE says no max age, one inclusive time…
kixelated Nov 16, 2026
50d8627
feat(lite)!: a lite-07 datagram always carries its timestamp
kixelated Nov 16, 2026
e5b2859
feat(net)!: lite-07 drops and skips carry a span, and stale drops are…
kixelated Nov 16, 2026
ea6c785
Merge the JS mirror of lite-07 drop spans and final stale drops
kixelated Nov 16, 2026
f04b801
test(moq-net): a socket's out-of-order message arrives within the unl…
kixelated Nov 16, 2026
e24d105
Merge branch 'worktree-agent-acb87873da274e136' into quest/m2/time-ad…
kixelated Nov 16, 2026
8d59f74
docs(drafts): an aborted largest group has not ended
kixelated Nov 16, 2026
c301ab5
fix(net): JS records a stale drop under the narrowest budget asked
kixelated Nov 16, 2026
00af7b7
docs(skill): verify-subscribe describes final drops and records its runs
kixelated Nov 16, 2026
faafc2c
Merge branch 'worktree-agent-af21bd8081fa415bc' into quest/m2/time-ad…
kixelated Nov 16, 2026
6000543
Merge branch 'quest/m2/time-addressing/lite07' into worktree-agent-a7…
kixelated Nov 16, 2026
35cf2ca
feat(net)!: lite-07 GROUP carries Previous Start and groups end with …
kixelated Nov 16, 2026
199d610
feat(js/net)!: lite-07 GROUP carries Previous Start and groups end wi…
kixelated Nov 16, 2026
1570420
fix(net): a skipped group takes the run held back for its GROUP
kixelated Nov 16, 2026
1d85300
docs(verify): the subscription model closes expired streams and passe…
kixelated Nov 16, 2026
ba6a557
quest: lite-07 addresses groups by start is done
kixelated Nov 16, 2026
03d0b70
fix(js/net): a GROUP_END waiting for its FIN still ends with its group
kixelated Nov 16, 2026
ff1bb32
Merge origin/main into quest/m2/time-addressing/lite07
kixelated Nov 17, 2026
6210b17
chore(net): regenerate the JS API report for Group.Producer.finishAt
kixelated Nov 17, 2026
b10adfa
chore(verify): the subscribe model's sync commit moves to the main merge
kixelated Nov 17, 2026
bbf6c39
fix(net): a held skip outlives the cache forgetting it, and an expiry…
kixelated Nov 17, 2026
7091c0a
chore(verify): the subscribe model's sync commit moves past the held-…
kixelated Nov 17, 2026
097b2b6
fix(net): the test-only forget_drops builds only with async
kixelated Nov 17, 2026
79379ee
Merge origin/main into quest/m2/time-addressing/lite07
kixelated Nov 17, 2026
a4ed9aa
style(net): rustfmt the merged publisher
kixelated Nov 17, 2026
2d80a9d
chore(verify): the subscribe model's sync commit moves to the second …
kixelated Nov 17, 2026
8d83f77
Merge origin/main into quest/m2/time-addressing/lite07
kixelated Nov 17, 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
48 changes: 22 additions & 26 deletions .claude/skills/verify-subscribe/SKILL.md

Large diffs are not rendered by default.

21 changes: 16 additions & 5 deletions doc/concept/moq-lite.md
Original file line number Diff line number Diff line change
Expand Up @@ -298,7 +298,9 @@ Ranges are both a request and a filter. A subscriber reads only the groups its
own ranges cover, resolved again whenever it replaces them, even when another
subscriber of the same track asked for more. Widening them, including lowering
the start, also serves the cached groups they newly cover, never one already
served. A reader that has accounted for every group its bounded ranges cover
served or reported. A report is final: raising max delay afterwards does not
bring back a group reported `OLD`, though a relay whose own reader allows more
asks upstream for it again. A reader that has accounted for every group its bounded ranges cover
ends, and repeated reads end immediately too. Widening the ranges resumes reading.
A moq-lite-07 publisher ends a bounded subscription once it covered it, and the
copy stays cached for the same ranges until an update asks for groups it did not
Expand Down Expand Up @@ -328,6 +330,14 @@ upstream as that ID, where a start selects the first group at or after it
rather than the one containing it. moq-lite 01 and 02 carry no start, so every
subscription there starts at the live group.

A group ends one of three ways: finished at the time it ends, so it is whole;
closed, so every frame written arrives but it may have held more, as when a
relay stops sending a group that went stale; or aborted with an error. A
finished group's end also bounds how long it stays fresh, so the last group of
a paused track still ages out. Over the work-in-progress moq-lite 07 each group
also names the start of the group before it, so a reader sees a gap at once;
older versions and moq-transport carry neither the end nor the previous start.

Order only decides what goes first, never what is skipped, so catching up oldest
first needs a max delay that covers the backlog. When a relay serves subscribers of
both orders from one upstream subscription, it asks upstream for newest first, and
Expand All @@ -350,7 +360,7 @@ track is judged by the wall clock alone. Tracks from moq-lite before 05, or from
moq-transport without a `TIMESCALE`, arrive
untimed. moq-lite 05 and 06 cannot declare an untimed track, so there its
frames go out stamped with their send time; the work-in-progress 07 carries it
untimed.
without a timescale, each frame stamped with its group's start.

A publisher refuses a group that starts before a lower one, and so does a
moq-lite 07 receiver. A receiver passes on the timestamps it gets over moq-lite
Expand Down Expand Up @@ -449,9 +459,10 @@ suits real-time audio and sensor data. There is no stream fallback, so a
datagram that doesn't fit isn't delivered.

Datagram tracks have a namespace apart from stream tracks, so `audio` as
datagrams and `audio` as streams are two independent tracks. Nothing on the
wire says which kind a name is: the application knows from its catalog or by
convention, so a broadcast's track listing never includes a datagram track. In
datagrams and `audio` as streams are two independent tracks. A broadcast's
track listing says which kind each track is, and lists datagram tracks only
over the work-in-progress moq-lite 07; elsewhere the application knows the kind
from its catalog or by convention. In
Rust, `broadcast.create_datagrams(name, info)` publishes one and
`broadcast.datagrams(name)` reads it. In JavaScript use
`broadcast.createDatagrams(name, info)` and `broadcast.datagrams(name)`.
Expand Down
9 changes: 5 additions & 4 deletions drafts/draft-lcurley-moq-e2ee.md
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,7 @@ Neither can cause a nonce to repeat, because only the publisher instance chooses
A restart or replacement of a publisher is a new instance and mints a new epoch.
So is a cloned process image, such as a `fork` without `exec`, a restored VM snapshot or process checkpoint, or a producing generation prepared once and copied to two processes: each copy MUST mint its own generation before it encrypts.
A clone copies the epoch and the per-track counters verbatim, so two copies that both encrypt would protect different plaintext under the same key and nonce, and nothing on the wire lets a receiver or relay detect it.
Transport sequence numbers therefore restart freely without any coordination between instances.
Group starts and datagram sequences therefore restart freely without any coordination between instances.
An ended instance stays readable only for as long as relays or archives retain it under its epoch; once another instance wins the shared path, subscribers resolve that one.


Expand Down Expand Up @@ -234,7 +234,8 @@ A subscriber derives both from the semantic name it wants; a publisher derives t
A protected object is the tuple `(generation, physical_name, domain, group, frame)`.

## Grouped Frames
A grouped frame uses `domain = 0x00`, the group's sequence as `group`, and the frame index within that group as `frame`.
A grouped frame uses `domain = 0x00`, the group's start as `group`, and the frame index within that group as `frame`.
The start is the Group Start of a moq-lite-07 GROUP, the Group Sequence of an earlier moq-lite version, and the Group ID on MoQ Transport, which carry the same value ({{moql}} Section "Group").
moq-lite numbers frames from 0 in write order ({{moql}}).
On MoQ Transport, `frame` is the explicit Object ID, never its arrival ordinal.
Publishers supporting both transports MUST assign contiguous Object IDs from zero so that each matches its moq-lite write-order index; relays MUST NOT renumber protected objects.
Expand Down Expand Up @@ -265,7 +266,7 @@ AES-128-GCM encrypts the application bytes with `key`, `nonce`, and empty AAD.
The bytes placed in the MoQ frame or datagram payload are ciphertext concatenated with the 16-byte tag, in the {{RFC5116}} convention.
There is no inner header.

Within a generation a publisher MUST allocate each semantic name's group sequences, and separately its datagram sequences, monotonically, and frame indices in write order, so an identity is encrypted at most once.
Within a generation a publisher MUST give each semantic name's groups strictly increasing starts, allocate its datagram sequences monotonically, and frame indices in write order, so an identity is encrypted at most once.
Encrypting at an identity the same instance already used is `reuse` and MUST be refused.
Relays and caches forward ciphertext unchanged, so replay from a cache never re-encrypts.

Expand All @@ -290,7 +291,7 @@ Encrypting then compressing is forbidden: ciphertext does not compress.
# Bounds {#bounds}
Implementations MUST refuse non-integer identities (including NaN and infinities) and identities outside these bounds before encoding or AEAD:

- `group` (grouped sequence or datagram sequence) and `kid`: `0..=2^53-1`. Above that is `identity`.
- `group` (group start or datagram sequence) and `kid`: `0..=2^53-1`. Above that is `identity`.
- `frame`: `0..=2^32-1`. `2^32` and above is `identity`.
- AEAD operations with one key: at most `2^24` invocations and at most `2^36` plaintext bytes (`2^32` 16-byte blocks). Exceeding either is `exhausted`.

Expand Down
Loading