Participant Relationship Protocol

Archived criterion

F25-PN: Pending

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

The selected column still specifies wire-v4 with protected adjacency and E2E suite 0x0202. The effective wire-v4 document retains ONION and two-flight HS2. The author-approved no-ONION fast-path direction belongs to a separately described successor: the TPA proposal explicitly preserves the existing wire implementation and leaves successor encoding/migration unqualified. These are not interchangeable byte budgets. Rechecking legacy TLV widths for identity suite 0x0002 gives M1=1736 and M2=1778 bytes; two fresh exchanges total 7028 canonical HS2 bytes before framing. For 256 useful bytes split into two 128-byte directions, legacy OPEN/ACCEPT plus four E2E item headers, four RRL record headers and four list counts total 384 inner bytes. The older 640-byte candidate instead contained 512 useful bytes. Neither inner amount is a complete endpoint budget or automatically additive to historical link subtotals. The next source review locates an actual cover scheduler and padding policy: prp_session_cover_work_fn sends an empty two-byte RRL only for active adjacent TX sessions. For suite 0x0202 the unpadded protected unit is 30 bytes (12 nonce + 2 RRL + 16 tag). Its size is raised to the configured padding target, bounded by session capacity. The scheduler uses ceil(8*unit_bytes*10^9/cover_rate_bps) nanoseconds with a 1 ms floor, and schedules from the actual current time rather than replaying missed intervals. At a 256-byte target and 1024 bit/s, one stable TX adjacency sends at most 1+floor(T/2 seconds) automatic cover units over an active interval T. For one such adjacency in each direction and T=60 seconds, the conservative cover-only bound is 18228 native Ethernet byte-times or 19964 over IPv4/UDP/Ethernet. This is a conditional source-derived bound, not measured completion in 60 seconds. Native Ethernet discovery now has a concrete source witness: version 2 SOLICIT and ANNOUNCE payloads are 48 bytes. A received SOLICIT causes a unicast ANNOUNCE when the link is allowed; ANNOUNCE records TX_ADDRESSABLE and RX_OBSERVED with current member generation and lease. One bilateral discovery cycle has two solicitations and two responses, totaling 344 untagged Ethernet byte-times (4*(48+38)). The default scan interval is 10000 ms and advertised lease 30000 ms. On an isolated two-node link, starting with no queued discovery work, no manual solicitations, resets or withdrawals, a 60-second interval has at most 28 such frames under a schedule with spacing at least ten seconds: 2408 byte-times. This accounts for continuing periodic discovery, not just the initial exchange.

Assessment method

Native carrier source trace and conditional discovery-frame bound; no runtime execution

Source context

Effective sibling specification files pinned by path and SHA256 in round474-sources.json; successor files include uncommitted proposals, not all attributable to the observed HEAD or public mirror

Outstanding qualification

Native discovery is source-bound, not an unbounded unknown or a zero-cost assumption. The interval calculation assumes stable allowed attachments, one interface per node, no other discovery participants/traffic and at least 10-second actual scan spacing; a Linux timing realization must preserve that spacing. Local current-member context creation remains necessary after wake; a carrier ANNOUNCE proves no PRP identity and HS2 still authenticates the peer. The 60-second interval is not an execution result or guaranteed delivery time. The complete F25 sequence still needs actual admission, route/relation exchange multiplicity, protected useful-data wrapping and successful delivery time consistent with the positive cover policy from round475. No independent acceptance of integration or the no-ONION successor is inferred. This Ethernet-discovery count is not silently reused for the UDP/IP carrier.

Public sources

Editorial evidence references

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