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
1 change: 0 additions & 1 deletion quest/m0/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,6 @@ regression test per Root Cause First.

- [#3087](/quest/m0/3087-relay-mtls-peers-bypass-auth-api-mode-so-proxy-grants.md) - relay: mTLS peers bypass --auth-api-mode, so proxy grants can't refuse or scope them
- [#2405](/quest/m0/2405-js-net-connect-logs-on-every-connection-at-the-wrong.md) - js/net: connect() logs on every connection at the wrong level and prints the JWT in the URL
- [Route resume identity](/quest/m0/route-resume.md) - a failing route ends the subscription instead of resuming through the next one, since announcements became prefix routes
- [Dart leaks](/quest/m0/dart-leak.md) - the generated Dart bindings leak native memory on every call
- [#3207](/quest/m0/3207-send-valid-publish-done-statuses-for-every-supported-ietf.md) - Send valid PUBLISH_DONE statuses for every supported IETF draft
- [#3076](/quest/m0/3076-moq-relay-publish-is-unimplemented-by-design-make-the.md) - moq-relay: PUBLISH is unimplemented by design - make the rejection fail fast for clients that wait
Expand Down
101 changes: 0 additions & 101 deletions quest/m0/route-resume.md

This file was deleted.

6 changes: 2 additions & 4 deletions quest/m2/pop-skipping/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,9 +85,8 @@ underneath it.
produced the content, which alternate routes to one publisher deliberately
share. The pre-#3225 front kept both (`FrontState.publisher` for the first,
`handover_allowed` and the hold for the last), with `same_identity` comparing
either and refusing `Hop::UNKNOWN` on both. [Route resume
identity](/quest/m0/route-resume.md) restores that comparison rule and the
publisher half as a failover fix; [Rank](/quest/m2/pop-skipping/rank.md) owns
either and refusing `Hop::UNKNOWN` on both. [moq#3312](https://github.com/moq-dev/moq/pull/3312) restored that comparison rule and the
publisher half as the first-hop resume; [Rank](/quest/m2/pop-skipping/rank.md) owns
the carrier half rather than reusing the wrong one.
- The operator hand-authors one undirected base graph. Same-PoP connectivity is
unconditional, not a self-edge operators must remember. The radius-two closure
Expand Down Expand Up @@ -154,7 +153,6 @@ wire version and the two directional costs of one bidirectional session.

## Related

- [Route resume identity](/quest/m0/route-resume.md) - supplies the identity comparison rule adoption reuses on a different hop
- [drain](/quest/m2/drain/README.md) - a second relay per PoP makes the same-PoP link price and its connection cardinality operationally important
- [wildcard](/quest/m2/wildcard/README.md) - it reuses this questline's route cost, and needs a cluster on Lite06
- [relay-memory](/quest/m2/relay-memory/README.md) - a denser mesh multiplies whatever a non-selected route costs
11 changes: 4 additions & 7 deletions quest/m2/pop-skipping/rank.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,13 +49,12 @@ leaving a drained or vanished route stays immediate.
### Two identities, not one

Adoption is a statement about the adjacent relay, and that is a different
identity from the one [Route resume identity](/quest/m0/route-resume.md)
restores. The pre-#3225 front kept both, because they answer different
questions:
identity from the first-hop resume rule [moq#3312](https://github.com/moq-dev/moq/pull/3312) landed.
The pre-#3225 front kept both, because they answer different questions:

- The **first** hop is who produced the content. Alternate routes to one
publisher deliberately share it, which is what makes them spliceable, and it
is what route-resume keys on.
is what the resume rule keys on.
- The **last** hop is the peer that advertised the route: the parent a relay
would be adopting. `handover_allowed` and the hold both keyed on it, and the
rank hash was taken over it (`fnv_key(name, [peer])`).
Expand All @@ -65,7 +64,7 @@ of one broadcast look like the same peer, so a changed parent would go
undetected and two relays could adopt each other, which is the failure the hold
exists to prevent.

What this quest reuses from route-resume is the comparison rule rather than the
What this quest reuses from the resume rule is the comparison rather than the
field: `Hop::UNKNOWN` identifies nobody and never matches itself, so two
anonymous relays must not pass for one relay reconnecting and skip the gate.

Expand All @@ -90,5 +89,3 @@ lucky hash.

- [Warm advertise](/quest/m2/pop-skipping/warm-advertise.md) - there is nothing
to rank until two relays can both advertise one broadcast as warm
- [Route resume identity](/quest/m0/route-resume.md) - supplies the identity
comparison rule, and the publisher half of it
4 changes: 0 additions & 4 deletions quest/m2/pop-skipping/warm-advertise.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,3 @@ draining path retracts rather than repricing, and a subscriber on it moves to
the broader route; a second relay carrying the same broadcast ties on warm and
is separated by cold.

## Required

- [Route resume identity](/quest/m0/route-resume.md) - a subscriber moving
between a warm route and a broader one must resume rather than end
13 changes: 5 additions & 8 deletions quest/m2/wildcard/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,10 +63,10 @@ What is genuinely missing, beyond patterns themselves, is content identity.
Announcement `Epoch` was specified into lite-06 by
[#2611](https://github.com/moq-dev/moq/pull/2611), never implemented, and
removed from the draft by #3225, which retired `draft-lcurley-moq-broadcast`
with it. [Route resume identity](/quest/m0/route-resume.md) restores per-path
identity from the route's first hop, reversing #3225's no-splice rule, and
this questline builds its collision handling on that rather than on a
generation field.
with it. [moq#3312](https://github.com/moq-dev/moq/pull/3312) restored per-path identity
from the route's first hop, reversing #3225's no-splice rule, and this
questline builds its collision handling on that rather than on a generation
field.

### Decisions

Expand Down Expand Up @@ -169,8 +169,7 @@ generation field.
can hash one path to different workers before either concrete announcement
propagates, and both land at the SAME literal path. Whichever route wins
selection serves it, and a consumer moves between them only when the winner's
identity is preserved, per [Route resume
identity](/quest/m0/route-resume.md); two distinct workers are two identities,
identity is preserved, per the first-hop resume rule ([moq#3312](https://github.com/moq-dev/moq/pull/3312)); two distinct workers are two identities,
so the loser's subscribers end and resubscribe rather than being spliced onto
another worker's frames mid-group. Wildcard routing invents neither a lease
nor a generation. This is weaker than the retired `Epoch` design, which could
Expand Down Expand Up @@ -262,5 +261,3 @@ than announce state.
pattern, and its catalog names the generations a wildcard cannot
- [pop-skipping](/quest/m2/pop-skipping/README.md) - it owns the route cost and
the rank hash this reuses
- [Route resume identity](/quest/m0/route-resume.md) - the per-path identity two
colliding advertisers are settled by
4 changes: 1 addition & 3 deletions quest/m2/wildcard/resolve.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ front's ordinary route change moves consumers at a group boundary. A
cache-only answer would strand every bound consumer on the wildcard
subscription with nothing able to migrate or stop it. When the concrete claim
is a DIFFERENT publisher, its consumers end and resubscribe rather than
splicing, per [Route resume identity](/quest/m0/route-resume.md); this quest's
splicing, per the first-hop resume rule ([moq#3312](https://github.com/moq-dev/moq/pull/3312)); this quest's
obligation is the route install that makes selection between them possible. Repeat requests for one path
share that one route, keyed to survive the exclusion filter rather than
handing one peer's answer to another.
Expand Down Expand Up @@ -97,5 +97,3 @@ Tests, at the process level with real sessions rather than an in-process stand-i
## Required

- [Advertise](/quest/m2/wildcard/advertise.md)
- [Route resume identity](/quest/m0/route-resume.md) - a wildcard-served
subscription must resume or end correctly when a concrete claim arrives
Loading