Participant Relationship Protocol

Back to matrix

G05-LP: No

Rationale

No for the selected IPv4/UDP/QUIC/libp2p composition, which explicitly excludes NAT. One connected, conventionally routed IPv4 namespace has at most 2^32 address values, fewer than the reference ten billion devices even before reserved ranges. Peer IDs and UDP ports distinguish peers or services but do not provide routable addresses for additional independently attached devices. Reusing private addresses in disconnected domains does not connect those domains. The selected direct numeric-peer composition contains no translating gateway or relay/addressing layer that removes this obstruction.

Assessment method

Selected-profile namespace and source-based resource bounds; no runtime experiment

Source context

RFC 791 section 3.1; existing LP selected-profile IPv4 and no-NAT binding

Outstanding qualification

This is a necessary-condition result for the currently selected global IPv4 profile, not a limitation of libp2p Peer IDs, QUIC or every libp2p deployment. IPv6 is a legitimate alternative but has not been silently substituted. An explicitly adopted IPv6 global witness would reopen this cell and require its routing/state argument, as already done separately for IP and Multipath QUIC. Multiple processes sharing one host address do not turn that host into multiple independently attached devices. No runtime or global performance claim.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.