Identifier/Locator Network Protocol

The Identifier/Locator Network Protocol (ILNP) (RFCs) is a network protocol designed to separate the two functions of network addresses, the identification of network endpoints, and assisting routing by separating topological information from node identity. ILNP is backwards-compatible with existing IP, and is incrementally-deployable.

ILNP itself is an architecture with two different instantiations at present. ILNPv4 is ILNP engineered to work as a set of IPv4 extensions, while ILNPv6 is ILNP engineered as a set of IPv6 extensions.

At least 3 independent open-source implementations of ILNPv6 exist. University of St Andrews (Scotland) has a prototype in Linux/x86 and FreeBSD/x86, while Tsinghua U. (China) has a prototype in Linux/x86.

In February 2011, IRTF Routing Research Group (RRG) Chairs recommended that the IETF standardise ILNP (RFC 6115) as the preferred evolutionary direction for IPv6.

ILNP Specifications (RFCs)
  • ILNP Architectural Description (RFC 6740)
  • ILNP Engineering Considerations (RFC 6741)
  • DNS Resource Records for ILNP (RFC 6742)
  • ICMPv6 Locator Update Message for ILNPv6 (RFC 6743)
  • IPv6 Nonce Destination Option for ILNPv6 (RFC 6744)
  • ICMP Locator Update for IPv4 (RFC 6745)
  • IPv4 Options for ILNPv4 (RFC 6746)
  • Address Resolution Protocol (ARP) for ILNPv4 (RFC 6747)
  • Optional Advanced Deployment Scenarios for ILNP (RFC 6748)
gollark: It DOES return things.
gollark: These headers *do not make sense*.
gollark: For maximum authenticity, the actual over-the-airwaves one complete with probably a lot of static instead of their uncool internet stream.
gollark: But nothing else. Only BBC Radio 4.
gollark: I was considering adding an AutoBotRobot feature where it streams BBC Radio 4 into voice channels.

See also


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.