Participant Relationship Protocol

Back to matrix

G05-IL: Yes

Rationale

Editorial plausibility inference: ILNPv6 forwards on aggregatable 64-bit Locators using IPv6 routing, while Identifier/Locator communication state belongs to active correspondents. DNS NID/L64 records distribute discovery through existing delegated authorities and caches. The namespace therefore does not require ten billion globally advertised host routes or a complete host directory in every router. Regional provider aggregation, distributed DNS service and finite peer working sets supply a credible route to the common population. This credits the selected TCP composition, without adding multipath transport, authentication or an overlay directory.

Assessment method

Primary documentary review and conditional architectural sizing

Source context

RFC 6740 sections 3.2 and 4.2–4.4; RFC 6741 host state; RFC 6742 NID/L64 and deployment; RFC 6743 updates

Outstanding qualification

Architectural inference, not a measured global deployment or implementation qualification. Use the common physical regional infrastructure and workload; no extra inter-region links or favorable substitute topology are assumed. The sizing examples are explicit planning assumptions, not measured record sizes, cache-hit rates or throughput. Place additional service capacity inside existing regional sites and charge its memory, replication and traffic. Arbitrary deaggregation, all-to-all simultaneous sessions, pathological churn and exhaustive path retention are not the witness. Actual skew, control traffic, certificate/DNS updates, CPU, failures and link provisioning need engineering sizing. The historical latency and memory references are not jointly certified. Existing implementation, independent-evidence and security cells are unchanged.

Public sources

Editorial evidence references

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