How is inter AP roaming handeld by Ruckus? Is this a proprietary protocol? Is the Zonedirector handeling this?

[koen_verbeeck]

Let's say a client Wireless IP phone is connected (sending UDP data) to a Ruckus AP1 while making a phone call he is roaming out of AP1s coverage area and roaming into AP2s coverage area.

Using the re-association frame (never used in the real world) AP1 would buffer the data for the client and the protocol will then trigger AP2 requesting the buffered data being send over ethernet to AP2.

What protocol is Ruckus using for this? Is the roaming handeld by the Zonedirector and what if there is no Zonedirector? If only autonomous access points are installed, how would the roaming be handeld? What about 802.11r & 802.11k?

Best regards

[michael_brado]

Ruckus ZoneDirector maintains client session information between APs for smooth
roaming transitions. Version 9.8 now includes 802.11r and 802.11k, if wireless
phones support them.

Standalone AP roaming is not seamless, and requires new authentication with
each roam between APs. This would introduce lost/delayed VoIP packets.

[koen_verbeeck]

Michael,

"Ruckus ZoneDirector maintains client session information between APs for smooth
roaming transitions."

Is this also true without 802.11r & 802.11k implemented?
Is buffered data forwarded between AP's via the zonedirector when tunnel mode is enabled?

BR.
Koen