D03-MQ: Yes
Rationale
Pinned picoquic c124cbe975f71b150ea929d325804335d2bdaa34 implements QUIC and its multipath scheduler in userspace. Its Linux build uses C/C++, picotls and OpenSSL, and the socket adapter uses stock UDP/IP. The locally retained Release build and round227 experiment execute proactive cross-path repetition without adding a kernel component or a physical accelerator. An ordinary CPU and IP-capable NIC suffice; no dedicated radio, secure element or crypto accelerator is mandatory. The selected two paths require two usable IP routes, not specialized computing hardware.
Assessment method
Primary-document and source-scope analysis; no new full-stack execution
Source context
Primary evidence reviewed 2026-10-15; retained hashes in round228-sources.json
Outstanding qualification
Dependency finding only. Simulation is not live-network qualification, throughput evidence, unprivileged execution or full multipath-21 conformance. Positive path limits avoid the previously identified zero-limit negotiation deviation. D01 and E03 remain separate; this decision does not silently resolve them.
Public sources
- https://github.com/private-octopus/picoquic/blob/c124cbe975f71b150ea929d325804335d2bdaa34/README.md
- https://github.com/private-octopus/picoquic/blob/c124cbe975f71b150ea929d325804335d2bdaa34/CMakeLists.txt
- https://github.com/private-octopus/picoquic/blob/c124cbe975f71b150ea929d325804335d2bdaa34/picoquic/picosocks.c
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round226-runtime.json
- round227-runtime.json