C01-BL: Yes
Rationale
An administratively authorized Babel node can keep its locally provisioned IPv6 address or attached destination prefix while changing its physical neighbor attachment. It originates that same local route through the new eligible adjacency; Babel updates and route selection propagate a usable path to the unchanged destination. This supplies a constructive last-attachment witness without changing the sender's numeric destination or adding a host-mobility protocol.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
RFC 1122 weak-host semantics, configured IPv4 routes and Babel local-route origination
Outstanding qualification
The destination is on the same authorized Babel node or on its retained local link, and the new access admits that node's route origination. The address remains assigned and the destination prefix must be accepted by the relevant filters. No concurrent conflicting origin is introduced. This uses the column's general local-ULA Babel service; it does not assert that the separate G01 fixed-hierarchy filters admit arbitrary relocation. Reconvergence and stale-route removal are required; no timing bound or lossless session is guaranteed. Administrative route-origination authority is explicitly allowed for this C01 witness and is precisely why F23-BL remains No under its stricter ordinary-endpoint rule. Moving an unprivileged host between unrelated prefixes is not covered. No runtime experiment.
Public sources
- https://www.rfc-editor.org/rfc/rfc8966.html#section-3.7
- https://www.rfc-editor.org/rfc/rfc8966.html#section-1.1
- https://www.rfc-editor.org/rfc/rfc8966.html#appendix-E
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round536.html
- round536-sources.json