A mixed-vendor municipal campus needs faster secure reassociation without depending solely on 802.11r client support. Which technique fits that conceptual need?
Select an answer to reveal the explanation.
Short Explanation
OKC is the campus’s shared memory of recent secure keys so the next AP does not start from zero. Handy when not every client speaks 802.11r cleanly. Open roamers SSIDs and WEP are not the mixed-vendor answer.
Full Explanation
OKC allows PMK security associations to be cached and reused opportunistically across APs to speed secure reassociation. It is commonly considered when FT support is uneven across client or infrastructure mixes. Weakening encryption or creating open roaming SSIDs does not implement OKC.