C01-RA: Yes
Rationale
The configured upper IPC endpoint ue.internet keeps address 1 in internet.DIF while its lower provider attachment changes. Enrollment through the new provider and link-state forwarding permit return traffic to reach that same address after the old attachment is disconnected; application redirection or an externally supplied replacement address is unnecessary.
Assessment method
Primary tutorial, configuration and implementation-source assessment; no execution
Source context
IRATI native bootstrap and two-provider mobility documentation
Outstanding qualification
Documentary and source-level evidence, not a local rerun. The witness uses a configured two-interface make-before-break handover. Abrupt outage recovery, lossless operation, simultaneous movement of both peers and arbitrary provider admission are not established. Local privileged setup is disclosed; it is not infrastructure route-administration authority. This is an inference from the stable address configuration and documented bidirectional echo-flow continuity, not a separate forced-failure test.
Public sources
- https://raw.githubusercontent.com/wiki/IRATI/stack/tutorial10/ue/internet.dif
- https://raw.githubusercontent.com/wiki/IRATI/stack/tutorial10/ue/ipcm.conf
- https://raw.githubusercontent.com/wiki/IRATI/stack/tutorial10/ue/internet.dif
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/rinad/src/ipcm/addons/mobility-manager.cc
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round658.html