diff --git a/quest/m0/README.md b/quest/m0/README.md index 9c7ca8b9fa5..884cffb42f1 100644 --- a/quest/m0/README.md +++ b/quest/m0/README.md @@ -34,12 +34,16 @@ that a relay moves End of Track's Location and refuses imquic's End of Group status. The fixes below LOCATION_FILTER come from them and go ahead of Seattle. The cold-relay Largest stays compliant with INVALID_RANGE (decided 2026-10-08), and the deviations doc landed in #5022. +An imquic draft-22 rig (2026-10-08) hit LOCATION_FILTER and a clear +FIRST_OBJECT at object 0 (#5027); the [release line](/quest/m0/release-22/README.md) +backports both with moq-noq 1.3.4 so Seattle peers get a fixed 0.17.x. Identity: the [broadcast epoch](/quest/m0/broadcast-epoch/README.md) line gates the next release (decided 2026-10-03: #4741 resumes an un-epoched republish into the old broadcast and stalls its viewers). #4741 can merge to main, but no release ships until first-party -publishers mint epochs. +publishers mint epochs. Backport patches cut from `release` don't carry +#4741 and aren't gated (decided 2026-10-08). Liveness: a serve loop with work always ready never yields, which starved an FFI publisher's QUIC driver and fails hosted Interop's go lanes (found @@ -55,6 +59,7 @@ remain and no release waits on them. - [Serve budget](/quest/m0/serve-budget.md) - a kio task that always has work ready yields after a budget, so a fast publisher can't starve its own QUIC driver - [Draft-22 LOCATION_FILTER](/quest/m0/ietf-location-filter-22.md) - moqt-22 LOCATION_FILTER carries its type instead of a Length in Rust and JS, so a draft-22 peer reads our Next Object correctly +- [Draft-22 media on 0.17](/quest/m0/release-22/README.md) - a 0.17.x with the LOCATION_FILTER and FIRST_OBJECT fixes and moq-noq 1.3.4, before Seattle - [Capped stream END_OF_GROUP](/quest/m0/ietf-end-of-track-location.md) - a stream capped by the subscription's end Location never claims END_OF_GROUP; moving End of Track's Location is deferred - [End of Group status](/quest/m0/ietf-end-of-group-status.md) - an End of Group status on a stream whose header already marks the group's end is accepted, so imquic's last object per group arrives - [TRACK stream demand](/quest/m0/track-stream-demand.md) - a lite-05+ subscribe shows the publisher one `used` edge, not a flap between TRACK and SUBSCRIBE @@ -62,3 +67,4 @@ remain and no release waits on them. - [web-transport releases the qmux fixes](/quest/m0/qmux-credit-upstream.md) - waiting on moq-dev/web-transport#412 and #413 to merge and ship, which qmux credit bumps to - [qmux credit](/quest/m0/qmux-credit.md) - qmux returns connection credit for dropped and stopped streams and delivers its close frame, on both lines - [Broadcast epochs](/quest/m0/broadcast-epoch/README.md) - every first-party publisher that can restart mints a fresh route epoch, the newest wins a path, and only routes with the same epoch resume a subscription +- [moq-noq 2.0.2 on main](/quest/m0/noq-2.0.2.md) - `main` carries the max datagram size fix `release` gets in 1.3.4 diff --git a/quest/m0/ietf-location-filter-22.md b/quest/m0/ietf-location-filter-22.md index 04985e8e5d0..6241849c998 100644 --- a/quest/m0/ietf-location-filter-22.md +++ b/quest/m0/ietf-location-filter-22.md @@ -62,3 +62,6 @@ Public API: none. Wire: moqt-22 LOCATION_FILTER changes to the draft's form. - [#4847](https://github.com/moq-dev/moq/issues/4847) - draft-22 LOCATION_FILTER should drop the Length and carry the Location Filter Type +## Related + +- [LOCATION_FILTER backport](/quest/m0/release-22/location-filter.md) - cherry-picks this fix onto `release` for a 0.17.x before Seattle diff --git a/quest/m0/noq-2.0.2.md b/quest/m0/noq-2.0.2.md new file mode 100644 index 00000000000..7c8e86b7fe8 --- /dev/null +++ b/quest/m0/noq-2.0.2.md @@ -0,0 +1,13 @@ +# [XS] main builds on moq-noq 2.0.2 + +## Goal + +`main` depends on moq-noq-proto, moq-noq-udp, moq-noq, and web-transport-moq +2.0.2 instead of 2.0.1, so it carries the same max datagram size fix +(moq-dev/noq#28) that `release` gets in 1.3.4. + +## Plan + +2.0.2 was published to crates.io on 2026-10-08. Bump the root `Cargo.toml` +pins and `Cargo.lock`, the same as #4699 did for 2.0.1. Kept in m0 (decided +2026-10-08) so `main` and `release` don't drift on the noq fix. diff --git a/quest/m0/release-22/README.md b/quest/m0/release-22/README.md new file mode 100644 index 00000000000..06fd874515f --- /dev/null +++ b/quest/m0/release-22/README.md @@ -0,0 +1,39 @@ +# Draft-22 media on the 0.17 release line + +## Goal + +A 0.17.x moq-relay and a release-line `@moq/net` ship before Seattle interop +on 2026-10-12 with draft-22 media working both ways: the draft-22 +LOCATION_FILTER form (#4847), a clear FIRST_OBJECT at object 0 accepted +(#5027), and moq-noq 1.3.4. A draft-22 peer (imquic main 925e3d83) can +subscribe with any of the six filters and publish through the relay. + +## Plan + +Reported 2026-10-08 from an imquic draft-22 rig against moq-relay. On the +subscriber side the relay misreads LOCATION_FILTER and closes the session +("short buffer", "duplicate", "wrong frame size"). On the publisher side it +drops imquic's group 1, which starts at object 0 with FIRST_OBJECT clear, as +"a group with no head". Draft-18 works end to end. + +Decided 2026-10-08: + +- One 0.17.x carries all three fixes rather than two staggered patches. +- Each backport is its own PR onto `release` (CONTRIBUTING), so the noq bump + and #5027 can land while #4847 is still in progress on `main`. +- Rust and JS both, so the release-line `@moq/net` gets the fixes too. +- The broadcast-epoch release gate does not apply: these backports do not + carry #4741. +- Offer the reporter the `release` head for their rig once the children + land, but don't gate the cut on their result. + +This README's own work, after the children merge: bump `@moq/net` on +`release` (`/bump`), merge the release-plz PR it regenerates for the +backports (0.17.3; 0.17.2 already shipped, and #4944 predates the +backports), and send the reporter the branch. + +## Required + +- [noq 1.3.4 on release](/quest/m0/release-22/noq.md) - `release` builds on moq-noq 1.3.4 +- [FIRST_OBJECT backport](/quest/m0/release-22/first-object.md) - #5027 on `release`, Rust and JS +- [LOCATION_FILTER backport](/quest/m0/release-22/location-filter.md) - the draft-22 filter form on `release`, Rust and JS diff --git a/quest/m0/release-22/first-object.md b/quest/m0/release-22/first-object.md new file mode 100644 index 00000000000..6453aaa7131 --- /dev/null +++ b/quest/m0/release-22/first-object.md @@ -0,0 +1,15 @@ +# [S] Backport the clear FIRST_OBJECT fix to release + +## Goal + +A draft-18+ subgroup stream with FIRST_OBJECT clear whose first Object ID is +0 delivers its group on `release`, in `moq-net` and `@moq/net`, as #5027 did +on `main`. A clear bit with any other first ID is still dropped. + +## Plan + +Cherry-pick fdfdf9a45 (#5027) onto `release` as its own PR. `release` has +the same early drop in `rs/moq-net/src/ietf/` and in +`js/net/src/ietf/subscriber.ts` ("dropping a group with no head"). Adapt +where the two branches have diverged, and keep #5027's tests (first ID 0 +delivered, first ID 3 dropped, the next group still arrives). diff --git a/quest/m0/release-22/location-filter.md b/quest/m0/release-22/location-filter.md new file mode 100644 index 00000000000..e5ad1a31e9e --- /dev/null +++ b/quest/m0/release-22/location-filter.md @@ -0,0 +1,18 @@ +# [S] Backport the draft-22 LOCATION_FILTER form to release + +## Goal + +On `release`, moqt-22 LOCATION_FILTER is encoded and decoded with a Location +Filter Type and no Length, in `moq-net` and `@moq/net`, matching the fix on +`main`. Drafts 20 and 21 keep the length-inferred form. + +## Plan + +Cherry-pick the main PR as its own PR onto `release`. `release` lacks #5028's +per-draft 0x21 rework in `js/net/src/ietf/parameters.ts`, `fetch.rs`, and +`subscribe.rs`, so expect to adapt rather than apply cleanly. Keep the main +PR's byte-vector tests for every type. + +## Required + +- [Draft-22 LOCATION_FILTER](/quest/m0/ietf-location-filter-22.md) - the fix lands on `main` first diff --git a/quest/m0/release-22/noq.md b/quest/m0/release-22/noq.md new file mode 100644 index 00000000000..eedab97b08d --- /dev/null +++ b/quest/m0/release-22/noq.md @@ -0,0 +1,13 @@ +# [XS] release builds on moq-noq 1.3.4 + +## Goal + +`release` depends on moq-noq-proto, moq-noq-udp, moq-noq, and +web-transport-moq 1.3.4 instead of 1.3.3, so a raw QUIC peer without +datagram support gets a max datagram size of 0 instead of a panic +(moq-dev/noq#29). + +## Plan + +1.3.4 was published to crates.io on 2026-10-08. Bump the root `Cargo.toml` +pins and `Cargo.lock`, the same as #4702 did for 1.3.3. PR targets `release`.