F15-MQ: Yes
Rationale
QUIC supplies address validation with Retry tokens, allowing a server to defer connection state, plus a pre-validation response-byte cap. It also defines bounded cryptographic buffering and stream/data limits. Configured Retry therefore provides an admission gate and expenditure containment at the QUIC setup boundary; multipath does not remove that base mechanism.
Assessment method
Primary specification and source analysis; experiments are complementary
Source context
Selected-profile primary sources and retained source traces; owner-approved F15 reformulation
Outstanding qualification
Retry must be enabled for the stateless-admission witness. Address validation proves return reachability, not final-peer identity authorization; the selected TLS policy remains separate. The amplification cap alone is not a CPU or global-memory guarantee. Multiple path states, UDP ingress and authorized connection floods remain separate assessment targets. Quantitative service preservation under bounded attacks is complementary validation, not a prerequisite for this architectural criterion. Historical round145 and later experimental records retain their original scope; they are not new pass/fail results under this definition. F15 now assesses CPU/state protection only. Network-capacity authorization is separate in F26; a response-byte cap by itself does not establish this F15 result.
Public sources
- https://www.rfc-editor.org/rfc/rfc9000.html#section-8
- https://www.rfc-editor.org/rfc/rfc9000.html#section-7.5
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round445.html
- round445-sources.json
- round446.html