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
12 changes: 9 additions & 3 deletions quest/m2/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,11 @@ complete it before cutting main into release.

## Plan

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
replaces lite-07's route layer before it freezes (rejected: lite-08). The
routes chain stays the critical path, now through that epic.

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
published surface, as the root [questline](/quest/README.md) defines: the
Expand Down Expand Up @@ -222,10 +227,11 @@ maintainer asked that what remains be unblocked or punted, and picked these on
[moq-dev/moq#8768](https://github.com/moq-dev/moq/pull/8768)). m2 keeps only
what would need a breaking release had it landed right after the cut:

- ✅ Left m2: [the request loop](/quest/m2/cluster-routes/request-loop.md)
- ✅ Left m2: [the request loop](/quest/m2/multicast/requests.md)
to m3's cluster-routing epic (a fixture and a fix, no wire), until it
returned to m2's cluster-routes epic on 2026-11-15 (maintainer, on
[moq-dev/moq#8832](https://github.com/moq-dev/moq/pull/8832));
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);
[media consumers](/quest/m3/time-addressing-consumers.md) to m3 (its API
breaks ride the model; dropping hang's markers is tolerated by readers);
[moq-transport time addressing](/quest/m4/ietf-time-addressing.md) to m4
Expand Down
2 changes: 2 additions & 0 deletions quest/m2/cluster-routes/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,8 @@ The items below were decided 2026-11-10 (maintainer, /quest-plan on lite-07 rout

30. ✅ Decided 2026-11-12 (maintainer, /quest-audit before the cut), after a survey of BGP, EIGRP, and their successors against item 27: most of the path rule already matches that prior art (AS_PATH loop detection, root-cause withdrawal, graceful restart, End-of-RIB, outbound route filtering, and item 29's Only-To-Customer flag). Three gaps are taken, all in [the switch](https://github.com/moq-dev/moq/pull/8731) and [acceptance](/quest/m2/cluster-routes/acceptance.md): **a dead-hop message on a scoped session applies only to the routes heard on that session and casts no doubt**, since in BGP a neighbour withdraws only what it sent, and a scoped peer (a federated relay, later a browser) could otherwise name a core hop it only read in a path and drop healthy routes outside its scope; **holds are bounded in time**, a neighbour's missing answer counting as nothing after a deadline, and a session whose announce stream has stopped draining is closed, which avoids EIGRP's stuck-in-active and BGP's zombie routes (RFC 9687), and is safe because a hold protects presence, not loop freedom; and **three tests before any design change**: neighbours noticing a dead relay up to the 3 s keep-alive apart (to size the doubt timer, measured in hops of delay today), a three-relay priority dispute wheel (RFC 4264's wedgies, since priority ranks above cost), and a primary that fails and returns. No wire bytes change; the first defines what the dead-hop message means. Rejected: declaring the link relation in SETUP and refusing leaked routes on receipt (RFC 9234), since the accepting side already knows the relation from its grant and it adds wire for a misconfiguration; MRAI and route-flap damping, which exist because BGP delays announcements; link state; per-hop signatures.

31. Reopened 2026-11-15 (maintainer, /quest-plan on the whole route layer): ✅ **this rule is the baseline, and [cache-aware multicast](/quest/m2/multicast/README.md) replaces it on lite-07-wip before the cut.** An audit of what is built found requirements the path rule does not meet: its exhaustive checking stops at 3 relays and rests on a timer that outlasts every stale offer, route state follows publishers, nothing prefers a warm copy, and a stalled route is never left. Superseded there: item 18 (every publisher an origin node), item 19 (ROUTE_HOLD), item 26's route per scope, item 27's doubt and remembered dead hops, the Route Key and qualified Node IDs of the contract below, and item 14. Standing: the path with its self-naming rule and the withdrawal that names a dead hop (item 27), revisions and floors, one announce stream per side with its interest set (items 21 to 24), the sticky down-only flag (item 29), and drain, then priority, then cost. This epic's children still land: they are what the [bake-off](/quest/m2/multicast/bakeoff.md) measures against. Rejected: repairing this rule in place; freezing lite-07 with it and redesigning in lite-08.

The route layer's core landed in
[moq-dev/moq#7676](https://github.com/moq-dev/moq/pull/7676): a
crate-private, sans-IO `Router` in `rs/moq-net/src/route/`, generic over the
Expand Down
7 changes: 7 additions & 0 deletions quest/m2/cluster-routes/acceptance.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,12 @@ mount continuity (`mount.rs`), and operation-count regressions
(`route/tests/cost.rs`, `route/node/tests.rs`). They found the flaws the
quests under Required fix; the tests that pin each flaw say so in their docs.

Reordered 2026-11-15 (maintainer, /quest-plan on
[cache-aware multicast](/quest/m2/multicast/README.md)): the retirement below
waits for [the switch](/quest/m2/multicast/switch.md), which rewrites these
fixtures' assertions for the new rule and deletes the Required quests it
makes moot.

What remains:

- Retire the quarantine, the dedup, and the hold once the Required quests
Expand All @@ -48,6 +54,7 @@ What remains:

## Required

- [The switch](/quest/m2/multicast/switch.md) - the rule whose fixtures replace the mitigations, once the new route layer is on the wire
- [Held after close](/quest/m2/cluster-routes/held-after-close.md) - a relay whose own session closed shows its held claims unavailable, not offline
- [Doubt holds](/quest/m2/cluster-routes/doubt-holds.md) - a relay keeps holding while doubt alone keeps it off its routes
- [Route fan-out](/quest/m2/cluster-routes/route-fanout.md) - a route change costs only the streams and broadcasts it touches
Expand Down
11 changes: 11 additions & 0 deletions quest/m2/cluster-routes/doubt-holds.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,13 @@ go while its neighbours answer that they have nothing.

## Plan

Reordered 2026-11-15 (maintainer, /quest-plan on [cache-aware
multicast](/quest/m2/multicast/README.md)): this waits on the
[bake-off](/quest/m2/multicast/bakeoff.md). The new rule has neither holds nor
doubt, so nothing would be left for this to fix. If the new rule goes ahead,
[the switch](/quest/m2/multicast/switch.md) deletes this quest with the
fixtures that pin it; if it does not, this starts as written.

Kept 2026-11-15 (maintainer, /quest-complete on
[moq-dev/moq#8832](https://github.com/moq-dev/moq/pull/8832)): ✅ keep it in
m2 (rejected: drop; moving it to m3).
Expand All @@ -34,6 +41,10 @@ neighbour that holds only because of doubt should answer with ROUTE_HOLD, not
nothing. Check the rule in `RouteHandoff.tla` with the `verify-route` skill
before changing `rs/moq-net/src/route/path.rs`.

## Required

- [The bake-off](/quest/m2/multicast/bakeoff.md) - decides whether the hold and the doubt this fixes remain

## Related

- [Routes and announces](/quest/m2/cluster-routes/README.md) - Plan item 27 and the hold rule
Expand Down
25 changes: 16 additions & 9 deletions quest/m2/cluster-routes/doubt-keepalive.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,20 @@ apart its neighbours notice the death within the keep-alive.

## Plan

Reordered 2026-11-15 (maintainer, /quest-plan on [cache-aware
multicast](/quest/m2/multicast/README.md)): this waits on the
[bake-off](/quest/m2/multicast/bakeoff.md). The maintainer deferred how the
doubt covers a silent death on 2026-11-15, "not yet sure about the doubt
design", and decided the same day that evidence replaces the doubt. If the new
rule goes ahead, [the switch](/quest/m2/multicast/switch.md) deletes this
quest with the fixtures that pin it; if it does not, this starts as written.

If the doubt stays, the decision returns to the maintainer: (a) the doubt
lasts at least the configured idle timeout, so it covers the spread (the
recommendation: no wire change, and a relay already knows its idle timeout);
(b) relay keep-alives shorten below the doubt, which costs traffic on every
relay link; (c) accept the window and keep the test pinning it.

Kept 2026-11-15 (maintainer, /quest-complete on
[moq-dev/moq#8832](https://github.com/moq-dev/moq/pull/8832)): ✅ keep it in
m2 (rejected: drop; moving it to m3).
Expand All @@ -21,16 +35,9 @@ dead `X` at 1 s, holds again at 1.5 s, and moves onto `R3`'s route through
at 3 s. Readers see each move as available for a moment, and a request in
that window goes to a dead relay. A 1 s doubt does not cover a 3 s spread.

## Waiting
## Required

- Maintainer: how the doubt covers a silent death. Options: (a) the doubt
lasts at least the configured idle timeout, so it covers the spread (the
recommendation: no wire change, and a relay already knows its idle
timeout); (b) relay keep-alives shorten below the doubt, which costs
traffic on every relay link; (c) accept the window and keep the test
pinning it. Check with `/quest-grill` or the PR that picks it up. The
maintainer deferred this decision on 2026-11-15, not yet sure about the
doubt design.
- [The bake-off](/quest/m2/multicast/bakeoff.md) - decides whether the doubt this sizes remains

## Related

Expand Down
12 changes: 12 additions & 0 deletions quest/m2/cluster-routes/held-after-close.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,14 @@ route recovers.

## Plan

Reordered 2026-11-15 (maintainer, /quest-plan on [cache-aware
multicast](/quest/m2/multicast/README.md)): this waits on the
[bake-off](/quest/m2/multicast/bakeoff.md). The new rule has no hold: a reader
debounces unavailable to offline locally, which answers the same symptom. If
the new rule goes ahead, [the switch](/quest/m2/multicast/switch.md) deletes
this quest with the fixtures that pin it; if it does not, this starts as
written.

Kept 2026-11-15 (maintainer, /quest-complete on
[moq-dev/moq#8832](https://github.com/moq-dev/moq/pull/8832)): ✅ keep it in
m2 (rejected: drop; moving it to m3).
Expand All @@ -32,6 +40,10 @@ move it, unavailable, onto a stream that still hears the held route, or show
it through the node itself, before the closing stream withdraws it. Turn the
three pinned fixtures into the contract's held-then-available sequence.

## Required

- [The bake-off](/quest/m2/multicast/bakeoff.md) - decides whether the hold this shows remains

## Related

- [Routes and announces](/quest/m2/cluster-routes/README.md) - the hold rule and "Presence and availability are separate"
64 changes: 0 additions & 64 deletions quest/m2/cluster-routes/request-loop.md

This file was deleted.

13 changes: 13 additions & 0 deletions quest/m2/cluster-routes/route-fanout.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,15 @@ remembered for sessions nothing was learned on.

## Plan

Reordered 2026-11-15 (maintainer, /quest-plan on [cache-aware
multicast](/quest/m2/multicast/README.md)): this waits on the
[bake-off](/quest/m2/multicast/bakeoff.md). Its first and third findings are
in `path::Router`'s indexes and its doubts and dead hops, which the new router
replaces; the second, per-broadcast rewrites in `route/node.rs`, the
[router](/quest/m2/multicast/router.md) takes as a requirement. If the new
rule goes ahead, [the switch](/quest/m2/multicast/switch.md) deletes this
quest with the fixtures that pin it; if it does not, this starts as written.

Kept 2026-11-15 (maintainer, /quest-complete on
[moq-dev/moq#8832](https://github.com/moq-dev/moq/pull/8832)): ✅ keep it in
m2 (rejected: drop; moving it to m3).
Expand Down Expand Up @@ -43,6 +52,10 @@ once fixed:
Build on [moq-dev/moq#8734](https://github.com/moq-dev/moq/pull/8734),
which also edits `path.rs`.

## Required

- [The bake-off](/quest/m2/multicast/bakeoff.md) - decides whether the path router these findings are in remains

## Related

- [Route wakes](/quest/m4/route-wakes.md) - origin-side wakes per route change
Expand Down
12 changes: 11 additions & 1 deletion quest/m2/lite07-finalize.md
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,7 @@ maintainer picked these on
[moq-dev/moq#8768](https://github.com/moq-dev/moq/pull/8768)), applying the maintainer's rule that m2 keeps only what
would need a breaking release had it landed right after the cut:

- ✅ [The request loop](/quest/m2/cluster-routes/request-loop.md) moved
- ✅ [The request loop](/quest/m2/multicast/requests.md) moved
to m3 and no longer gates this: a fixture and a fix with no wire change.
It returned to m2 on 2026-11-15 and still does not gate this.
- ✅ [Route layer acceptance](/quest/m2/cluster-routes/acceptance.md) stays
Expand All @@ -155,8 +155,18 @@ would need a breaking release had it landed right after the cut:
both publishers already name a Group Stream the subscriber stopped in
SUBSCRIBE_DROP, which the draft now states, even after a reliable reset.

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
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 end when
[the switch](/quest/m2/multicast/switch.md) lands.

## Required

- [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
- [Routes and announces](/quest/m2/cluster-routes/README.md) - lite-07 carries the route layer: ROUTE per origin node and path-less ANNOUNCE, with the native hop list gone (only the temporary lite-06 compatibility chain remains)
- [Lite-07 by start](/quest/m2/time-addressing/lite07.md) - lite-07 carries group starts, previous-start links, GROUP_END, and time bounds instead of sequence numbers
- [@moq/net by start](/quest/m2/time-addressing/js.md) - JS speaks the same lite-07 wire
Expand Down
Loading