From e898a612b58e8a65dc597140857abdd226401859 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Wed, 30 Sep 2026 13:58:13 -0700 Subject: [PATCH] quest: delete cluster-origin and front-upgrade from the wildcard line cluster-origin is replaced by m1 ietf-cluster-off and m2 ietf-cluster-peers (#4629); front-upgrade is dropped by the edge/core tiers decision. Co-Authored-By: Claude Opus 5.5 --- quest/m1/README.md | 2 -- quest/m1/cluster-origin.md | 38 -------------------------------------- quest/m1/front-upgrade.md | 37 ------------------------------------- 3 files changed, 77 deletions(-) delete mode 100644 quest/m1/cluster-origin.md delete mode 100644 quest/m1/front-upgrade.md diff --git a/quest/m1/README.md b/quest/m1/README.md index e28aa4b36ad..5cef63b6d7a 100644 --- a/quest/m1/README.md +++ b/quest/m1/README.md @@ -67,8 +67,6 @@ QUIC studies there on that rule. - [#2991](/quest/m1/2991-net-coalesce-dynamic-tracks-and-preserve-sequences-across.md) - one dynamic producer per track name in both languages, with the sequence namespace surviving a replacement - [JavaScript FETCH](/quest/m1/js-fetch.md) - generic on-demand group serving and IETF FETCH for browser publishers - [Archive](/quest/m1/archive/README.md) - record selected tracks to any object_store and replay them over FETCH or derived HLS; the catalog entry and format may break in place, since no archives exist -- [Cluster origin reply](/quest/m1/cluster-origin.md) - a moq-transport downstream of a spreading relay never splices two pool members, and the cluster draft says how it tells them apart -- [Verified route upgrade](/quest/m1/front-upgrade.md) - a relay moves a live subscription to a cheaper route once that route's reply names the same origin - [In-band auth](/quest/m1/auth/README.md) - a session tells its peer what it may publish and subscribe to, unions tokens presented in band, and fails loud on an out-of-scope publish - [Dropped sources](/quest/m1/dropped-sources.md) - track consumers see the producer's real error on every end path, never `Dropped` - [C++ through moq-ffi](/quest/m1/cpp/README.md) - generated C++ over moq-ffi with futures and expected-style errors, shipped as a tarball, vcpkg, and Conan, and adopted by the OBS plugin diff --git a/quest/m1/cluster-origin.md b/quest/m1/cluster-origin.md deleted file mode 100644 index c887da5b0e8..00000000000 --- a/quest/m1/cluster-origin.md +++ /dev/null @@ -1,38 +0,0 @@ -# [M] Cluster origin reply - -## Goal - -A relay that spreads a pool's paths never lets a moq-transport downstream -splice one pool member's content onto another's, and -`draft-lcurley-moq-cluster` says how a downstream learns which member serves a -path. - -## Plan - -Spreading keys route selection's hash on the requested path, so equal-cost -advertisers of one prefix share its paths, and a relay advertises one route for -the whole pool. On moq-lite-07 the SUBSCRIBE_OK and FETCH_OK replies name the -serving origin, and a relay splices a failover only between replies naming the -same one. The cluster extension (moq-transport 17+) has no such field, so a -downstream relay still pins failover to the advertisement's first Hop ID, which -labels the pool rather than the member serving the path. The draft's -"Several Publishers of One Namespace" section still requires that the first -Hop ID downstream name the publisher whose Objects flow, which a spreading -relay breaks. - -Two ways out, to settle before implementing: - -- Name the serving origin in a moq-transport reply as a cluster-extension - parameter, mirroring lite-07, and stitch on it. Recommended: one identity - model on every wire. -- Keep the label truthful instead: toward a downstream that cannot learn the - origin, do not spread (or advertise per path). - -Either way the test is the one lite-07 has: two workers behind a pool relay -behind a moq-transport downstream relay, and killing the serving worker ends -the downstream subscription rather than splicing the survivor's objects. - -## Related - -- [Wildcard](/quest/m0/wildcard/README.md) - spreading and the lite-07 reply - origin landed there diff --git a/quest/m1/front-upgrade.md b/quest/m1/front-upgrade.md deleted file mode 100644 index b8dff150e4e..00000000000 --- a/quest/m1/front-upgrade.md +++ /dev/null @@ -1,37 +0,0 @@ -# [M] Verified route upgrade - -## Goal - -A relay whose front learned its origin from a reply moves a live subscription -to a cheaper route once that route's source proves it serves the same origin, -instead of staying on the costlier route until it fails. - -## Plan - -On moq-lite-07 a front's identity is the origin its source's SUBSCRIBE_OK or -FETCH_OK names, not the route's first hop, because one route can lead to many -pool members. The front only learns a new route's origin once that source -replies, so today it stays on its live source when a better route appears -(`Pin::Stay` in `rs/moq-net/src/model/front.rs`) and only moves on failover. -That keeps content from being spliced across origins but leaves traffic on a -route that may no longer be the cheapest. - -The move to make: when a cheaper route appears, ask it before letting go of the -live source, and splice over at a group boundary only once its reply names the -front's origin. A reply naming another origin leaves the front where it is, -with nothing delivered from the candidate. Things to watch: - -- The candidate's content is held until admitted (the copy's provenance), so - asking early must not deliver anything or start demand the live source - already covers longer than needed. -- Churn: a route that keeps flapping should not keep opening and dropping - upstream subscriptions. -- Measure the cost of a verification round trip against staying put, and - benchmark it across routes and subscribers. - -## Related - -- [Wildcard](/quest/m0/wildcard/README.md) - the reply-named identity landed - there -- [Cluster origin reply](/quest/m1/cluster-origin.md) - the same identity on - moq-transport