Given that the standard seems to include a Client-Identifier but little client-side support; that would be the answer. Lobby hard for user interaction or even a unique client identifier if the vendor doesn't want client interaction. Given how valuable PPSK/IPSK/DPSK/whatever you call it, is to so many use cases to be abandoned or forced into fragile RADIUS lookups. Seeing how much backward compatibility was tossed for 6GHz, is there a chance that Client-Identifier can be made mandatory or some other mechanism to allow SAE3 PPSK?
Todd Smith
Given that the standard seems to include a Client-Identifier but little client-side support; that would be the answer. Lobby hard for user interaction or even a unique client identifier if the vendor doesn't want client interaction. Given how valuable PPSK/IPSK/DPSK/whatever you call it, is to so many use cases to be abandoned or forced into fragile RADIUS lookups. Seeing how much backward compatibility was tossed for 6GHz, is there a chance that Client-Identifier can be made mandatory or some other mechanism to allow SAE3 PPSK?