Participant Relationship Protocol

Back to matrix

L02-MQ: Yes

Rationale

Noq supplies an implementation-scoped express patent commitment for native IETF QUIC and multipath code. Its pinned README identifies RFC 9000/9001/9002 and the QUIC multipath extension, and offers MIT OR Apache-2.0; noq-proto inherits that workspace license. Selecting Apache-2.0 invokes section 3 for contributor-controlled claims necessarily infringed by contributions alone or with the Work. Production paths.rs implements multipath PathId and per-path packet-number state; transport_parameters.rs encodes and parses initial_max_path_id. This binds the grant to relevant QUIC/multipath code rather than the unrelated 2014 Google QUIC disclosure or a cryptographic dependency.

Assessment method

Primary pinned implementation licensing and source-scope review; no runtime or patent clearance

Source context

Noq pinned README, workspace/crate manifests, production path/transport-parameter code; Apache-2.0 section 3

Outstanding qualification

Yes records the Apache-licensed Noq contributor Work, not a specification-wide patent promise for every implementation of multipath draft-21. Shared path-ID, packet-number-space and initial_max_path_id mechanisms establish relevance; exact draft-21 wire compatibility and complete feature conformance were not tested or inferred. Apache section 3 scope and patent-litigation termination remain applicable. No license from picoquic authors, whole UDP/IP/TLS dependency clearance, third-party patent clearance or performance result follows. Noq is an additional licensing witness, not a replacement for the selected transport profile or runtime evidence.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.