Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Jay, "The non-AP STA should store the newly allocated IRM as an identifier for use with the AP(s) in the ESS, and the AP(s) should store that IRM as an identifier for that non-AP STA" Personally I like it and prefer it. I did want to keep the idea that the AP(s) do store the IRM. I got the impression at the meeting however, that others felt that we should not tell the AP what to do, and hence the phrase after the
comma is deleted. I have left both versions in 23/1373r4 and I assume we will discuss and possibly straw poll the two.
Thanks for your insights Graham From: yang.zhijie@xxxxxxxxxx <yang.zhijie@xxxxxxxxxx>
Hi Graham, I have checked the description of "PMKSA caching" in the baseline(11me draft 4.0) as the storage of PMKSA caching is similar to IRM (Although their generation manner has some difference.
) . And I found the following sentence.
Obviously, PMKSA caching looks like ESS level and all APs in the ESS share all the same PMKSA , and each AP verify the PMKSA independently. It's out of 802.11 standard that how APs in the ESS synchronize the generated PMKSA . If we follow the similar writing sytle above, the following setence should be prefered. Otherwise, the storage description on APs/ESS side will be missing. "The non-AP STA should store the newly allocated IRM as an identifier for use with the AP(s) in the ESS, and the AP(s) should store that IRM as an identifier for that non-AP STA" What's your thought? Thanks Best Regards Jay Yang (杨志杰) To unsubscribe from the STDS-802-11-TGBH list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBH&A=1 |