Participant Relationship Protocol

Back to matrix

F24-PI: Yes

Rationale

PRP architecture section 8.2 explicitly requires the DTN realization to negotiate participant availability windows, including short intervals, for energy-saving transmission and inactivity between communication opportunities. This supplies coordinated receiving opportunities rather than merely restarting a session after sleep.

Assessment method

Primary documentary assessment under revised criterion; no runtime experiment

Source context

Pinned PRP architecture worktree and IP RFCs

Outstanding qualification

Architectural capability credit, using the same documentary threshold as F27; not an implemented wake scheduler. The current worktree amendment is pinned separately from its base commit. Negotiation procedures, timing encodings, clock tolerance, update/expiry and control/cover behavior remain unspecified here. Carrier support is required. For PRP over IP, this does not schedule the underlying radio or suppress unrelated IP traffic. No radio wake precision, energy saving, preserved live session or guaranteed retained-packet delivery is demonstrated. Custody alone and old F24 reenrollment evidence are not the basis of this Yes.

Public sources

Editorial evidence references

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