Just because a spec doesn't have it doesn't mean it can't be done. At the same time, implementing something that makes you out-of-spec (like Zero Handoff with a

Just because a spec doesn't have it doesn't mean it can't be done. At the same time, implementing something that makes you out-of-spec (like Zero Handoff with a virtual floating BSSID between multiple orchestrated AP's -- totally unsupported and not in the spec) and designing it the right way can sometimes mean that a function you thought could not be there is there anyway. What he is probably referring to isn't frequency hopping, because what it sounds like and that it actually refers to means different things to different people. For someone who is not a RF engineer, hopping might simply mean "an AP that has multiple radios that uses one to scan the 802.11 2.4Ghz space to see what channels have the least utilization, and then restarts the other radios on a that channel, possibly forcing all clients to lose their connection as if out-of-range and reconnecting again on the new channel as they find it". This, of course, has nothing to do with RF frequency hopping, but if you don't actually know anything about RF, you won't know what hopping means either, and just imagine that what your router with built in AP is doing must therefore be that 'hopping'.