G02-BL: Yes
Rationale
An authorized destination node can reattach within a provisioned ULA region and originate its unchanged local prefix through the replacement adjacency. Regional Babel routers, including the ingress used by outside senders, update their selected path. Native prefix/interface filters suppress that specific route on outward interfaces while a separately provisioned covering aggregate remains advertised. External traffic therefore follows a changed regional route without requiring every router to learn the destination's individual attachment.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
RFC 8966 route updates and babeld 1.13 prefix/interface export filters
Outstanding qualification
Prepare both attachments, permit the origin and prefix inside the region, retain usable return routes and maintain the covering aggregate. Use babeld's outbound filters and explicit redistribution, not assumed automatic aggregation. The exact G01 fixed-tree configuration is not claimed to admit arbitrary moves. Ordinary unfiltered meshes and moves outside the prepared region may propagate changes more widely. Reconvergence, stale routes and withdrawal holds remain relevant. This requires routing authority; F23 remains unchanged. No daemon or mobility experiment ran.
Public sources
- https://www.rfc-editor.org/rfc/rfc8966.html#appendix-C
- https://www.rfc-editor.org/rfc/rfc8966.html#section-3.7
- https://github.com/jech/babeld/blob/babeld-1.13/babeld.man
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round562.html
- round562-sources.json