Participant Relationship Protocol

Archived criterion

F25-YG: 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 bounded configuration witness fits the 65,536-byte F25 budget. Three fresh Yggdrasil v0.5.14 / Ironwood d50055b runs deliver and byte-verify 256 useful bytes in each direction using the ordinary numeric IPv6/UDP API, pinned numeric TLS peering and independent Ed25519 keys. Linux TCP_INFO on the endpoint-facing relay socket reports stream-byte totals 7,385/7,361/7,123 and combined incoming/outgoing segment counts 44/42/38, with no retransmissions, unacknowledged or unsent data at the snapshot. TCP_MAXSEG=1200 yields measured send/receive MSS 1188. Map each trace to provisioned IPv4, untagged Ethernet MTU 1500, no losses, no DHCP/DNS or multicast peer discovery, and fresh ARP. Charge 20 IPv4 + 60 maximum TCP-header + 38 Ethernet byte-times per counted segment, add three complete handshake segments conservatively for listener counter omissions, and two 84-byte-time ARP frames. Totals are 13,099 / 12,839 / 12,129 byte-times, including startup, routing convergence, session establishment and both complete useful payloads. The largest is below 65,536.

Assessment method

Measured TCP stream and segment accounting plus a conditional loss-free Ethernet configuration model

Source context

Pinned upstream code; three ordinary-path successful local executions; Linux TCP_INFO counters and explicit Ethernet/ARP accounting

Outstanding qualification

Yes is a documentary low-latency single-peer configuration witness, not a physical Ethernet capture or universal upper bound. Actual execution is loopback; TCP bytes and segment counts are measured, while Ethernet/ARP and transfer of the observed loss-free packetization to the specified link are modeled. The opposite TCP relay leg is infrastructure outside the endpoint interface; the relay does not terminate TLS. Fresh cores stand in for retained valid keys/configuration with expired sessions/learned state, not a physical 24-hour sleep. Payload verification and a 300 ms settling window precede the snapshot; teardown after delivery is outside F25. The upstream routing-readiness wait plus three-second settling delay is not a convergence guarantee. A slower link, other peers, loss/retransmission, background traffic, dynamic addressing, VLAN/Wi-Fi, or different packetization needs a new budget. This credits no energy, global capacity, or runtime interoperability certification.

Public sources

Editorial evidence references

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