Participant Relationship Protocol

Back to matrix

D03-PI: Yes

Rationale

The inspected Linux IPv4/UDP binding uses ordinary networking facilities: AF_INET/SOCK_DGRAM sockets and kernel_sendmsg. The runtime supplies a preferred-suite software crypto callback, and libprp provides software ML-KEM/X25519 operations. No specialized radio, cryptographic accelerator, DPU or secure element is mandatory for this configuration. Additional software modules and setup privileges are distinct D01/D02 questions.

Assessment method

Read-only implementation and test-fixture inspection; no new runtime execution

Source context

Pinned runtime, core carrier and IP carrier source inventory in round203-sources.json

Outstanding qualification

No new physical-NIC, throughput, latency or end-to-end hardware qualification is claimed. Retain the selected 0x0202 and carrier when measuring performance; optional hardware acceleration is not credited as mandatory.

Public sources

Editorial evidence references

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