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
9 changes: 5 additions & 4 deletions doc/bin/relay/cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,10 +23,11 @@ The first relay a request reaches picks the origin node, by a hash of the path
and the node's identity that every relay computes alike, and names it on the
request so later hops follow their own route to that node. A relay running both
versions translates: a moq-lite-06 peer's routes enter the route layer as the
relay's own claims, and lite-07 routes reach a moq-lite-06 peer as a hop list
that starts at their origin node. A relay drops a moq-lite-06 route whose hop
list names its own routing identity, since that is one of its claims coming
back.
relay's own claims, keeping their hop list, which lite-07 carries alongside
them. A lite-07 route reaches a moq-lite-06 peer as that hop list followed by
its origin node. A relay drops a route whose hop list names it, by its hop or
its routing identity, since that is one of its claims coming back, so a
rolling upgrade's mix of versions ends a withdrawn broadcast everywhere.

A track from a moq-transport publisher keeps its Object IDs, object properties,
and END\_OF\_GROUP status objects across a moq-lite-07 link, since relays
Expand Down
23 changes: 20 additions & 3 deletions drafts/draft-lcurley-moq-lite.md
Original file line number Diff line number Diff line change
Expand Up @@ -972,6 +972,8 @@ The following Setup Parameters are defined:
|------|----------------|-------------|
| 0x8 | Route Key | Proof (..) |
|------|----------------|-------------|
| 0x9 | Lite-06 Chain | (empty) |
|------|----------------|-------------|

### Probe Parameter {#probe-parameter}
The Probe Parameter advertises the sender's capability level when acting as a publisher on a [Probe Stream](#probe).
Expand Down Expand Up @@ -1064,6 +1066,11 @@ A receiver that relies on the key MUST verify the signature first, closing the s
A relay MUST NOT forward it.


