From a775274631dffde3451458ad7b1c9ed665900b0b Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sat, 7 Nov 2026 08:17:13 -0800 Subject: [PATCH 1/2] chore(quest): claim quest/m1/session-policy/README.md Quest-Claim: 57336650aa5712cc From 6c3d11bdc7a8ad767868434b680fb7cbaaee3b6f Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sat, 7 Nov 2026 08:18:39 -0800 Subject: [PATCH 2/2] quest: session policy lives in moq-net, finished moq-webrtc's data channel transport runs its sessions through Client::connect_with and Listener::accept_with (#8122), the last clause of the epic's Goal, so the epic is deleted along with every link to it and the held-epic prose that named it. Co-Authored-By: Claude Opus 5.5 --- quest/m1/README.md | 3 +- quest/m1/session-policy/README.md | 55 ------------------------------- quest/m2/README.md | 1 - quest/m2/recut-held.md | 3 +- 4 files changed, 2 insertions(+), 60 deletions(-) delete mode 100644 quest/m1/session-policy/README.md diff --git a/quest/m1/README.md b/quest/m1/README.md index 90202de1b48..330d3f102ac 100644 --- a/quest/m1/README.md +++ b/quest/m1/README.md @@ -25,7 +25,7 @@ because a downstream iGPU transcode trial needs it now. Held here by open claims: a quest's branch is its path, so a claimed quest cannot move until its PR merges, and an epic moves with its children. These breaking epics and quests stay in m1 for now and are listed in m2's -`Required`, so the cut still waits on them: api-audit, drop-set, rind, session-policy, and +`Required`, so the cut still waits on them: api-audit, drop-set, rind, and stream-credit. The [re-cut follow-up](/quest/m2/recut-held.md) moves what remains of them once their claims merge. @@ -48,7 +48,6 @@ moves what remains of them once their claims merge. - [Push-to-talk's press-to-audible latency fits a budget on the defaults](/quest/m1/push-to-talk-latency.md) - press to audible on the browser defaults, excluding device output, stays under a kixtop-measured budget that `just test push-to-talk` enforces - [Socket endpoints split into servers and clients](/quest/m1/socket-roles.md) - servers announce `.server/` and clients `.client/`, so plain grants keep a client from posing as a server or reading another client - [TS fidelity and recovery](/quest/m1/ts-reliability/README.md) - both modes have explicit profiles, automated validation, loss tests, and a dedicated guide -- [Session policy lives in moq-net](/quest/m1/session-policy/README.md) - accept and connect deadlines, admission, window widening and reconnect live once in moq-net; moq-tokio and moq-relay's io_uring path call them - [Vendor and trim the WebRTC stack](/quest/m1/webrtc-vendor.md) - str0m, dimpl, `is`, and sctp-proto live in moq-webrtc with unused code removed, so moq-webrtc can take rind - [MoQ on rind](/quest/m1/rind/README.md) - every MoQ crate takes its crypto from rind, a pure-Rust graviola fork, so no build compiles C crypto - [VA-API encode is correct on radeonsi](/quest/m1/vaapi-radeonsi.md) - AMD's VA-API H.264 encode decodes, or the node is refused for OpenH264 diff --git a/quest/m1/session-policy/README.md b/quest/m1/session-policy/README.md deleted file mode 100644 index 35c1253c768..00000000000 --- a/quest/m1/session-policy/README.md +++ /dev/null @@ -1,55 +0,0 @@ -# [M] Session policy lives in moq-net - -## Goal - -Session policy lives once, in moq-net. Accept and connect deadlines (spanning -SETUP, admission and the reply, closing with Timeout), the admission bound, -widening the receive window on admit, and reconnect with backoff come from -moq-net for tokio, io_uring and WebRTC sessions alike. moq-tokio keeps only -sockets, DNS, TLS, accept loops, the fallback runtime and spawning. The epic is -done when the WebRTC transport's session runs through the same policy. - -## Plan - -Planned 2026-11-04 with the maintainer, from the WebRTC consolidation draft -[moq-dev/moq#7804](https://github.com/moq-dev/moq/pull/7804), which asked -where moq-webrtc should plug its externally established transport in. The -maintainer asked what that means for io_uring and how much of moq-tokio belongs -in moq-net, and decided: - -- ✅ **Move the policy first**, then give moq-tokio thin handoffs - (`Listener::accept_with`, `Client::connect_with`), which moq-webrtc's - data channel transport builds on (#7804 closed unmerged). - Not chosen: a moq-tokio handoff now with the move later; moq-webrtc calling - moq-net directly with its own policy. -- ✅ **Reconnect is in scope**: the reconnect, backoff and GOAWAY candidate - walk move too, as a poll machine. Not chosen: leaving them in moq-tokio - until io_uring dials. -- ✅ **Fold** the m2 relay-serve-path quest into the io_uring path, which landed - in [moq-dev/moq#8082](https://github.com/moq-dev/moq/pull/8082), and the - poll-first server-machines quest into accept policy, which landed in - [moq-dev/moq#8003](https://github.com/moq-dev/moq/pull/8003). -- ✅ **Break moq-net's public API in m1**, before the cut, with MIGRATE notes. - Not chosen: additive APIs beside the old ones. - -Research (2026-11-04, `origin/main` at e6be13d5f8): - -- moq-tokio owns the accept deadline (`server.rs` `Setup::deadline`, - `within`, `Deadline::bound`, default 10 s in `listen.rs`) up to the SETUP - reply, which moq-net already bounds through `Handshake::with_deadline` - (`rs/moq-net/src/server.rs`), the connect - deadline (`client.rs`, default 30 s in `connect.rs`), receive-window holding - and widening on admit (`Request::ok`, `qmux_limits`), `Request` - construction per transport, and reconnect (`connection.rs` `Backoff`, - `Goaway`, `run`). All of it runs on `kio::clock`, so none of it needs tokio. - Only sockets, DNS, Happy Eyeballs, TLS, accept loops, `runtime::scope`, - spawning and WebRTC's own UDP socket are tokio-specific. -- moq-uring has no client side. -- Widening on admit needs a transport hook: moq-net's `transport::poll` - session exposes only `receive_window()`, while tokio QUIC, qmux and uring's - `web::Session` all have `set_limits`. Add a trait method whose default - reports unsupported, the same move [QUIC deadline](/quest/m5/quic-deadline.md) - plans for per-stream deadlines. -- moq-net stays poll-first and spawns nothing - ([libraries spawn nothing](https://github.com/moq-dev/moq/pull/6849)): - policy returns drivers and machines, and the caller spawns and does the I/O. diff --git a/quest/m2/README.md b/quest/m2/README.md index d99076ffdb2..2886459e317 100644 --- a/quest/m2/README.md +++ b/quest/m2/README.md @@ -182,7 +182,6 @@ quests that require them. - [Stream credit by priority](/quest/m1/stream-credit/README.md) - every stream opens through one priority entry point, and a higher-priority group takes over or resets a lower one when credit runs out (held in m1 by an open claim) - [Finalize moq-lite-07](/quest/m2/lite07-finalize.md) - when the maintainer cuts it, lite-07 negotiates as `moq-lite-07` and the next release ships it - [Unbounded groups](/quest/m2/unbounded-groups/README.md) - groups and frames lose their size caps; a group keeps a 32 MB tail, and readers behind it replay through paced flights or refresh -- [Session policy lives in moq-net](/quest/m1/session-policy/README.md) - accept and connect deadlines, admission, window widening and reconnect live once in moq-net; moq-tokio and moq-relay's io_uring path call them (held in m1 by an open claim) - [One typed WebTransport error per QUIC adapter](/quest/m2/web-error.md) - moq-tokio and moq-uring each expose one typed `quic::web::Error`, and uring's `quic::Error` loses its `Web` and `Http3` variants - [moq-quic drops inherited surfaces with no consumer](/quest/m2/moq-quic-unused-surface.md) - unused accept, connection, and stream-id surfaces leave moq-quic's public API before the cut - [Publish reports rendition stats as hang's type](/quest/m2/rendition-stats-type.md) - `Rendition.stats` and `Report.Writer` take the rendition stats schema's input type, so encoders write plain numbers diff --git a/quest/m2/recut-held.md b/quest/m2/recut-held.md index fbfb0dbe3b5..0ebd072421b 100644 --- a/quest/m2/recut-held.md +++ b/quest/m2/recut-held.md @@ -4,8 +4,7 @@ The epics that open claims held in place during the 2026-11-05 milestone re-cut sit where the re-cut's rules put them. What remains of api-audit, -drop-set, rind, -session-policy, and stream-credit moves from m1 to m2; and the +drop-set, rind, and stream-credit moves from m1 to m2; and the probe epic moves from m2 to m3. The "held" notes in the m1, m2, and cut gate READMEs are removed, along with each held entry's extra link from m2's or the gate's `Required`.