C01-LI: Yes

Rationale

LISP separates the destination EID from RLOCs naming network attachment points. An authorized destination-site reattachment can preserve the EID while replacing the serving RLOC mapping. Map registration, lookup and cache-update mechanisms allow the sender's ITR to encapsulate toward the new RLOC without requiring the sending application to substitute its destination EID.

Assessment method

Primary specification review; no runtime experiment

Source context

LISP RFC 9300 and RFC 9301 mapping and attachment semantics

Outstanding qualification

Bounded infrastructure-managed witness: provision the same destination EID behind an authorized serving ETR at the new attachment, ensure local delivery and underlay reachability, update the Map-Server registration, and refresh the source ITR cache through the defined mapping procedures. This changes the destination's EID-to-attachment binding rather than only repairing transit to one unchanged locator. The mapping service returns encapsulation locators to the ITR, not a replacement destination for the application. Administrative authority and convergence are required; stale caches and unavailable control services can prevent recovery. No arbitrary host roaming, LISP-MN, LISP-SEC or uninterrupted session is credited. F23-LI remains No for autonomous mobility of the selected ordinary endpoint.

Public sources

Editorial evidence references

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

round529.html
round529-sources.json