PROTOCOL NOTES / 09
Handoff & recovery
Prepare a new path without confusing intent with commitment.
Android and iOS software implemented · Apple Wi-Fi Aware, Bluetooth LE and mixing tested on hosts and emulators only · Physical qualification pending
Changing parent is a transaction
Discovery preference alone cannot move a live voice path. RWCP prepares a candidate, proves reachability in both directions, activates an exact transaction, and waits for acknowledgment before advertising the new path.
The same transaction runs on every link kind. Transport direction does not decide the parent: the prospective child is the endpoint that sends handoff_prepare, so a Bluetooth LE host or an accepting Apple device can become the child of the phone that connected to it. On a Bluetooth LE link, readiness probes travel in datagram frames.
Walk through a successful handoff
1. Offer
The candidate advertises a fresh signed route. The child retains its current active parent.
2. Prepare
The child binds the attempt, parent generation, and offer revision. A bounded preparation lease is created.
3. Probe
Both sides require authenticated UDP reachability. A ready message alone is not enough.
4. Activate
The child sends activation for the exact tuple. Ordinary traffic does not use an uncommitted standby edge.
5. Acknowledge
Only the matching acknowledgment commits the child’s new active parent and advertised path.
6. Drain
The old path drains for 500 ms, then scoped retirement releases its references.
The messages and their owners
Failure is part of the protocol
If the candidate cannot be established or its offer changes, abort preparation and preserve the old parent when available. If activation acknowledgment is lost, rollback uses a newer generation on the retained old active-child edge. Stale messages or failures cannot commit or dismantle a newer attempt.
Preparation leases are 2 seconds. Probe readiness has a 1-second budget with up to three attempts 250 ms apart. Activation acknowledgment has a 1-second deadline. If there is explicitly no spare capacity and the current parent is unhealthy or the replacement leads to a different root, the old path may need to close first; that branch has a real continuity gap. A phone limited to one Bluetooth LE link keeps a suspect Bluetooth LE parent and opens another link only after that one closes, since it cannot hold two.
Authority: Transactional parent handoff. Public examples are synthetic. This guide is maintained against the private implementation; it does not imply access to its source.