| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
From standard point of view, we just need to define a different replay counter for Protected Sensing Frames- which essentially says it all. Ali From: Rojan Chitrakar <rojan.chitrakar@xxxxxxxxxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Ali, Thanks for the clarification, I understand the intention better and am fine if Chao Ming wants to keep it in the motion.
However, personally I would still think PN segmentation is an implementation specific solution; I don’t believe .11 spec needs to define it. As long as it is ensured that the PN is incremented for each new frame and never repeats, replay
attacks are prevented. Regards, Rojan From: Ali Raissinia <alirezar@xxxxxxxxxxxxxxxx>
Once a device is associated, it derives a PTK and a corresponding PN sequence for packet transmissions (PN is coupled to PTK). Since frames are in general classified (i.e. TIDs) and sent out of order then for each classification a PN segment
is assigned (i.e. PN=10000 to 50000) so that receiver can track and if needed detect a replay attack. The ‘Protected sensing frames’ cannot share the same PN segment as Protected Dual Public Action frames since they would need to be transmitted when TB/NTB
measurement instant occurs regardless. Regards, Ali From: Rojan Chitrakar <rojan.chitrakar@xxxxxxxxxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Chao Ming, I have a question regarding motion 2: A new action category of robust ‘Protected Sensing Frame’ is defined to separate PN segment. What is the meaning of “..to separate PN segment”? Is it necessary to include this in the motion? PNs are tied to the keys that are used to protect the frame; if the keys are different, the PN space will be automatically different as well. Regards, Rojan From: luochaoming@xxxxxxxx <000015d97e832564-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi All, I plan to run the following motions, and if you have any further comment or concern, please do send me an email, thanks! Tony, please help to add the following two motion requests: Motion 1, Ref: 22/0286r1, SP1 18Y/3N/15A Move to add the following to the TGbf SFD:
Motion 2, Ref: 22/0286r1, SP2 14Y/3N/18A Move to add the following to the TGbf SFD: •A new action category
of robust ‘Protected Sensing Frame’ is defined to separate PN segment. BR, Chaoming
OPPO 本电子邮件及其附件含有OPPO公司的保密信息，仅限于邮件指明的收件人使用（包含个人及群组）。禁止任何人在未经授权的情况下以任何形式使用。如果您错收了本邮件，请立即以电子邮件通知发件人并删除本邮件及其附件。 This e-mail and its attachments contain confidential information from OPPO, which is intended only for the person or entity whose address is listed above. Any use of the information contained
herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately
and delete it! To unsubscribe from the STDS-802-11-TGBF list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 To unsubscribe from the STDS-802-11-TGBF list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 To unsubscribe from the STDS-802-11-TGBF list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 To unsubscribe from the STDS-802-11-TGBF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 |