dignifiedquire
97dfe4329a
Two tests confirming no data blackout during network change: 1. Single-path replacement (open_first mode): replacement path inherits validated status from the still-alive old path. Stream data sent after network change arrives at the server without waiting for PATH_CHALLENGE round-trip. Verified by sending known bytes and reading exact match. 2. Mixed paths (relay + direct): data flows on the recoverable relay path while the non-recoverable direct path's replacement validates. Verified by sending known bytes and reading exact match on the server. These confirm noq avoids the "data blackout" gap identified in the picoquic comparison, using a different mechanism: open_first ordering ensures validation inheritance, and recoverable paths carry data during transition.
noq
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:
- Supports the core QUIC specifications:
- RFC 8999 - Version-Independent Properties of QUIC.
- RFC 9000 - QUIC: A UDP-Based Multiplexed and Secure Transport.
- [RFC 9001 - Using TLS to Secure QUIC].
- RFC 9002 - QUIC Loss Detection and Congestion Control.
- The standardised QUIC extensions:
- Draft extensions:
- qlog: Structured Logging for Network Protocols.
- QUIC Multipath.
- With experimental qlog support.
- QUIC Address Discovery (QAD).
- Using QUIC to traverse NATs (QNT).
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
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
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.