F23-RA: Yes
Rationale
The mobile endpoint locally drives attachment and DIF enrollment across the configured providers while retaining upper application communication. The application does not reconstruct the relationship, and the procedure does not require the endpoint to administer provider routes or originate infrastructure prefixes.
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.
Public sources
- https://raw.githubusercontent.com/wiki/IRATI/stack/Tutorial-10%3A-DMM-two-providers-ARCFIRE-2018.md
- 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