Participant Relationship Protocol

Archived criterion

F25-LT: Yes

Archived previous-definition assessment — revision 5.73. Retired in 5.82; excluded from the active matrix and counts. This historical verdict is not a current assessment.

Historical wake-traffic inventory (cutoff retired)

Rationale

A controlled short-contact witness completes the earlier LTP/AOS inventory. Charge 1,024 acquisition octets and 24 complete 1,028-octet AOS-plus-ASM units in each direction: 51,392 bytes total, below 65,536. The 48 units include twelve data/report/ack units and 36 idle units. Four initial idle units establish fresh frame synchronization; data occupy slots 5-8, reports slot 10 and acknowledgments slot 12. At one frame per second, <=0.1 s one-way propagation and <=0.1 s response processing leave causal guards and avoid a 20 s retransmission timer. A complete 256-byte useful payload is carried each way in the compact protected BP bundle; no application fragmentation assumption is needed.

Assessment method

Conditional documentary byte bound and executable timing arithmetic; no RF or full-stack execution

Source context

Primary LTP/AOS/Encapsulation and synchronization formats; explicit constructed short-contact schedule

Outstanding qualification

Yes is a bounded documentary plausibility result, not measured performance or a universal spacecraft-link bound. The constructed receiver must acquire within the explicitly charged 1,024-octet prefix and four initial idle frames; CCSDS does not guarantee that acquisition time. Provisioned short, loss-free links, rates/clocks, engine/channel mappings, contact plans and valid BPSec keys are retained after 24 h silence; LTP sessions and frame synchronization are fresh. All idle traffic through the scheduled stop is counted. Pin uncoded historical 131.0-B-3, mandatory FECF inside each 1,024-byte AOS frame, compact managed options and Encapsulation fill. No other traffic, reports, coding, retries or plan/key downloads. Longer acquisition, propagation or processing requires recalculation. Full BPv7/BPSec/LTP/Encapsulation/AOS executable integration and physical receiver validation remain unqualified; this decision does not resolve E03, D03, G05 or security testing.

Public sources

Editorial evidence references

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