F23-YG: Yes
Rationale
A moving Yggdrasil node retains its key-derived IPv6 address while establishing new adjacent peerings. Routing resolves paths toward that identity independently of the underlying TCP/TLS peering addresses; the documented design explicitly handles node mobility. With the process, TUN interface and application UDP endpoint retained, path replacement need not recreate the application peer relationship. The witness uses reachable, preconfigured adjacent numeric peers in the selected private mesh; it does not import public peers or automatic peer exchange. This is architectural credit, not a measured handover or a guarantee that every interruption is survivable.
Assessment method
Primary documentation and bounded selected-profile inference; no execution
Source context
Yggdrasil implementation: identity and path recovery
Outstanding qualification
Using the pinned Ironwood composition, move one endpoint between two configured adjacent peers, preserving keys, TUN and UDP socket. Verify bidirectional delivery and unchanged IPv6 addresses; exercise stale paths, make-before-break, complete peering loss and recovery time.