# Mobility-Multihoming Duality
## 5 Evaluation of Mobility Multihoming Duality
### Experimental Methodology  
New L64 values detected via IPv6 RAs can be VALID or ACTIVE states within the ILCC. A VALID state for an L64 value means that it is available for use, but it is not currently in use. The ACTIVE state means that the L64 is in use. It is possible for more than one L64 to be ACTIVE--an \"overlap\" period for the use of the networks to which the L64 values refer.  
When multiple L64 values are ACTIVE, multiple networks are in use. Our implementation uses a host-wide load balancing, with a Deficit Round-Robin (DRR) [51] mechanism on both the source and destination L64 selection. This allows both send and receive to happen on the ACTIVE L64s present on the MN. In addition, this includes a mechanism to disable network interfaces from the communication on the host by listing them in a list of disabled interfaces. This mechanism gracefully removes the L64s associated with those interfaces included on the disabled interface list. This is done by notifying the CN of the new set of L64s using LU messages, allowing those interfaces to be disconnected without the loss of packets or disruption to the communication.  
The following describes how each stage is performed:  
1. **Adding an L64** In an ongoing communication between two hosts, the ILCC holds one NID and one L64, starting on the network aa. Upon adding a new L64 on the MN, the following steps take place: 1. The layer 2 'link-up' occurs at the new interface on the MN. 2. An IPv6 RA is received at the MN. 3. ILNP adds the new prefix as an L64 in the local ILCC at the MN, and it sets the new L64 as VALID. 4. On the L64 currently in use, the MN sends to the CN an LU containing two L64s: the new L64 and the one that is currently in use. 5. The MN sets the new L64 as ACTIVE, and it begins sending from it. 6. The CN receives the LU on the known L64, and it updates its ILCC entry for the MN with the additional L64. 7. The CN sends a LU-ack to the MN's newer L64, and it begins sending to the MN's new L64. 8. The MN receives the LU-ack from the CN. 2. **Removing a L64** With an ongoing communication utilising multiple L64 values between two hosts, the following steps take place to gracefully remove an L64. 1. On the MN, using the ILNP sysctl interface entry, add an interface to be removed from the communication to the disabled interface list. 2. The MN identifies the L64 belonging to the interface and sets its state to VALID.  
\begin{table}
\begin{tabular}{l c} \hline
**Parameter** & **Value [s]** \\ \hline max-interval & 5 \\ min-interval & 3 \\ valid-lifetime & 15 \\ preferred-lifetime & 9 \\ \hline \end{tabular}
\end{table}
Table 6: Lifetime and interval settings of IPv6 Router Advertisements (RAs) on access networks provided by R1, R2, and R3.  
\begin{table}
\begin{tabular}{c c c} \hline
**Network** & **Router** & **ILNP L64 Value** \\ \hline aa & R1 & 2001:2:aa:aa:a::1/64 \\ bb & R2 & 2001:2:bb:bb:b:/64 \\ cc & R3 & 2001:2:cc:cc:/64 \\ dd & R4 & 2001:2:dd:dd::/64 \\ \hline \end{tabular}
\end{table}
Table 5: IPv6/ILNP configuration for evaluation testbed. The ILNP L64 is an IPv6 prefix.  
3. The MN sends an LU with all ACTIVE L64s: that is, without any L64 values that belong to an interface in the list of disabled interfaces in step 2a.
4. The CN receives the LU with the new L64 values, and it sets the state of the removed L64 as VALID in the L64 entry for the MN.
5. The CN sends an LU-ack to the MN's L64 that is included in the LU.
6. The MN receives the LU-ack, and it can now turn off the interface.