Back to matrix

C01-IL: Yes

Rationale

ILNP binds the selected TCP communication to the Node Identifier, while the Locator may change. In the selected overlapping-attachment scenario, the moving destination learns the new Locator and sends Locator Updates to its correspondent before leaving the old attachment. The correspondent continues addressing the same Identifier through the new attachment without application redirection.

Assessment method

Primary documentary review and bounded selected-composition inference; no execution

Source context

HIP, ILNP, Babel and SCION specifications

Outstanding qualification

The stable destination reference is the Identifier, not an unchanged Identifier-Locator vector: the wire Locator changes. Credit covers an existing session with unchanged NIDs, overlapping authorized attachments and a stationary reachable correspondent. DNS updates serve future sessions but are not the mechanism preserving this communication. No simultaneous-movement or lossless-handover result is claimed.

Public sources

• https://www.rfc-editor.org/rfc/rfc6740.html#section-6.2
• 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.

• round494.html
• round494-sources.json