C01-RI: Yes
Rationale
Within the configured RPL domain, a leaf can keep its provisioned IPv6 destination address when its old parent adjacency fails and an eligible alternative parent becomes reachable. DAO Target and Transit Information separate the destination address from its parent relationship. Updated path information lets the non-storing root rebuild its downward source route to the unchanged target; the sender does not need an alternative destination address.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
batman-adv translation-table roaming and RPL DAO target/parent separation
Outstanding qualification
Bounded composition witness: the same ULA remains valid across both attachments in the same configured domain; link access and keys are provisioned for the replacement neighbor, OF0 admits a valid parent, and required 6LoWPAN registration succeeds. DAO information must reach the root and stale path state must be repaired before delivery. A fresh DTLS handshake or retransmission is allowed. This is a last-hop parent change, not just transit failover. No movement to an unrelated prefix/domain, address conflict, permanent partition, bounded handover latency or uninterrupted session is covered. Registration failure and finite route lifetimes remain real limits. This is documentary plausibility, not a claim of a tested integrated implementation.
Public sources
- https://www.rfc-editor.org/rfc/rfc6550.html#section-9.4
- https://www.rfc-editor.org/rfc/rfc6550.html#section-9.2
- 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.
- round532.html
- round532-sources.json