# ARCFIRE: Experimentation with the Recursive InterNetwork Architecture
## 3 Scaling up RINA Networks
### Distributed Mobility Management  
The goal of this scenario is to validate the distributed mobility management [17] and multi-access capabilities [18] enabled by the layer structure and naming and addressing scheme of RINA. Part of these capabilities have already been illustrated in [7]: the Mobile Host--called User Equipment in this  
Figure 11: CDF of delay at systems CPE63 and CPE41, for multiple flows with different QoS requirements. Figure 10: Physical systems in the multi-layer QoS experiment. experiment (UE)--exploited multi-homing via two WiFi interfaces to preserve service continuity during handover (a strategy usually called _make before break_). Multi-homing has been demonstrated both to two base stations of the same provider and to two base stations of different providers. This experiment features a handover between different providers that use different access technologies (wired and WiFi), and also illustrates the capability of routing the traffic of different applications through the DIFs of different providers according to policies configured at the UE. A detailed explanation of how to set up the experiment, including a bill of materials, configuration files, scripts and steps that need to be carried out, can be found at the IRATI tutorial#11 [19]. Figure 12 shows a view of the physical systems involved in the experiment. Three Raspberry Pis play the role of WiFi Access Routers (ARs) of the mobile provider network. The three ARs are connected to an Edge Router (ER), which is connected to a Core Router (CR). The CR connects the service provider network to the Internet via an ISP (Internet Service Provider) router. The ER is connected to a Data Centre (DC) gateway, which provides access to a small service-provider owner DC with two servers. The bottom of the figure shows a fixed provider network, that provides fixed connectivity to the customer edge router (CPE). The fixed provider network is connected to the Internet via ISP2. Both ISP1 and ISP2 are connected to ISP3, which provides access to Server3. All these systems (except for the Raspberry Pis) have been deployed as KVM/QEMU Virtual Machines (VMs). A single UE device (a laptop) starts the experiment connected to one of the mobile provider's access routers. The user with the UE device is accessing two applications: one located at the edge datacenter of the mobile provider, running at _Server 1_ and reachable via the _Slice 1 DIF_; and the other one running at _Server 3_ and reachable over the _Internet DIF_. The user with the UE is travelling home and roams through the mobile provider wireless access routers executing two handovers: _ARI_ to _AR2_ and _AR2_ to _AR3_. When the user arrives home, it plugs its UE device to the cable that connects it to the fixed provider. The user has a policy configured in its UE device that, whenever the _Internet DIF_ is available through the home provider, this one must be used. Hence, the UE device executes a handover and now it uses the wired interface provider by the home provider to reach the _Internet DIF_. However, it continues connected to the mobile provider via the WiFi interface, since the home provider does not have access to the _Slice 1 DIF_. Figure 13 shows the organizations of IPC Process instances at the UE system, and how it evolves through the experiment lifetime. The UE has three shim IPC Processes: one to wrap each WiFi interface (_wlan0_ and _wlan2_) and one to wrap _VLAN 40_ on Ethernet interface _etth0_ (this one is the fixed interface to connect to the home fixed network). As the UE moves, the shim IPCPs over the WiFi interfaces leave  
Figure 12: Physical systems present at the distributed mobility management experiment. and join different DIFs (over the different WiFi networks provided by AR1, AR2 and AR3 respectively). During this time, the IPCP belonging to the _Mobile Network DIF_ (the blue one on Figure 13) changes its point of attachment to the different shim WiFi IPCPs, and different routing updates take place on the _Mobile Network DIF_ to signal these changes.