Participant Relationship Protocol

Back to matrix

G02-LI: Yes

Rationale

An infrastructure-managed destination reattachment can preserve its EID while changing the serving ETR/RLOC registration. RFC 9301 updates the responsible Map-Server; remote ITRs obtain mappings on demand and refresh relevant caches through selective SMR or expiry and lookup. These external ITRs change their encapsulation destination, so this is not merely an unchanged external route. The individual binding need not be broadcast to every router or participant.

Assessment method

Primary documentation and pinned source review; no runtime experiment

Source context

RFC 9301 registration, selective SMR and on-demand mapping lookup

Outstanding qualification

Use the existing C01 witness: authorized ETRs, local delivery at the new attachment, already-routed old/new RLOC prefixes, stable mapping-system authority and finite cache TTLs. Registration, affected-site state and interested ITR caches change. SMR targets recent traffic partners and does not enumerate every cache; stale one-way or inactive caches may require expiry. Mapping-service replication and resolution paths remain part of the affected control scope. Moving underlay aggregates or mapping authority can require wider updates. This is an administratively managed capability, not autonomous endpoint mobility, instantaneous recovery or a global-capacity claim. No LISP-MN, LISP-SEC or Pub/Sub extension is added.

Public sources

Editorial evidence references

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