Participant Relationship Protocol

Back to matrix

D01-PN: Yes

Rationale

Architectural Yes, based on the author's explicit endpoint model and the inspected portable processing boundary. A native PRP endpoint is an ordinary user process owning its identity and relationship state. It exchanges complete PRP records through a provisioned system transport interface; receiving a complete record does not itself require a raw Ethernet socket or administrative network authority. The endpoint need not configure the carrier, routing or host-wide networking. Linux userspace is the examined architectural target. The portable session API separates record processing from transport callbacks. Requiring the endpoint itself to implement privileged Ethernet access conflated transport provisioning with routine endpoint operation. This is a capability assessment, not a claim that the current native Linux interface has already implemented this unprivileged path.

Assessment method

Author-confirmed architectural capability with retained implementation qualification

Source context

Owner clarification and approval, 2026-10-20; retained portable API and Linux privilege audits

Outstanding qualification

Author-confirmed architecture plus source-level separation, not an executed unprivileged native stack. The inspected Linux generic-netlink path requires GENL_ADMIN_PERM for session and TX operations; delegated receive access alone does not remove that restriction. That implementation remains unqualified for complete ordinary-user TX/RX and new-session operation. Privileged initial installation, carrier provisioning and any continuing privileged userspace mediator must be disclosed; no such mediator is silently counted as unprivileged runtime. The architectural witness requires a suitably scoped endpoint interface, not permission to transmit arbitrary raw frames. Tests with in-memory callbacks do not demonstrate native Ethernet, HS2, framing, MTU handling or the selected protected composition under a checked UID and capability set. No kernel code or security policy was changed.

Public sources

Editorial evidence references

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