diff --git a/quest/a1/README.md b/quest/a1/README.md index 951db889..3bc0dae1 100644 --- a/quest/a1/README.md +++ b/quest/a1/README.md @@ -13,7 +13,6 @@ The Required list is ordered by priority. Independent children may proceed concu - [QMux send-rate filter](/quest/a1/qmux-rate-filter.md) - app-limited samples no longer lower the estimate, on main and 0.5 - [QMux send-rate filter on 0.5](/quest/a1/qmux-rate-filter-0.5.md) - backport for published moq-relay - [Dual-stack bind](/quest/a1/dual-stack-bind.md) - native clients bind by the server's address family -- [Router crypto features](/quest/a1/router-crypto-features.md) - interim aws-lc-rs/ring features on `web-transport` - [Rust crates on rind](/quest/a1/rind/README.md) - no C crypto outside Quiche - [Binding runtime coverage](/quest/a1/bindings/README.md) - independent language jobs - [Node idle configuration](/quest/a1/node-idle/README.md) - typed native input and Node options diff --git a/quest/a1/rind/README.md b/quest/a1/rind/README.md index 5c4e7a52..79d4f031 100644 --- a/quest/a1/rind/README.md +++ b/quest/a1/rind/README.md @@ -37,7 +37,3 @@ Decision prompts (✅ chosen): - [Noq on rind](/quest/a1/rind/noq.md) - Noq's rustls without ring, with rind keys - [iroh on rind](/quest/a1/rind/iroh.md) - iroh endpoint built with rind's provider - [QMux on rind](/quest/a1/rind/qmux.md) - TLS and WSS paths with no aws-lc-rs - -## Related - -- [Router crypto features](/quest/a1/router-crypto-features.md) - interim features that the Quinn child removes diff --git a/quest/a1/rind/quinn.md b/quest/a1/rind/quinn.md index effa0be7..fc683dde 100644 --- a/quest/a1/rind/quinn.md +++ b/quest/a1/rind/quinn.md @@ -12,7 +12,7 @@ Decided with the maintainer on 2026-11-06 (planning interview): - A public `web_transport_quinn::crypto` module implements quinn-proto's public crypto traits over `rustls::quic`: the session, `QuicClientConfig`/`QuicServerConfig` equivalents, packet and header keys, the Retry integrity tag (AES-128-GCM), the reset `HmacKey`, and the `HandshakeTokenKey` (HKDF). Retry, HMAC and HKDF come from rind. The session accepts any rustls provider with QUIC suites. Endpoints are built with `Endpoint::new` and an `EndpointConfig` from this module, since `Endpoint::client`/`server` need ring. - FFI and callers of `Client::new(endpoint, quinn::ClientConfig)` build their configs from this module. Document the migration from `quinn::crypto::rustls`. - Builders default to the installed process provider, else rind. A CPU rind refuses returns a new `UnsupportedCpu` error from the finishing methods. `rind::cpu::check()` runs before any rind primitive is built (the Retry, reset and token keys), even when an installed provider is used. FFI's client constructor, which builds configs from this module, runs the same check first and returns the refusal as a `WebTransportError`. `Client::default()` keeps its `with_system_roots().unwrap()` and documents that it panics on such a CPU. -- Remove `aws-lc-rs`/`ring` from web-transport-quinn, web-transport-ffi, and the router (the features from [router crypto features](/quest/a1/router-crypto-features.md)). Check that py/kt/swift and Node still build and pass their binding CI. +- Remove `aws-lc-rs`/`ring` from web-transport-quinn and web-transport-ffi, so the router no longer pulls aws-lc-rs in through its default dependency. Check that py/kt/swift and Node still build and pass their binding CI. - Test interop against an unmodified quinn peer on aws-lc-rs: handshake, Retry, stateless reset, key update, 0-RTT rejection, and a CPU-refusal path. Use controlled time where the protocol allows. - The adapter is deleted once upstream allows any provider; see [Quinn adapter removal](/quest/a2/quinn-adapter-removal.md). diff --git a/quest/a1/router-crypto-features.md b/quest/a1/router-crypto-features.md deleted file mode 100644 index 626ad214..00000000 --- a/quest/a1/router-crypto-features.md +++ /dev/null @@ -1,25 +0,0 @@ -# [XS] Forward crypto-provider features through the router crate - -## Goal - -Native users of `web-transport` can build the router on `ring` instead of aws-lc-rs: the crate gains `aws-lc-rs` (default) and `ring` features that pass through to web-transport-quinn, and they do nothing on WASM. - -## Plan - -Decided with the maintainer on 2026-11-06 (planning interview): - -- Forward `aws-lc-rs` and `ring` to `web-transport-quinn` with its default features off. -- With neither feature on, the native `ClientBuilder` disappears, mirroring web-transport-quinn's gate. Session and Server conversion still compile, so callers can build web-transport-quinn clients themselves (for example with `Client::new` and quinn's own rustls features). No `compile_error!`. -- With both features on, behave as web-transport-quinn already does: an installed process provider wins, else the builder panics. Document both the neither-feature rule and the both-features rule in the crate docs; changing web-transport-quinn's rule is out of scope for this interim change. -- These features are interim. [Quinn on rind](/quest/a1/rind/quinn.md) removes them when the router moves to rind. Ship this anyway: the reporter gets an option without aws-lc-sys sooner (ring still builds C and assembly through `cc`), and the churn is accepted. If the rind switch lands first, delete this quest instead. -- Check that the WASM build still compiles with each feature combination. - -Decision prompts (✅ chosen): - -- Goal: ✅ forward features / fold into #135 quest / won't fix. -- Neither feature: ✅ gate ClientBuilder / `compile_error!`. -- After rind was planned: fold into rind / ✅ ship interim features. - -## Closes - -- [#477](https://github.com/moq-dev/web-transport/issues/477) - the forwarded features answer the request