G02-RI: Yes
Rationale
A leaf retains its configured IPv6 address while changing its parent within the same RPL domain. In non-storing mode, its DAO reports the revised target/parent relationship to the root, which reconstructs the downward source route. The affected neighbors, forwarding path and root handle the update; unrelated nodes need not receive an individual location announcement. A sender elsewhere in the domain can still reach the same destination through the root, whose delivery state has actually changed.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
RPL non-storing DAO updates and 6LoWPAN registration
Outstanding qualification
Use the C01 witness: the same ULA remains valid, an eligible parent and provisioned link keys are available, registration succeeds and updated DAO state reaches the root. Keep the domain and aggregate reachability stable. This local leaf change does not require a global repair; other failures, root-triggered refreshes or version changes can have broader effects. Stale state, partitions and finite lifetimes can prevent delivery. No inter-domain mobility, bounded convergence, root-memory bound or integrated runtime qualification is credited.
Public sources
- https://www.rfc-editor.org/rfc/rfc6550.html#section-9.7
- https://www.rfc-editor.org/rfc/rfc6550.html#section-9.4
- https://www.rfc-editor.org/rfc/rfc6775.html#section-5.5
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round556.html
- round556-sources.json