| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Jay, I think your original text is better than the text proposed. I suggest that it is reinstated. I will do that in my proposal.
Thanks Graham From: Jay Yang <yang.zhijie@xxxxxxxxxx>
Hi Graham, Sorry, I miss one proposed change when I go though your mail again. I find my origianl text is " AP that has dot11DeviceIDActivated equal to true and that
receives a (Re)Association Request frame or the first PASN frame(when using PASN) that includes an Extended RSN Capabilities field with the Device ID Active field equal to 1 shall do one of the following" You propose: "An AP that receives a (Re)Association
Request frame or the first PASN frame(when using PASN ) that includes an Extended RSN Capabilities field with the Device ID
Active field equal to 1 shall do one of the following" I'm thinking a case that the STA thought the AP support 11bh feature via receving a very old Beacon/probe response frame, and then AP disable such feature suddenly, but the STA isn't
aware of that. And then the STA send an authentication/association to the AP with 11bh flag in RSNE equal to 1 based on the recorded old AP information, How the AP make the response if the AP already disable it? (Or we assume the STA must receive the latest
Beacon/probe response via active/passive scan before each association?) So I thought we still need the condition AP that has dot11DeviceIDActivated equal to true. What's your thought? Thanks Best Regards Jay Yang (杨志杰)
Original From: 杨志杰 Date: 2023年10月26日
08:48 Subject: Re: [STDS-802-11-TGBH] CID 107 and CID 103 Hi Graham, Thanks for your valuable suggestion, your proposed change looks good to me. Hi Mark, Before run the motion next call, may I request to show the following editorial change proposed by Graham in 1316r15? 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 From: GSmith <gsmith@xxxxxxxxxxxxxxxxxxx> Date: 2023年10月25日
00:46 Subject: [STDS-802-11-TGBH] CID 107 and CID 103 Hi Jay, At the TGbh meeting today when we were considering CID 107 you noted that it would be better if the text for activation of IRM reflected the text you had proposed for CID 103 which was the activation rules for Device ID. Here is the text you have proposed for Device
ID (from 23/1316r14): “An AP that has dot11DeviceIDActivated equal to true advertises activation of the device ID mechanism by setting the Device ID Active field to 1 in the Extended RSN Capabilities field (see 9.4.2.241 (RSNXE
)) in Beacon and Probe Response frames. A non-AP STA that has dot11DeviceIDActivated equal to true, indicates activation of the device ID mechanism by setting the Device ID Active field to 1 in the Extended RSN Capabilities field in (Re)Association Request
frames or the first PASN frame (when using PASN ) sent to any AP in an ESS that has dot11DeviceIDActivated equal to true and that receives a (Re)Association Request frame or the first PASN frame(when
using PASN ) that includes an Extended RSN Capabilities field with the Device ID Active field equal to 1 shall do one of the following: - include an Extended RSN Capabilities element in the (Re)Association Response frame with the Device ID Active field set to 1. - include an Extended RSN Capabilities element in the Second PASN frame(when using PASN ) with the Device ID Active field set to 1. The
Device ID mechanism depends on all APs in the ESS being configured with dot11DeviceIDActivated set to true.” In general this is great, but the second sentence is very long and seems weird at the end. I looked at it for some time and here I think
is what is intended (I also propose deleting the “(when using PASN )” which I think is superfluous): “An AP that has dot11DeviceIDActivated equal to true advertises activation of the device ID mechanism by setting the Device ID Active field to 1 in the Extended RSN Capabilities field (see 9.4.2.241 (RSNXE
)) in Beacon and Probe Response frames. A non-AP STA that has dot11DeviceIDActivated equal to true, indicates activation of the device ID mechanism by setting the Device ID Active field to 1 in the Extended RSN Capabilities field in (Re)Association Request
frames or the first PASN frame - include an Extended RSN Capabilities element in the (Re)Association Response frame with the Device ID Active field set to 1. - include an Extended RSN Capabilities element in the Second PASN frame The Device ID mechanism depends on all APs in the ESS being configured with dot11DeviceIDActivated set to true.” Based on this, here is the IRM version, which is proposed as resolution for CID 107: REVISED replace cited clause with: “An AP that has dot11IRMActivated equal to true advertises activation of the IRM mechanism by setting the IRM Active field to 1 in the Extended RSN Capabilities field (see 9.4.2.241 (RSNXE )) in Beacon and
Probe Response frames. A non-AP STA that has dot11IRMActivated equal to true, indicates activation of the IRM mechanism by setting the IRM Active field to 1 in the Extended RSN Capabilities field in (Re)Association Request frames or the first PASN frame sent
to any AP in an ESS that has dot11IRMActivated equal to true. An AP that receives a (Re)Association Request frame or the first PASN frame that includes an Extended RSN Capabilities field with
the IRM Active field equal to 1 shall do one of the following: - include an Extended RSN Capabilities element in the (Re)Association Response frame with the IRM Active field set to 1. - include an Extended RSN Capabilities element in the Second PASN frame with the IRM Active field set to 1. The IRM mechanism depends on all APs in the ESS being configured with dot11IRMActivated set to true.” Please let me know your thoughts. Are others OK with this and also the slight change to the CID 103 text in 23/1316r14? Thanks Graham 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 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 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 |