C01-CG: Yes
Rationale
SABR can compute a route to the same destination node after its contact with one neighbor ends and a contact through another becomes usable. Constructive witness: the supplied plan ends A-to-D and provides B-to-D plus a feasible route to B. The singleton destination EID and its configured node-number mapping remain unchanged; only the contact sequence and convergence-layer attachment change.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
BP destination identity, TCPCL active-only polling and SABR contact routing
Outstanding qualification
This is planned destination reattachment, not merely alternate transit to an unchanged final contact. The plan must accurately represent the lost and replacement contacts, ranges, timing and capacity; unexpected loss requires corresponding plan correction or another usable planned opportunity. Contact-plan distribution and EID-to-node mapping are supplied by operators. No automatic mapping of every RFC 9758 encoding to historical CBHE is assumed: retain an explicit correct mapping for the configured private-domain EID. Numeric TCPCL contacts, NODE-ID trust and final-pair BPSec keys remain provisioned. Storage, expiration and connectivity limits apply. The Yes is documentary plausibility of ordinary singleton forwarding, not qualification of custody, critical metadata, a complete executable BPv7/SABR integration or a runtime handover test.
Public sources
- https://public.ccsds.org/Pubs/734x3b1.pdf
- https://www.rfc-editor.org/rfc/rfc9171.html#section-5.4
- https://www.rfc-editor.org/rfc/rfc9174.html#section-4.4.4
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round533.html
- round533-sources.json