Participant Relationship Protocol

Back to matrix

F15-BP: Yes

Rationale

The selected TCPCL/TLS composition requires certificate NODE-ID validation before completing session establishment; failed or missing required identity terminates the session. For the subsequent BP acquisition boundary, pinned ION provides configurable aggregate inbound ZCO heap/file occupancy limits. bpContinueAcq reserves space before appending an extent; unavailable space causes waiting or a congestive/discard path. This documents peer admission combined with bounded accounted bundle-storage allocation.

Assessment method

Primary documentation and pinned source review; no runtime experiment

Source context

RFC 9174 NODE-ID admission and pinned ION inbound ZCO reservation

Outstanding qualification

Require TLS, local certificate trust and authenticated NODE-ID, with certificates issued only to accepted neighbors; configure finite inbound heap/file budgets. These quotas cover accounted inbound ZCO storage, not all process memory, pending reservation metadata, sockets, concurrent TLS handshakes or CPU. maxAcqInHeap alone merely selects heap versus file and is not the aggregate bound. An authenticated relay may carry unauthorized final sources or exhaust the shared quota. BPSec remains a separate origin/content check. Evidence combines TCPCL normative ordering with ION storage-source behavior; no complete adapter integration, executable composition or overload service guarantee is claimed. No new protocol layer or external limiter is added.

Public sources

Editorial evidence references

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