ENGINEERING GUIDE · WIRELESS

802.11k, 802.11v and 802.11r

How enterprise Wi-Fi helps clients discover candidate APs, receive transition recommendations and move between APs with less authentication delay.

Engineering referenceWi-Fi roaming802.11k · v · r
The important bit: roaming remains client-driven. 802.11k can improve candidate discovery, 802.11v can recommend a transition, and 802.11r can reduce authentication delay. None guarantees that a client will roam.

In this guide

  1. 802.11k
  2. 802.11v
  3. 802.11r
  4. FT security and Mobility Domains
  5. The client still decides
  6. A practical roaming sequence
  7. Troubleshooting

802.11k — neighbour information

802.11k provides radio-resource information that helps a client discover nearby candidate APs efficiently. A client can request a neighbour report and the infrastructure can supply candidate BSS information such as BSSID, operating channel and other radio details.

This reduces the need for a client to blindly scan every possible channel, which can reduce scan time and temporary disruption. It does not select the AP on the client's behalf.

802.11v — BSS Transition Management

802.11v includes BSS Transition Management. An AP or controller can send a BSS Transition Management Request containing candidate information and a recommendation to move.

The client can accept, reject or ignore the recommendation. Steering can consider radio conditions, capacity and policy, but 802.11v is not a command that forcibly moves every client.

Do not confuse a transition recommendation with a successful roam: the client still has to authenticate and reassociate successfully.

802.11r — Fast BSS Transition

802.11r reduces the work required when a compatible client moves between APs in the same mobility domain. Fast Transition establishes a key hierarchy so the target AP can derive the required session keys without repeating the complete authentication exchange in the same way.

Key concepts include PMK-R0, PMK-R1 and resulting pairwise transient key material. FT can operate using Over-the-Air or Over-the-DS procedures depending on WLAN design and implementation.

802.11r is a security/transition optimisation, not a signal-strength or AP-selection mechanism. Client support and compatible authentication methods are essential.

FT security and Mobility Domains

The Mobility Domain Identifier (MDID) identifies the Fast BSS Transition domain. APs participating in the same FT domain need compatible WLAN/security configuration and key-management relationships.

Do not reduce this to “same SSID equals same security domain”. The FT domain is defined by the mobility and security configuration and the implementation.

FT can be used with supported WPA2/802.1X, WPA2/PSK and WPA3/SAE deployments. Older IoT clients can have compatibility problems, so test before enabling it universally.

The client still decides

The client driver and supplicant decide when a roam is desirable. Vendor drivers expose different roaming controls, and Windows roaming behaviour should be treated as driver/OEM dependent rather than one universal algorithm.

Sticky clients can remain associated at poor signal levels even when the infrastructure provides good neighbour information and transition recommendations. Minimum RSSI policies, band steering and load balancing can help, but aggressive steering can also create instability.

A practical roaming sequence

  1. The client is associated to AP A.
  2. 802.11k can provide a neighbour report describing AP B and other candidates.
  3. The client evaluates RF conditions, application needs and policy.
  4. 802.11v may recommend AP B.
  5. The client decides to roam.
  6. If FT is enabled and supported, 802.11r performs the fast-transition exchange and derives required key material.
  7. The client reassociates to AP B and resumes data.

Troubleshooting roaming

  • Verify compatible SSID, security, mobility-domain and FT settings across APs.
  • Check whether the client advertises 802.11k/v/r capability.
  • Capture management frames and identify neighbour reports, BSS Transition Management, authentication and reassociation/FT exchanges.
  • Measure RSSI and SNR at the actual roam point rather than assuming distance equals signal quality.
  • Check whether the client is refusing a transition recommendation.
  • For voice, measure roam interruption, packet loss and jitter rather than relying only on “roamed successfully”.
  • Test problematic client models individually; one incompatible supplicant can make an otherwise correct WLAN appear broken.
Engineering principle: good roaming is a system outcome: RF design, client behaviour, security configuration, AP/controller policy and the application all matter.

Standards and references

  • IEEE 802.11k — radio resource measurement.
  • IEEE 802.11v — wireless network management and BSS transition.
  • IEEE 802.11r — Fast BSS Transition.
  • Vendor wireless documentation for client compatibility and steering behaviour.

Key takeaways

Think of k, v and r as three separate tools: k helps find candidates, v recommends a move, r makes the security transition faster. The client remains central to the decision.