Back to matrix

F24-CG: Yes

Rationale

Architectural capability with the supplied contact/range plans already selected for this composition. SABR defines contacts by sending and receiving nodes, start/end times and rate, and assumes communication plans known to participants. A planned final-hop contact therefore provides a known receiving opportunity; BP can retain bundles until that contact and routing accounts for its timing.

Assessment method

Primary specification and pinned code review; no runtime experiment

Source context

SABR contact plans, LTP operating schedules and BP/TCPCL

Outstanding qualification

Bounded witness: provision coherent plans to the sender, receiver and final-hop forwarder, and use the receiver operating schedule to activate its link for the corresponding arrival interval, including propagation delay, clock error and setup/drain guards. Local link management must enforce that schedule for data and required control traffic; SABR itself does not switch radios or distribute plans. Updates require consistent reprovisioning, and a missed contact can require rerouting or retention until another opportunity, subject to bundle lifetime and storage limits. This is a supplied-plan architectural capability, not negotiated windows (F27), an executable power-management integration, or measured energy saving.

Public sources

• https://ccsds.org/Pubs/734x3b1.pdf
• https://www.rfc-editor.org/rfc/rfc9171.html

Editorial evidence references

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

• round506.html
• round506-sources.json