diff --git a/quest/m2/cluster-routing/federation.md b/quest/m2/cluster-routing/federation.md index b8d64c6389c..26e1b042283 100644 --- a/quest/m2/cluster-routing/federation.md +++ b/quest/m2/cluster-routing/federation.md @@ -63,7 +63,7 @@ only the route children federation builds on, [acceptance](/quest/m2/cluster-routing/routes/acceptance.md), not the whole [route epic](/quest/m2/cluster-routing/routes/README.md). Federation is relay-to-relay, so browser route-key proofs, the Playwright pin they wait on, -and the mixed-version follow-ups (lite-06 failover, mount takeover) gate the +and the mixed-version follow-up (mount takeover) gates the lite-07 cut, not this. Its consumer, the [mesh node](/quest/m3/mesh/node.md), is a Rust relay too. Acceptance still brings the js/net route layer for its Rust/JS interop checks. Rejected: session integration alone, which drops the diff --git a/quest/m2/cluster-routing/routes/README.md b/quest/m2/cluster-routing/routes/README.md index 1816813739e..05743abd669 100644 --- a/quest/m2/cluster-routing/routes/README.md +++ b/quest/m2/cluster-routing/routes/README.md @@ -542,7 +542,6 @@ benchmarks. - [Route layer acceptance](/quest/m2/cluster-routing/routes/acceptance.md) - forwarding fixtures ported and the model deleted, incident fixtures, end-to-end checks, and benchmarks - [Firefox tabs prove their route key](/quest/m2/cluster-routing/routes/browser-proof.md) - a current Firefox tab opens a lite-07 session with a route-key proof the relay verifies, once neqo's exporter follows the draft - [Playwright bundles Chromium's spec exporter](/quest/m2/cluster-routing/routes/playwright-pin.md) - the toolchain's Playwright bundles Chromium 158+, so the route key lane proves the Chromium tab -- [A declined lite-06 route is reconsidered when the lite-07 path fails](/quest/m2/cluster-routing/routes/lite06-failover.md) - a mixed-version relay fails over to the lite-06 route it declined - [A covering predecessor's takeover shows under a mount](/quest/m2/cluster-routing/routes/mount-takeover.md) - lite-07 presents a takeover beneath a mount as lite-06 does ## Related diff --git a/quest/m2/cluster-routing/routes/lite06-failover.md b/quest/m2/cluster-routing/routes/lite06-failover.md deleted file mode 100644 index 01e0ac1055e..00000000000 --- a/quest/m2/cluster-routing/routes/lite06-failover.md +++ /dev/null @@ -1,23 +0,0 @@ -# [M] A declined lite-06 route is reconsidered when the lite-07 path fails - -## Goal - -In a mixed-version cluster, a relay that declined an identity's lite-06 -route because it already knew that identity over lite-07 accepts the lite-06 -route again once the lite-07 path is gone, so the lite-06 path takes over -instead of leaving the broadcast unreachable. Today the relay declines it -once and never revisits it. - -## Plan - -Decided 2026-11-06 (maintainer, /quest-complete, a follow-up of -[moq-dev/moq#8023](https://github.com/moq-dev/moq/pull/8023)): ✅ m2, in this -epic, since the cut ships mixed-version clusters and this is a failover gap. -Not chosen: m3; m4. - -- Recognize known identities on lite-06 ingress, and keep the declined route - so it can be accepted again when the lite-07 route for that identity ends. -- Cover it with a mixed-version test: a relay with both paths to one - publisher loses the lite-07 one and keeps serving over lite-06. - -Starts once #8023 lands. Public API: none expected. Wire: none.