G02-IP: Yes

Rationale

In the C01 private-IPv4 witness, a host retains a /32 while replacing its final access through router A with access through B. An ingress router outside those access links changes its host route from A to B; the administrator confines that route and its updates to the affected routing region. Other regions retain a covering route toward the ingress. Thus delivery state used for external traffic changes without distributing the individual host's new attachment throughout the network. RFC 1812 supports static routes and control over their propagation.

Assessment method

Primary documentation and pinned source review; no runtime experiment

Source context

RFC 1812 static-route export control and RFC 1122 weak-host attachment witness

Outstanding qualification

Preprovision both paths, retain the address on a logical host interface, permit weak-host reception and provide a return route. Authorized administrators must update the affected routes and prevent export of the /32 beyond the region. The covering route must remain valid. This is configured native routing, not ordinary address portability between unrelated providers or endpoint-controlled mobility. Cross-region movement may require wider changes. No Mobile IP, tunnel, DNS, globally advertised /32, automatic convergence or runtime result is credited.

Public sources

Editorial evidence references

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

round561.html
round561-sources.json