ILNPv6 — selected stack

ILNPv6 / TCP with ILNP identifier-only transport binding (RFC 6740 and RFC 6741); IPv6-compatible packet format with distinct 64-bit Identifier and Locator semantics, not an outer IPv6 tunnel; RFC 6743 Locator Updates and RFC 6744 Nonce Destination Option; locally generated NIDs, Router Advertisements and neighbour discovery; DNS NID/L64 discovery per RFC 6742. Host mobility between authorized attachments with overlap, a stationary reachable correspondent, and unchanged NIDs during the TCP connection. No IPsec, TLS, CGA identity binding or multipath TCP selected. Experimental specification; executable composition not qualified. F37/F38: optional local AQM and independently administered DiffServ policies explicitly selected in the IPv6-compatible forwarding plane; Traffic Class retained, no extra outer IP tunnel. No RSVP/IntServ or application reservation added. F39 application witness: a well-behaved socket application retains a participant name and TCP service port; ILNP-aware resolution supplies the current Identifier-Locator vector. A local service listens on its assigned vector or wildcard. Host-local routing delivers to the co-resident service; remote delivery uses the same naming/socket model and identifier-bound transport. No application switch to localhost or AF_UNIX is required. The pinned public Linux ILNP prototype corroborates local-path plausibility; its static-hosts resolver setup is not claimed as a runtime validation of the selected DNS NID/L64 composition.

Official project website · Logo credits · Methodology and limits