From 13803560e56ae1aae136542b2e1020afc54779ef Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sat, 31 Oct 2026 23:27:12 -0700 Subject: [PATCH 1/3] chore(quest): claim quest/m1/ietf-publisher-unknown-range.md Quest-Claim: 6d36e2006157c151 From 9ad313e96c69b8599ceee116c430177bd555828b Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sat, 31 Oct 2026 23:29:30 -0700 Subject: [PATCH 2/3] docs(quest): record superseded unknown-range premise Co-Authored-By: GPT-6.1 Sol --- quest/m1/ietf-publisher-unknown-range.md | 39 +++++++++++++++++++----- 1 file changed, 32 insertions(+), 7 deletions(-) diff --git a/quest/m1/ietf-publisher-unknown-range.md b/quest/m1/ietf-publisher-unknown-range.md index dfb757042fe..322f8ef7d51 100644 --- a/quest/m1/ietf-publisher-unknown-range.md +++ b/quest/m1/ietf-publisher-unknown-range.md @@ -9,16 +9,41 @@ of skipping it silently. ## Plan +Inspection 2026-10-31: this plan predates the final implementation of +[moq-dev/moq#7204](https://github.com/moq-dev/moq/pull/7204). That change removed +both listed-group loops and the JS unknown-marker behavior. Rust's +`prepare_fetch` reads the sole group into an owned `FetchedGroup` before +`serve_fetch_stream` sends FETCH_OK; JS does the same with `readFetched`. +Eviction before acceptance refuses the request, while eviction after acceptance +cannot truncate the buffered answer. There is no remaining FETCH listing/write +race to reproduce on drafts 18 or 22. + +Draft-22 fills still acquire the selected head after opening FETCH_HEADER, but +both Rust `run_fill` and JS `#runFill` reset their own stream when the group is +unavailable. This is explicit failure, not the silent skip described below. +The merged PR records that fill-failure policy. Replacing it with an unknown +marker needs a new scope decision, including whether a missing head may count +as a successfully completed fill. + +`Unsupported` must remain a refusal: it can mean unsupported request shape or +an IETF group representation that FETCH cannot serialize. `NotFetchable` means +the sequence is held as a datagram, not that its existence is unknown. Before +FETCH_OK either error is returned as a request refusal; a fill resets its own +stream. Neither should be hidden as unknown without a separate decision. + +Recommendation to the parent: retire this quest as superseded by the settled +one-group implementation. If a fill marker is still wanted, first settle that +behavior for Rust and JS together. No production change has been made. + Found 2026-10-28 by [moq-dev/moq#7150](https://github.com/moq-dev/moq/pull/7150), -which fixed the JS publisher. In `rs/moq-net/src/ietf/publisher.rs` Rust skips -such a group in two places: the FETCH answer loop in `serve_fetch_stream`, on +which fixed the then-current JS publisher. The original Rust diagnosis was a +skip in two places: the FETCH answer loop in `serve_fetch_stream`, on `NotFound | NotFetchable | Unsupported | Old`, and `run_fill`, when `fetch_group` fails with the same errors. -Rust can refetch from upstream, so a skip there means a failed refetch rather -than only an eviction. `NotFound` and `Old` map to `0x10C`. Decide in the PR -whether `Unsupported` and `NotFetchable` mean "unknown" too, or need their own -handling, and record the reason. +Rust can refetch from upstream, so a skip there meant a failed refetch rather +than only an eviction. The original proposal mapped `NotFound` and `Old` to +`0x10C` and left `Unsupported` and `NotFetchable` for the PR to decide. Decided 2026-10-28 (maintainer): it starts after the open quests that edit the same publisher land. Those have landed: Rust FETCH parity in @@ -31,7 +56,7 @@ IETF fill timeout, which paths and has landed. A FETCH or fill now lists at most one group, so this marks that one group. -Tests: a listed group evicted before it is written, for FETCH on drafts 18 +Original test request: a listed group evicted before it is written, for FETCH on drafts 18 and 22 and for a draft-22 fill, each failing before the fix. Run `just test interop --all` if the framing order changes. Public API: none. Wire: none; the marker exists in both drafts. From 218ecef85e4b4a463b650214cc616dc003e08730 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sun, 1 Nov 2026 10:16:06 -0800 Subject: [PATCH 3/3] docs(quest): retire the superseded unknown-range marker quest The maintainer retired it on 2026-11-01. moq-dev/moq#7204 removed the listed-group loops it targeted: FETCH buffers its one group before FETCH_OK, and Rust and JS fills reset their stream on failure instead of skipping silently. Co-Authored-By: Claude Opus 5.5 --- quest/m1/README.md | 1 - quest/m1/ietf-publisher-unknown-range.md | 62 ------------------------ 2 files changed, 63 deletions(-) delete mode 100644 quest/m1/ietf-publisher-unknown-range.md diff --git a/quest/m1/README.md b/quest/m1/README.md index dfde045a690..13a1f1013ed 100644 --- a/quest/m1/README.md +++ b/quest/m1/README.md @@ -146,7 +146,6 @@ removed). - [moq-quic's API improves on quinn's](/quest/m1/quic-api/README.md) - moq-quic and both QUIC drivers ship one mirrored API: `send::`/`recv::` namespaces, one error per direction, consuming terminal operations, plain configs, no quinn baggage - [On-demand JavaScript FETCH](/quest/m1/js-fetch-on-demand.md) - browser publishers answer IETF FETCH for evicted or uncached groups through the JS ranges request surface - [Rust cancels an unclaimed fill head when a subscription ends](/quest/m1/ietf-fill-end-cancel.md) - SUBSCRIPTION_ENDED cancels, not finishes, a fill no group was sent for, as in JS -- [Rust marks a lost listed group unknown](/quest/m1/ietf-publisher-unknown-range.md) - the Rust IETF publisher sends End of Unknown Range for a listed group it can't serve, after the publisher's open quests land - [Native rung disable](/quest/m1/simulcast-rung-disable.md) - OBS stops sending the top renditions its grant cannot fund, as the Rust/FFI publishers do, and a shaped uplink through moq-ffi proves the resume - [Audio jitter target](/quest/m1/audio-jitter-target/README.md) - the playout target is default in both languages; a manual browser proof and a native trace replay remain - [A/V clock](/quest/m1/av-clock.md) - the audio playhead drives Sync.reference while audio plays, through per-track sync handles diff --git a/quest/m1/ietf-publisher-unknown-range.md b/quest/m1/ietf-publisher-unknown-range.md deleted file mode 100644 index 322f8ef7d51..00000000000 --- a/quest/m1/ietf-publisher-unknown-range.md +++ /dev/null @@ -1,62 +0,0 @@ -# [S] The Rust IETF publisher marks a lost listed group unknown - -## Goal - -When the Rust moq-transport publisher has listed a group in a FETCH answer or -a draft-22 fill but can no longer serve it, it sends End of Unknown Range -(`0x10C`) for that group on drafts 18 and 22, as the JS publisher does, instead -of skipping it silently. - -## Plan - -Inspection 2026-10-31: this plan predates the final implementation of -[moq-dev/moq#7204](https://github.com/moq-dev/moq/pull/7204). That change removed -both listed-group loops and the JS unknown-marker behavior. Rust's -`prepare_fetch` reads the sole group into an owned `FetchedGroup` before -`serve_fetch_stream` sends FETCH_OK; JS does the same with `readFetched`. -Eviction before acceptance refuses the request, while eviction after acceptance -cannot truncate the buffered answer. There is no remaining FETCH listing/write -race to reproduce on drafts 18 or 22. - -Draft-22 fills still acquire the selected head after opening FETCH_HEADER, but -both Rust `run_fill` and JS `#runFill` reset their own stream when the group is -unavailable. This is explicit failure, not the silent skip described below. -The merged PR records that fill-failure policy. Replacing it with an unknown -marker needs a new scope decision, including whether a missing head may count -as a successfully completed fill. - -`Unsupported` must remain a refusal: it can mean unsupported request shape or -an IETF group representation that FETCH cannot serialize. `NotFetchable` means -the sequence is held as a datagram, not that its existence is unknown. Before -FETCH_OK either error is returned as a request refusal; a fill resets its own -stream. Neither should be hidden as unknown without a separate decision. - -Recommendation to the parent: retire this quest as superseded by the settled -one-group implementation. If a fill marker is still wanted, first settle that -behavior for Rust and JS together. No production change has been made. - -Found 2026-10-28 by [moq-dev/moq#7150](https://github.com/moq-dev/moq/pull/7150), -which fixed the then-current JS publisher. The original Rust diagnosis was a -skip in two places: the FETCH answer loop in `serve_fetch_stream`, on -`NotFound | NotFetchable | Unsupported | Old`, and `run_fill`, when -`fetch_group` fails with the same errors. - -Rust can refetch from upstream, so a skip there meant a failed refetch rather -than only an eviction. The original proposal mapped `NotFound` and `Old` to -`0x10C` and left `Unsupported` and `NotFetchable` for the PR to decide. - -Decided 2026-10-28 (maintainer): it starts after the open quests that edit -the same publisher land. Those have landed: Rust FETCH parity in -[moq-dev/moq#6999](https://github.com/moq-dev/moq/pull/6999), and the -SUBSCRIBE properties opt-out in -[moq-dev/moq#7085](https://github.com/moq-dev/moq/pull/7085). A third was -IETF fill timeout, which -[moq-dev/moq#7194](https://github.com/moq-dev/moq/pull/7194) dropped for -[one group](https://github.com/moq-dev/moq/pull/7204), which edited the same -paths and has landed. A FETCH or fill now lists at most one group, so this -marks that one group. - -Original test request: a listed group evicted before it is written, for FETCH on drafts 18 -and 22 and for a draft-22 fill, each failing before the fix. Run `just test interop --all` if the framing order changes. - -Public API: none. Wire: none; the marker exists in both drafts.