802.11r, 802.11k, 802.11v: The Three Protocols That Make WiFi Roaming Seamless
In a multi-AP WiFi environment — a mesh system, an office with multiple access points, or a home with a router and a range extender — the experience of moving between access points defines the quality of the whole system. A phone call that drops when you walk from the kitchen to the garden is not a signal problem; it is a roaming problem. Three 802.11 protocol amendments, operating together, are the mechanism that makes roaming fast enough to be invisible.
Why Roaming Is a Client Decision
The counterintuitive starting point: in 802.11 networks, the client device decides when to roam, not the access point. The AP cannot force a connected device to disconnect and move to a better AP. It can suggest, request, and in some implementations apply pressure — but the final roaming decision is made by the operating system and WiFi driver on the device itself.
This creates the “sticky client” problem. A device connected to an AP maintains that connection even as the device moves farther away, because the existing connection is still technically functional. The device is receiving signal from the original AP at -78 dBm, a closer AP is available at -52 dBm, but no mechanism has notified the device of the better option. The device sits on the degraded connection until signal falls below the driver’s minimum threshold, then begins the full authentication and association process with a new AP — which takes hundreds of milliseconds, long enough to drop a VoIP call.
The three roaming protocols — 802.11r, 802.11k, and 802.11v — address different parts of this problem.
802.11k: Telling the Device What Is Available
802.11k, ratified in 2008, defines a Neighbor Report mechanism. An AP that implements 802.11k can respond to a client’s Neighbor Report Request with a list of nearby APs: their BSSIDs, operating channels, and signal information. The client can use this information to make roaming decisions without conducting a full channel scan.
The performance benefit of neighbor reports is in scan time reduction. When a device decides it needs to roam, it must discover what other APs are available. Without 802.11k, this typically involves scanning every possible channel — dwell on channel 36, listen for beacons, move to channel 40, listen, continue through all possible channels. On 5 GHz with 25 channels and a typical 20ms dwell time per channel, a full scan takes 500ms or more.
With an 802.11k neighbor report cached from the current AP, the device knows to scan channel 149 (where the nearby AP operates) rather than scanning all channels. Scan time drops to milliseconds for a single targeted channel. The client finds the target AP almost immediately, executes the roaming transition, and the gap is substantially reduced.
802.11k also includes load reporting: APs can advertise their current client count and channel utilization, allowing clients to make informed choices between multiple candidate APs rather than simply taking the nearest one.
802.11r: Making the Handoff Fast
802.11r, also ratified in 2008, defines Fast BSS Transition (FT). Without 802.11r, the roaming sequence when a device moves to a new AP involves: deauthentication from the old AP, discovery of the new AP, reassociation, and a full 802.1X re-authentication or four-way handshake to establish new session keys. Even with WPA2-PSK, the four-way handshake adds tens to hundreds of milliseconds to the roaming gap.
For most web browsing, an 80ms roaming gap is imperceptible — TCP connections resume after a brief pause. For a VoIP call sampled at 20ms intervals, an 80ms gap drops multiple audio frames and produces an audible glitch. For a video call, the codec may freeze or artifact visibly. For real-time gaming or industrial control, any roaming gap is a problem.
802.11r pre-authenticates the device to potential target APs before the roaming decision is made. Using the PMK hierarchy, a device associated with AP1 can establish a PMK-R1 with AP2 through a pre-registration process. When the device decides to roam to AP2, the cryptographic material is already in place. The handoff involves re-association only — no full authentication sequence. Roaming latency drops from 50 to 200ms to under 10ms, and often to 1 to 2ms on good implementations.
This is the protocol that enables transparent voice call continuity as a user walks through an office or campus. Without 802.11r, VoIP over WiFi in multi-AP environments produces audible artifacts at every AP boundary. With 802.11r, the transition is below the perceptual threshold.
802.11v: Asking the Device to Roam
802.11v, ratified in 2011, defines BSS Transition Management — a mechanism by which the AP can send a BSS Transition Management Request to a client, suggesting or requesting that it roam to a different AP.
The AP can include a list of candidate APs with the request, giving the client the information it needs to roam immediately without scanning. The disassociation timer in the request frame sets a deadline: the AP gives the client a grace period, after which it will disassociate the client regardless. In practice, well-behaved clients typically comply with the suggestion before the deadline expires.
802.11v is the mechanism behind two important features: band steering and load balancing. Band steering uses 802.11v requests to encourage dual-band capable devices to use the 5 GHz band when the AP determines it is more appropriate. Load balancing uses 802.11v requests to move clients from a congested AP to a less-loaded one, even when the client’s signal to the current AP is still acceptable.
The three protocols work together most effectively. 802.11k ensures the client knows where the candidate APs are. 802.11r ensures the cryptographic handoff is fast when the client decides to roam. 802.11v gives the AP a mechanism to nudge the client toward roaming at the appropriate time. Combined, they are sometimes referred to as “fast roaming” or “802.11k/r/v” in vendor documentation and enterprise WiFi controller configuration menus.
Enabling These Protocols
On consumer mesh systems, 802.11r/k/v support is typically enabled by default when the system is set up with roaming optimization. The user interface does not expose individual protocol toggles — the mesh intelligence handles it.
On controller-managed access points (Ubiquiti UniFi, TP-Link Omada, Cisco, Aruba), the protocols are configurable per SSID. UniFi’s “High Performance Devices” band setting and the separate “BSS Transition” and “Fast Roaming” options in the SSID configuration are the relevant toggles. For environments with VoIP devices or moving users, all three should be enabled. For static deployments with desktop clients that never roam, the overhead is minimal but the benefit is also zero — the protocols are harmless to enable regardless.
One constraint: 802.11r requires consistent security configuration across all APs sharing the SSID. All APs must use the same passphrase, the same encryption type, and be configured as part of the same mobility domain. A mesh or controller system handles this automatically; a manual multi-AP deployment with 802.11r requires careful matching of security parameters across all devices.