On Fri, Dec 21, 2018 at 06:11:29PM +0530, Neelansh Mittal wrote: > I wanted to know if there is any significance of the > dot11RSNASAERetransPeriod and dot11RSNASync parameters for non-mesh > networks? > > It seems that the 802.11-2016 specification does not make any > distinctions. To quote from the spec:- > > "If validation of the received SAE Commit message fails, the protocol > instance shall send a Del event to the parent process; otherwise, it > shall construct and transmit an SAE > Commit message (see 12.4.5.3) followed by an SAE Confirm message (see > 12.4.5.5). The Sync counter shall > be set to 0 and the t0 (retransmission) timer shall be set. The > protocol instance transitions to Confirmed state." > > But in the hostapd code, there is no role of the t0 timer and Sync > counter for non-mesh networks. The standard is a bit vague on how these retransmission cases apply in infrastructure BSS where there is clear difference in roles between the non-AP STA and AP (i.e., the non-AP STA is the one initiating the authentication case whereas in mesh BSS, either STA can do that). The current hostapd implementation follows the model used in infrastructure BSS for other authentication algorithms, i.e., let the non-AP STA be the one taking care of retransmissions, if needed. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
