Participant Relationship Protocol

Archived criterion

F25-IL: Yes

Archived previous-definition assessment — revision 5.73. Retired in 5.82; excluded from the active matrix and counts. This historical verdict is not a current assessment.

Historical wake-traffic inventory (cutoff retired)

Rationale

A stationary ILNPv6/TCP endpoint can resume with fresh discovery and a fresh connection within a conservative 18,432-byte endpoint budget. Reserve twenty IPv6 access-control frames at 512 byte-times (10,240), two DNS queries and responses at 1,024 each (4,096), twelve TCP control frames at 256 each (3,072), and two 256-useful-byte TCP data frames at 512 each (1,024). The data envelopes include a 40-byte IPv6 header, a 16-byte ILNP destination-options header carrying a 96-bit nonce, up to 60 bytes of TCP header and 38 Ethernet byte-times: 410, below the allocated 512. Fresh nonces and identifier-only transport checksum binding are retained; this does not substitute an ordinary IPv6 TCP session.

Assessment method

Documentary byte accounting and source-role/lifecycle analysis; no runtime or legal clearance

Source context

Primary RFCs and pinned implementation sources; reviewed 2026-10-22

Outstanding qualification

Constructive configuration witness, not a measurement or universal bound. One retained local NID, unchanged valid locator/prefix, link-local address and configured numeric recursive resolver; one peer DNS name of at most 64 wire octets, one NID and one L64 answer, no alias chain, DNSSEC or additional security wrapper. Two separate UDP DNS queries allow both answers without relying on additional-section processing. The ordinary IPv6 resolver/bootstrap role is included in the endpoint budget. The twenty access frames cover two address checks (one DAD probe each), router solicitation/advertisement, two MLD reports for each of two solicited-node groups plus a query, and three NS/NA pairs; remaining slots are reserve. Provisioned lifetimes remain valid and delivery completes before periodic refreshes. Twelve TCP controls cover a fresh three-way handshake, independent acknowledgments and graceful close; do not retain a TCP session, nonce or learned neighbor entry across sleep. The unchanged locator needs no Locator Update or DNS update. No losses, fallback, unrelated traffic or retry; no cryptographic peer authentication is claimed. Existing mobility capability is unchanged but is not exercised by this stationary wake-up witness.

Public sources

Editorial evidence references

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