G02-RA: Yes
Rationale
RINA limits mobility updates through nested DIF scopes. Attachment and address changes update routing and directory mappings within the affected DIF; higher scopes see only moves crossing their lower-DIF boundaries. The selected two-provider IRATI mobility mode explicitly hides within-provider handovers from the Internet DIF while maintaining bidirectional application flows.
Assessment method
Architecture, configuration and documented mobility-mode inspection; no new runtime test
Source context
ETSI RINA architecture report and IRATI configuration/mobility documentation
Outstanding qualification
Yes for the documented scoped-update mechanism, including destination reachability. It is not based merely on an initiating client reconnecting: lower-layer routes and mappings change while upper communication remains reachable. Boundary crossings can affect higher DIFs; a single flat global DIF would not provide this benefit. Convergence time and global workload capacity remain unqualified. See ETSI section 7.4 and Tutorial 10.
Public sources
- https://www.etsi.org/deliver/etsi_gr/NGP/001_099/009/01.01.01_60/gr_ngp009v010101p.pdf
- https://github.com/IRATI/stack/wiki/Tutorial-10:-DMM-two-providers-ARCFIRE-2018
- 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.
- round663.html