G02-LT: Yes
Rationale
A destination keeps its EID/node mapping while its final contact changes from A-to-D to B-to-D within a prepared region. Using the documented ION exit hierarchy, outside nodes retain an aggregate exit toward the regional gateway. Operators update contact information at the gateway and affected regional nodes, which recompute delivery toward B. The final route changes without distributing D's individual contact change throughout the network.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
SABR contact-plan handling and pinned ION regional exit routing
Outstanding qualification
The gateway must remain reachable, the regional plan must include usable contacts within bundle lifetime, and EID/node mapping must remain correct. SABR leaves plan distribution unspecified; this is an explicit local-administration witness, not automatic regional dissemination. Recompute invalidated routes after plan changes. Movement outside the prepared region or failure of its gateway may require broader updates. Retain provisioned LTP engine and Encapsulation/AOS channel mappings; LTP does not itself locate endpoints. No IP layer, complete executable integration or runtime result.
Public sources
- https://public.ccsds.org/Pubs/734x3b1.pdf
- https://github.com/nasa-jpl/ION-DTN/blob/154a4cc7354b26661169f8d8b75a4002cd509a9f/bpv7/doc/pod5/ipnrc.pod
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round570.html
- round570-sources.json