Participant Relationship Protocol

Back to matrix

F16-PI: Yes

Rationale

For the final-peer access task, authenticated relationship policy is the native authority. Lifecycle sections 4–5 invalidate exclusively derived objects on revocation and forbid reusing the revoked epoch; sections 13 and 17 reject stale generations and unauthenticated mutation. This credits the specified protected relationship mechanism, not implementation conformance or protection of unrelated host services.

Assessment method

Documentary analysis; no protocol execution

Source context

Primary specification / explicit selected policy

Outstanding qualification

Bind the local final-peer allowlist to the actual selected carrier and E2E receiver; exercise denied identities, all active paths, queued-but-undelivered work, restart, stale epochs and renewed authorization. Working-draft lifecycle interoperability and full cutover execution remain unqualified.

Public sources

Editorial evidence references

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