# Mobility-Multihoming Duality
## 6 Results of Evaluation
### UDP Throughput  
Figure 10b on page 27 shows the throughput observed for the UDP mobility--multihoming scenarios. The throughput observed remained consistent, with outliers within \(\pm\)0.02 Mbps (\(\pm\)0.2%) of the target throughput of 10 Mbps. Again, some of this variation was due to the packet pacing used by iperf2 to maintain the target throughput. Figure 9: Plots showing packet delivery statistics of TCP and UDP over ILNP. Note that the y axis is in the range of 0.00–0.01, i.e., 0.00–1.00%. The box around the median value is invisible, as the results were consistent across the runs, and the rate remained near zero. In all cases, both the misorder and loss were very low and very consistent across multiple runs. Note that the different transmission characteristics and behaviours for TCP and UDP mean these metrics are not directly comparable. (**a**) TCP misordering ratio based on sequence numbers (data packets) and acknowledgement numbers received. Negligible misordering was observed. (**b**) TCP duplicate ratio based on sequence numbers (data packets) and acknowledgement numbers sent and received.No significant numbers of duplicate packets were observed in the sequence numbers or the acknowledgement numbers. (**c**) UDP packet statistics observed in mobility–multihoming duality scenarios with iperf2 UDP over ILNP. With all scenarios, both misordering and loss ratio remained low or nil. The small size of the box indicates that there was little to no variation across different runs. Figure 10: Plots showing the throughput for TCP and UDP over ILNP. Note that, due to the different protocols and their characteristics, these are not directly comparable to each other. (**a**) Throughput observed in the mobility–multihoming duality scenarios with iperf2 TCP flows over ILNP. Across all delay scenarios, the throughput remained near the 10 Mbps target with little variation, as shown by barely visible 25 th and 75 th percentile line of the box plot. Note that the \(y\) axis is in the range of 9.0–11.0 Mbps. The box around the median value is invisible, as the results were consistent across the runs, and the value remained near 10.2 Mbps. (**b**) Throughput observed in mobility–multihoming duality scenarios with iperf2 UDP flows over ILNP. The throughput remained consistent at around the 10 Mbps target with very few exceptions. Note that the \(y\) axis is in the range of 9.0–11.0 Mbps. The box around the median value is invisible, as the results were consistent across the runs, and the value remained near 10.1 Mbps. Figure 11: Plots showing the throughput and sequence numbers observed in typical mobility–multihoming duality iperf2 TCP scenario evaluations received at the CN. In each column, the top graph is throughput (faceted top to bottom as network aa, bb, cc, and aggregate). There was consistent aggregate throughput (bottom facet), with the expected throughput observed at the respective source/destination IL-V on each network (aa, bb, cc) as expected. The vertical dashed line shows the Locator Update (LU) message event. In each column, the lower graph is the TCP sequence number progression. This also showed consistent increase, indicating a consistent flow and delivery of packets. Figure 12: Plots showing the throughput and sequence numbers observed in typical mobility–multihoming duality iperf2 TCP scenario evaluations received at the MN. In each column, the top graph is throughput (faceted top to bottom as network aa, bb, cc, and aggregate). There was consistent aggregate throughput (bottom facet), with the expected throughput observed at the respective source/destination IL-V on each network (aa, bb, cc) as expected. The vertical dashed line shows the Locator Update (LU) message event. In each column, the lower graph is the TCP sequence number progression. This also showed consistent increase, indicating a consistent flow and delivery of packets. Figure 13: Plots showing the throughput and sequence numbers observed in typical mobility–multihoming duality iperf2 UDP scenario evaluations received at the CN.