What is it about?
The Identifier-Locator Network Protocol (ILNP) provides a different approach to mobility which can be implemented by modifying the end-systems only. We show how the TCP code in the Linux kernel can be extended allowing legacy TCP applications that use the standard C sockets API to operate over ILNP without requiring changes or recompilation. Our direct testbed performance comparison shows that ILNP provides better host mobility support than Mobile IPv6 (MIPv6) in terms of session continuity, packet loss, and handoff delay for TCP.
Featured Image
Photo by Rodion Kutsaev on Unsplash
Why is it important?
This approach does not require any changes to the network -- indeed, the network is not "aware" of the mobility, as it is implemented by direct communication between end-systems.
Perspectives
This shows that you can make end-system mobile without modifying the network, or introducing new entities into the network (such as middleboxes), and using only the existing unicast routing (no "mobile-aware" routing is required).
Prof Saleem N Bhatti
University of St Andrews
Read the Original
This page is a summary of: End-To-End Mobility for the Internet Using ILNP, Wireless Communications and Mobile Computing, April 2019, Hindawi Publishing Corporation,
DOI: 10.1155/2019/7464179.
You can read the full text:
Resources
Contributors
The following have contributed to this page
