C06-LP: No
Rationale
libp2p over direct QUIC protects transport payloads, but the selected direct IP/UDP connection exposes the source and destination network addresses and UDP ports on each used path. The observer can associate the final communicating endpoints without decrypting application data or recovering a peer public key.
Assessment method
Header/encapsulation assessment under revised C06; no traffic capture
Source context
Primary RFCs and pinned protocol/implementation headers
Outstanding qualification
Connection-ID rotation, path migration and distinct identity keys do not conceal the address pair of the observed direct path. This is not a claim of unconditional cross-path linkage through a reused connection ID. No privacy relay, VPN or anonymity overlay is selected; authenticated peer identity and real-world identity are not required for the address-pair finding.
Public sources
- https://www.rfc-editor.org/rfc/rfc9000.html#section-12
- https://www.rfc-editor.org/rfc/rfc9000.html#section-9.5
- https://www.rfc-editor.org/rfc/rfc8200.html#section-3
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round490.html
- round490-sources.json