F09-MQ: Yes
Rationale
The existing architectural Yes now has a bounded executable witness: the pinned picoquic combined mutual-authentication test negotiated multipath, validated two paths and completed a content-checked transfer. The final server qlog recorded 835 sent STREAM frames on path 0 and 757 on path 1 in the same connection, with both paths used during the transfer.
Assessment method
Documentary capability supplemented by bounded executed evidence
Source context
Multipath-21 and executed pinned picoquic simulated-network witness
Outstanding qualification
Retained evidence is from upstream simulated links, not physical independent carriers. No throughput, scheduler optimality, global scale, shared-bottleneck fairness or external interoperability claim. The 41 cross-path repeated ranges also show duplication during this execution, without proving every duplicate was proactive or every payload was duplicated. General capability remains defined by multipath-21; the known positive-limit configuration qualification is retained.
Public sources
- https://www.ietf.org/archive/id/draft-ietf-quic-multipath-21.html#section-5.5
- https://github.com/private-octopus/picoquic/blob/c124cbe975f71b150ea929d325804335d2bdaa34/picoquictest/multipath_test.c
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round295-runtime.json
- round295-sources.json
- round295_quic.c