Participant Relationship Protocol

Back to matrix

F05-MQ: Yes

Rationale

The selected composition already includes mutual TLS authentication, locally trusted peer certificates and an explicit final-peer key allowlist (F16-MQ), with resumption and 0-RTT disabled. Retain that admission policy independently of QUIC connections. A new connection from another reachable attachment must prove the same admitted key in a fresh TLS handshake before delivery. The retained allow/deny decision supplies the authorization context; certificate stability alone does not. RFC 9001 section 4.4 provides QUIC peer authentication through TLS, while RFC 8446 separates credential verification from access control. The old No considered only connection state and resumption and omitted the selected policy.

Assessment method

Consistency correction using primary specifications; no runtime execution

Source context

QUIC/TLS peer authentication and the already selected local admission policy

Outstanding qualification

Documentary capability under explicitly retained local policy, using the same boundary as F05-HIP and F05-RI. It is not a default guarantee for arbitrary QUIC deployments. Keep admission records across connection teardown, enforce them in each fresh handshake and deny unlisted peers before application delivery. Provisioning, reachable numeric peers and carrier attachment remain prerequisites. No live handover, automatic identity discovery, crash-persistence, complete multipath-21 conformance or new runtime test is claimed. This corrects No to Yes; it does not close a previously Pending cell, alter the selected composition or add a new application authentication layer.

Public sources

Editorial evidence references

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