# Mobility-Multihoming Duality
## 2 Combined Mobility and Multihoming
### Other Approaches
\begin{table}
\begin{tabular}{c c c c c c c c} \hline \hline
**Criterion** & **LISP** & **MIPv6** & **Shim6** & **DIME** & **HIP** & **MP-TCP * ** & **QUIC * & **ILNP** \\ \hline FUNCTION & & & & & & & & \\ Addressing & IP (EID, RLOC) & IP (HoA, CoA) & IP (ULID, Loc) & IP (HID, Loc) & HI, IP (Loc) & IP & IP & NID, \\ Layer & **3** & **3** & **3+** (shim) & **3+** (shim) & **3+** (shim) & **4** & **4** & **3** \\ Mobility & + & ✓ & + & ✓ & + & + & – & ✓ \\ Multihoming & ✓ & – & ✓ & + & + & – & **-** & ✓ \\ \hline CHANGES & & & & & & & & \\ Host & **N** & **Y** & **Y** & **Y** & **Y** & **Y** & **N** & **Y** \\ Applications & **N** & **N** & **N** & **N** & **Y** & **Y** & **Y** & **N** \\ Network & **E,P** & – & **F** & **F** & – & – & – & – \\ New Entities & **3,T** & **3,T** & **N** & – & **A,3,T** & – & **A** & – \\ \hline FUNCTION & & & & & & & & \\ Addressing & How addresses and addressing are used. \(\tt{IP}\) is \(\tt{IP}\) address\(\tt{id}\), & & & & & & \\  & & & & & & & & \\  & & & & & & & & \\ Layer & Which layer is modified & & & & & & & \\  & & & & & & & & \\  & & & & & & & & \\  & & & & & & & & \\ Mobility & How mobility is supported & & & & & & & \\  & & & & & & & \\  & & & & & & & \\  & & & & & & & \\  & & & & & & & \\ Multihoming & How multihoming is supported & & & & & & \\  & & & & & & & \\  & & & & & & & \\  & & & & & & & \\  & & & & & & & \\  & & & & & & & \\ \hline CHANGES & & & & & & & \\ Host & **Y**es or **No** : host needs to be updated. & & & & & & \\ Applications & **Y**es or **No** : APIs and/or applications need to be updated. & & & & & \\ Network & Existing network **Functions or **E**rotocols & & & & & & \\  & need to be updated. & & & & & & \\ New entities & New entities for **Application** layer, Layer **3** & (network), & & & & & \\  & & & & & & & \\  & & & & & & & \\  & & & & & & & \\ \hline LISP & Overloads IP address usage, needs new network entities, control plane protocols, & & & & & \\  & and tunnelling. & & & & & & \\ MIPv6 & Overloads IP address usage, needs to network entities. & & & & & \\ Shim6 & Overloads IP address usage, needs Shim layer for **U**LID/Loc mapping. & & & & & \\ DIME & Overloads IP address usage, needs NAT-like function for **HID**/IP mapping. & & & & & \\ HIP & Needs public keys to generate secure **H** values, needs new network entities, & & & & & \\ applications need to be modified. & & & & & & \\ MP-TCP & Transport layer only. & & & & & & \\ QUIC & Transport layer only, new API, needs applications to be modified. & & & & & \\ ILNP & Network layer, no tunnels, proxies, or address translation; no modification to APIs & & & & & \\  & or applications. (See Section 3.) & & & & & & \\  & & & & & & & \\  & & & & & & & \\ \hline \hline \end{tabular}
\end{table} 
Table 1: A summary of different mobility and multihoming solutions. distribution and management between network sites. The EVPN can provide multihoming and also provides mobility for nodes based on the management of Media Access Control (MAC) address values for those nodes between network sites. There is clearly a significant control plane overhead for managing the state across an EVPN. ILNP does not have such state management overhead, using only a simple, end-to-end control plane protocol.