F15-LP: Yes
Rationale
The selected libp2p QUIC transport retains QUIC Retry/address validation and pre-validation expenditure containment. These protect transport admission before libp2p stream/application work. The already documented ConnectionGater supplies an additional authenticated Peer-ID policy boundary; it is not treated as a zero-cost pre-handshake filter.
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
Credit the native QUIC Retry configuration at the transport boundary, not a new resource-manager deployment. Full-process quotas, protocol handler work and admission of many reachable peers require separate assessment. QUIC reachability validation does not establish Peer-ID authorization. No external firewall or new transport layer is added. 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://raw.githubusercontent.com/libp2p/go-libp2p/master/core/connmgr/gater.go
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