Back to matrix

S04-CG: Yes

Rationale

SABR consumes contact/range plans and local routing state; section 2.3 and annex B leave plan distribution outside its protocol rather than mandate a particular external operator. In the selected composition participants supply those plans, clocks, numeric peers, certificate trust and BPSec keys themselves. Bundle forwarding, TCPCL trust and route calculation can therefore remain under participant administration.

Assessment method

Documentary composition review; no new execution

Source context

Primary protocol documents and Linux v6.12 local management source

Outstanding qualification

The plan must be maintained and its updates secured. This is not automatic discovery, authority-free planning, or a verified BPv7/SABR executable integration. Public allocation and global reachability remain separate.

Public sources

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

Editorial evidence references

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

• round252-sources.json
• round249.html