### Lite-06 Chain Parameter {#lite06-chain-parameter}
The Lite-06 Chain Parameter says the sender reads the Lite-06 Chain on ANNOUNCE_START, ANNOUNCE_UPDATE, and ANNOUNCE_RESTART (see [ANNOUNCE_START](#announce-start)).
It is a temporary extension for relays that also peer over moq-lite-06, and the next version removes it.
The Parameter Value MUST be empty; a receiver MUST close the session with a PROTOCOL_VIOLATION otherwise.

## ANNOUNCE_REQUEST {#announce-request}
A subscriber sends an ANNOUNCE_REQUEST message to indicate it wants to receive the claims, and the routes they travel under, for any broadcasts with a path that starts with the requested prefix.

Expand Down Expand Up @@ -1258,6 +1265,7 @@ ANNOUNCE_START Message {
Instance (b),
Epoch (i),
Announce Cost (i),
[Lite-06 Chain (..)],
}
~~~

Expand Down Expand Up @@ -1290,6 +1298,12 @@ Only an ANNOUNCE_RESTART changes the Instance or the Epoch; ANNOUNCE_UPDATE neve
The origin's price for this prefix, in the units of the [Cost Parameter](#cost-parameter): 0 for content it already produces, larger for a standby that starts work on demand.
A relay forwards it unchanged; the cost of a path through the claim is the Announce Cost plus the route's metric.

**Lite-06 Chain**:
The moq-lite-06 Hop ID list a claim arrived with where its origin node learned it over moq-lite-06, encoded as that list: a count, then each Hop ID.
A publisher sends it, as the message's last field, only to a peer that sent the [Lite-06 Chain Parameter](#lite06-chain-parameter), and only when the claim has one; a received empty chain is a PROTOCOL_VIOLATION.
A relay forwards it unchanged, and translating the claim for a moq-lite-06 peer sends it followed by a Hop ID standing for the claim's origin node.
A node MUST NOT serve a claim whose chain names itself, by its own Hop ID or one standing for its Node ID, or whose translated chain would exceed its hop limit.


## ANNOUNCE_END {#announce-end}
A publisher sends an ANNOUNCE_END message when the origin withdrew a claim, referencing its Announce ID.
Expand Down Expand Up @@ -1325,6 +1339,7 @@ ANNOUNCE_UPDATE Message {
Message Length (i)
Announce ID (i),
Announce Cost (i),
[Lite-06 Chain (..)],
}
~~~

Expand All @@ -1334,8 +1349,8 @@ Set to 0x2 to indicate an ANNOUNCE_UPDATE message.
**Announce ID**:
As defined for [ANNOUNCE_END](#announce-end).

**Announce Cost**:
As defined for [ANNOUNCE_START](#announce-start), replacing the claim's.
**Announce Cost** and **Lite-06 Chain**:
As defined for [ANNOUNCE_START](#announce-start), replacing the claim's; an absent chain replaces it with none.


## ANNOUNCE_RESTART {#announce-restart}
Expand All @@ -1352,6 +1367,7 @@ ANNOUNCE_RESTART Message {
Instance (b),
Epoch (i),
Announce Cost (i),
[Lite-06 Chain (..)],
}
~~~

Expand All @@ -1361,7 +1377,7 @@ Set to 0x3 to indicate an ANNOUNCE_RESTART message.
**Announce ID**:
As defined for [ANNOUNCE_END](#announce-end).

**Instance**, **Epoch**, and **Announce Cost**:
**Instance**, **Epoch**, **Announce Cost**, and **Lite-06 Chain**:
As defined for [ANNOUNCE_START](#announce-start), replacing the claim's.

## ANNOUNCE_FLOOR {#announce-floor}
Expand Down Expand Up @@ -2200,6 +2216,7 @@ The `Message Length` describes the payload size on the wire.
- The Cost parameter must be at least 1.
- Replaced the shortest-path, Hop ID, Instance Hash, and Chain Hash tie-breaks with the local priority of the route's session, the Announce Cost plus the route's metric, and a Rendezvous Hash of the requested path and the origin's Node ID.
- Removed the standby-ordering deployment requirements on Route Cost seeds and bounds.
- Added the temporary Lite-06 Chain Setup Parameter (0x9) and a trailing Lite-06 Chain on ANNOUNCE_START, ANNOUNCE_UPDATE, and ANNOUNCE_RESTART: the moq-lite-06 Hop ID list of a claim learned over moq-lite-06, which a node drops when it names that node.

### Tracks {#changelog-07-tracks}

Expand Down
1 change: 0 additions & 1 deletion quest/m1/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,6 @@ moves what remains of them once their claims merge.

- [Drop set](/quest/m1/drop-set.md) - the drop set's track and cursor runs are billed to the cache pool, so fragmenting drops costs what the pool holds; eviction folds final runs or ends the cursor with `TooFarBehind`
- [Routing guide](/quest/m1/routing-guide.md) - concepts and practical outbound federation setup
- [A withdrawn claim ends across mixed lite-06 and lite-07 relays](/quest/m1/mixed-version-ring.md) - lite-07 carries a temporary lite-06 compatibility chain, so a rolling upgrade's withdrawn broadcast stops circling
- [A reader on a failed copy continues on the held re-offer](/quest/m1/copy-recover.md) - a live reader keeps a group whose copy fails by continuing on the same track's re-offer at the same frame
- [Group errors are cached by kind](/quest/m1/group-error-cache.md) - permanent group errors bind every reader, retryable ones are kept only for a bounded time, and a live SUBSCRIBE_DROP or FETCH answered `Old` no longer caches it for good
- [The overcommitted receive-window cells run again](/quest/m1/receive-windows-evicted.md) - `benchmark_receive_windows` measures its 256-stream and 4 MiB-frame cells again, reporting delivered frames and evictions instead of stalling
Expand Down
96 changes: 0 additions & 96 deletions quest/m1/mixed-version-ring.md

This file was deleted.

3 changes: 1 addition & 2 deletions quest/m2/cluster-routing/routes/js.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Decided 2026-10-27 (maintainer), from
the cheapest one; fix it with the route-selection rework here.
- Feed the availability API from [Announcement availability](/quest/m2/cluster-routing/routes/availability.md).
- Rust/JS interop covers the route messages, the floor marker, and the echo.
- Decode the temporary lite-06 compatibility chain that lite-07 announcements carry ([mixed-version ring](/quest/m1/mixed-version-ring.md)). JS translates nothing, so it keeps no chain.
- Leave the temporary Lite-06 Chain Setup Parameter unsent: JS translates nothing, so it keeps no chain, and a Rust peer sends the chain only to a peer that offers it.
- Restore the native JS lite-07 lanes. Decided 2026-11-06 (maintainer,
/quest-complete on [moq-dev/moq#8023](https://github.com/moq-dev/moq/pull/8023)),
asked how to handle the in-tree lanes running JS on lite-07-wip once the
Expand All @@ -43,7 +43,6 @@ the cheapest one; fix it with the route-selection rework here.
## Required

- [Announcement availability](/quest/m2/cluster-routing/routes/availability.md) - the API this feeds
- [Mixed-version ring](/quest/m1/mixed-version-ring.md) - defines the compatibility chain field this decodes

## Related

Expand Down
7 changes: 3 additions & 4 deletions quest/m2/lite07-finalize.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,9 +28,9 @@ The route layer of [Cluster routing](/quest/m2/cluster-routing/README.md)
(ROUTE_START/UPDATE/END, path-less ANNOUNCE, the native hop list dropped) lands in
lite-07, decided 2026-10-05. That removes lite-07's `Hop Base`/`Hop Keep`
announce compression along with the hop list, and moq.pro's lite-07 rollout
has to plan for a lite-07 without native hop lists; only the temporary lite-06
compatibility chain from [Mixed-version ring](/quest/m1/mixed-version-ring.md)
rides announcements until the lite-07 to lite-08 migration. Only
has to plan for a lite-07 without native hop lists; only the temporary Lite-06
Chain, negotiated by its Setup Parameter, rides announcements until the lite-07
to lite-08 migration. Only
[Routes and announces](/quest/m2/cluster-routing/routes/README.md) gates the cut,
not the later federation/P2P integrations. Decided 2026-10-13: routes now
owns the tier/partition correctness tests, so they run before the cut. Peer
Expand Down Expand Up @@ -127,7 +127,6 @@ whose lite-07 encoding [lite-07 by start](/quest/m2/time-addressing/lite07.md) c
- [A group a subscriber gives up on is always reported](/quest/m2/group-drops.md) - may add SUBSCRIBE_DROP for a stopped group; leaves this list if it takes the no-wire path
- [Delete the old start bookkeeping](/quest/m2/subscribe-ranges/start-bookkeeping.md) - may change START per update on lite-07
- [Minted instances are a typed flag](/quest/m2/instance-provenance.md) - lite-07 carries an explicit minted flag beside each instance instead of the `~` prefix
- [A withdrawn claim ends across mixed lite-06 and lite-07 relays](/quest/m1/mixed-version-ring.md) - lite-07 announcements carry a temporary lite-06 compatibility chain

## Related

Expand Down
2 changes: 2 additions & 0 deletions rs/moq-net/src/client.rs
Original file line number Diff line number Diff line change
Expand Up @@ -331,6 +331,8 @@ impl Client {
implementation: self.implementation(),
// Filled by `lite::start` from the attached origin handles.
route_key: None,
// Filled by `lite::start` from the version.
lite06_chain: false,
}
} else {
lite::Setup::default()
Expand Down
2 changes: 2 additions & 0 deletions rs/moq-net/src/fuzz.rs
Original file line number Diff line number Diff line change
Expand Up @@ -536,6 +536,7 @@ impl RouteNode {
cost: 0,
upstream: false,
learned: false,
chain: crate::Hops::new(),
}
}

Expand Down Expand Up @@ -637,6 +638,7 @@ impl RouteRelay {
cost,
upstream: false,
learned: false,
chain: crate::Hops::new(),
}
}

Expand Down
Loading
Loading