Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
11 changes: 7 additions & 4 deletions quest/m2/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ removal, a rename, or a wire, catalog, or format change that is free until
returned from m4, and the two moq-transport interop quests in m3 were
deleted. Kept as they are: datagram tracks with their lite-05/06 bridge,
all seven lite versions, the hidden `.` path prefix, and the route plan
of [cache-aware multicast](/quest/m2/multicast/README.md), whose switch
of [cache-aware multicast](https://github.com/moq-dev/moq/blob/41cc107579/quest/m2/multicast/README.md), whose switch
settled the public route API in
[moq-dev/moq#9053](https://github.com/moq-dev/moq/pull/9053). The
moq-cluster draft stays, since third-party relays ship it, rewritten to
Expand Down Expand Up @@ -77,9 +77,12 @@ overruns. [moq-dev/moq#9198](https://github.com/moq-dev/moq/pull/9198) and
relative starts and the bare GROUP_END are gone.

Decided 2026-11-15 (maintainer, /quest-plan on the whole route layer): ✅ the
cut waits on [cache-aware multicast](/quest/m2/multicast/README.md), which
cut waits on [cache-aware multicast](https://github.com/moq-dev/moq/blob/41cc107579/quest/m2/multicast/README.md), which
replaces lite-07's route layer before it freezes (rejected: lite-08). The
routes chain stays the critical path, now through that epic.
That epic finished 2026-11-20
([moq-dev/moq#9231](https://github.com/moq-dev/moq/pull/9231)), and the cut's
routing wait moved to [claim reach](/quest/m2/lite07-claim-reach-routes.md).

Decided 2026-11-05 (maintainer, milestone re-cut): m2 holds the breaking half
of what was "everything before the cut" (2026-10-20). Breaking covers every
Expand Down Expand Up @@ -122,7 +125,7 @@ Decided 2026-11-12 (maintainer, /quest-audit before the cut):
path; see the routes epic, finished in
[moq-dev/moq#9202](https://github.com/moq-dev/moq/pull/9202). The
route layer that replaced it keeps the flag as a route's mark
([cache-aware multicast](/quest/m2/multicast/README.md) item 6).
([cache-aware multicast](https://github.com/moq-dev/moq/blob/41cc107579/quest/m2/multicast/README.md) item 6).

Carried from m1's Plan before the re-cut, where "m1" means the whole pre-cut
milestone, now m1 and m2:
Expand Down Expand Up @@ -301,7 +304,7 @@ what would need a breaking release had it landed right after the cut:
to m3's cluster-routing epic (a fixture and a fix, no wire), until it
returned to m2 on 2026-11-15 (maintainer, on
[moq-dev/moq#8832](https://github.com/moq-dev/moq/pull/8832)) and became
the request quest of [cache-aware multicast](/quest/m2/multicast/README.md);
the request quest of [cache-aware multicast](https://github.com/moq-dev/moq/blob/41cc107579/quest/m2/multicast/README.md);
media consumers (later start placement) to m3 (its API
breaks ride the model; dropping hang's markers is tolerated by readers),
until it returned to m2 on 2026-11-16;
Expand Down
9 changes: 6 additions & 3 deletions quest/m2/lite07-finalize.md
Original file line number Diff line number Diff line change
Expand Up @@ -174,12 +174,16 @@ would need a breaking release had it landed right after the cut:

Decided 2026-11-15 (maintainer, /quest-plan on the whole route layer): ✅
lite-07 carries the redesigned route layer of
[cache-aware multicast](/quest/m2/multicast/README.md), and the cut waits
[cache-aware multicast](https://github.com/moq-dev/moq/blob/41cc107579/quest/m2/multicast/README.md), and the cut waits
for it (rejected: freezing lite-07 with the path rule and redesigning in
lite-08; freezing lite-07 with no route layer). That redesign removes the
Route Key Parameter, so the 2026-11-10 wait on its symbolic model and the
route key lane's early signal above ended when
[moq-dev/moq#8987](https://github.com/moq-dev/moq/pull/8987) landed.
That epic finished 2026-11-20 with its last child
([moq-dev/moq#9231](https://github.com/moq-dev/moq/pull/9231)), and the cut's
routing wait moved to [claim reach](/quest/m2/lite07-claim-reach-routes.md)
(maintainer, 2026-11-20).

Decided 2026-11-16 (maintainer, /quest-plan of the pre-cut audit, which also
audited the lite-07 draft for what it could lose):
Expand All @@ -197,7 +201,7 @@ audited the lite-07 draft for what it could lose):
- ✅ Kept as they are: datagram tracks, including the lite-05/06 bridge (a
named consumer wants them); all seven lite versions, which keep
negotiating with today's behaviour; the hidden `.` path prefix; and the
route plan of [cache-aware multicast](/quest/m2/multicast/README.md)
route plan of [cache-aware multicast](https://github.com/moq-dev/moq/blob/41cc107579/quest/m2/multicast/README.md)
(rejected: routing as a separately versioned SETUP extension).
- The smaller wire fixes rode [lite-07 by start](https://github.com/moq-dev/moq/pull/8908):
Max Age as value plus one, no Padding stream or datagram type, a kind in
Expand Down Expand Up @@ -232,7 +236,6 @@ and switching rules in `rs/moq-net/AGENTS.md` before the cut):

- [No relative anchors](/quest/m2/time-addressing/no-relative-anchors.md) - SUBSCRIBE's anchors lose Relative, and Min Age places a live join
- [Group Streams carry each time once](/quest/m2/time-addressing/group-times.md) - GROUP loses Previous Start, FRAME's first delta counts from the start, and GROUP_END carries an end
- [Cache-aware multicast](/quest/m2/multicast/README.md) - lite-07 carries the redesigned route layer: routes to forwarding nodes, no holds or doubt, claims crossing trust boundaries by a chain, and no Route Key
- [Groups never overlap](/quest/m2/groups-never-overlap.md) - first-party producers and importers keep the no-overlap MUST the cut publishes
- [A lite-07 claim is shown no broader than the grants it crossed](/quest/m2/lite07-claim-reach-routes.md) - a peer is never shown a claim at a path no route of it can serve, through any number of relays (maintainer, 2026-11-20)

Expand Down
Loading