Participant Relationship Protocol

Back to matrix

F27-PI: Yes

Rationale

The owner-identified architecture amendment, section 8.2, requires the PRP DTN realization to negotiate availability windows between participants, including short intervals, for energy-saving transmission and inactivity between communication opportunities. This explicitly supplies the architectural capability that F18 retention and F24 silent resumption do not assess.

Assessment method

Primary architectural or protocol evidence; distinguish specified capability from executable realization

Source context

PRP architecture section 8.2 amended worktree

Outstanding qualification

Architectural Yes based on the exact amended worktree source pinned in round460-sources.json, not the unchanged base commit. The amendment leaves negotiation procedures, timing parameters and wire formats to separate specification and makes realization carrier-dependent. Duration/spacing encodings, update/cancellation, clock tolerance, control/cover exceptions, waiting-data policy and interaction with session/key expiry are not established by this paragraph. No executable integration, preserved traffic keys throughout sleep or energy measurement is claimed. Over IP, a PRP-level window does not by itself coordinate the underlying radio or suppress unrelated IP traffic.

Public sources

Editorial evidence references

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