Back to matrix

G02-IL: Yes

Rationale

ILNP changes a mobile destination Locator while retaining its Identifier. RFC 6740 sections 5.1 and 6 send Locator Updates to active correspondents and update the relevant DNS records for future incoming sessions. Per-host changes do not require disseminating the new Locator to every router or every network participant.

Assessment method

Primary documentary reassessment; no runtime experiment

Source context

Pinned architecture/lifecycle source and ILNP experimental RFCs

Outstanding qualification

Use the selected overlapping authorized attachments and stable reachable correspondent. The new access prefix is already routed; local attachment state changes, correspondents receive updates, and authoritative DNS plus interested caches handle rendezvous. DNS update/cache delay and wider failures of routing aggregates remain; no zero-interruption, immediate cold discovery or constant global update-cost guarantee. This evaluates a moving destination, not merely an initiating client.

Public sources

• https://www.rfc-editor.org/rfc/rfc6740.html#section-6
• https://www.rfc-editor.org/rfc/rfc6743.html

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.

• round489.html
• round489-sources.json