Frando 149d5a8554 fix(proto): make permit_idle_reset per-path instead of per-connection
The `permit_idle_reset` flag controls whether sending an ack-eliciting
packet resets the idle timer (per RFC 9000 Section 10.1). Previously this
was a single bool on the Connection, shared across all paths.

This caused a cross-path idle timer contamination bug: receiving a packet
on the relay path (path 0) would set the global flag, and then a PTO
probe sent on a dead direct path (path 2) would consume it, resetting
the dead path's idle timer. This could keep the dead path alive
indefinitely, preventing fallback to relay.

Move the flag to PathData so that it is tracked per-path. Now receiving
on path A only permits idle reset when the next ack-eliciting packet is
sent on path A, not on unrelated path B.
2026-04-09 16:17:29 +02:00
2026-02-06 10:04:56 +00:00
2026-03-09 14:41:38 +01:00
2025-03-24 15:57:34 +00:00
2026-03-09 14:42:54 +01:00
2026-03-09 14:40:18 +01:00
2020-01-27 10:21:10 -08:00
2026-03-09 14:45:33 +01:00
2025-02-23 11:52:46 +00:00

noq

Documentation Crates.io Chat License: MIT License: Apache 2.0

General purpose implementation of the QUIC transport protocol in pure Rust. Noq is built as an async-friendly API in the noq crate on top of a sans-io protocol library in noq-proto.

Noq started out as a fork of the excellent Quinn project. The main focus of development has been towards adding support for more QUIC (draft) extensions:

Features

  • Easy to use futures-based async API.
  • Client and server server functionality.
  • 0-RTT and 0.5-RTT data support.
  • Ordered and unordered stream reads.
  • Custom and zero-length connection identifiers.
  • Fully pluggable crypto API with a Rustls implementation using ring or aws-lc-rs provided by default for convenience.
  • Broad platform support, including Linux, Windows, macOS, android, iOS and wasm.

Standards

The noq library aims to be correct implementation of various QUIC standards:

Getting started

Examples at https://github.com/n0-computer/noq/blob/main/noq/examples

$ cargo run --example server ./
$ cargo run --example client https://localhost:4433/Cargo.toml

This launches an HTTP 0.9 server over the QUIC transport on the loopback address serving the current working directory, with the client fetching ./Cargo.toml. By default, the server generates a self-signed certificate and stores it to disk, where the client will automatically find and trust it.

License

Copyright 2025 The quinn developers Copyright 2025 N0, INC.

This project is licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this project by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

S
Description
noq, a QUIC implementation in Rust
Readme 106 MiB
Languages
Rust 99.3%
Python 0.5%
Shell 0.2%