G02-MT: No
Rationale
After a destination moves and a learned next hop fails, the selected recovery mechanism clears the next-hop preference and retries through managed flooding. That packet exposes the destination NodeID to eligible relays across its remaining hop horizon, including branches unrelated to the affected attachment or prior communication path. Replies can then establish new next-hop state. The mechanism does not confine discovery/update traffic to the changed region and relevant communication participants.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
Meshtastic managed-flooding recovery and next-hop learning
Outstanding qualification
No concerns the scope of attachment recovery, not the existence of mobility or C01 same-NodeID reachability, which remains Yes. This is not a claim that every node receives every packet or keeps a complete location directory. Hop limits, duplicate suppression and radio topology limit each flood, but do not select recipients by the changed region. A small neighborhood may recover locally by circumstance. No MQTT, regional directory or additional scoped-routing mechanism is selected; no airtime or scale experiment ran.
Public sources
- https://meshtastic.org/docs/overview/mesh-algo/
- https://raw.githubusercontent.com/meshtastic/firmware/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/NextHopRouter.cpp
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round564.html
- round564-sources.json