Hi,
I am going to present SP0942 below in 6/30 teleconference. Please kindly let me know if you have any comments/suggestions for the SP text, so that I can address the comments/suggestions
ahead of time for better use of the SP discussion time. Thanks!
Some explanations based on the comments I already received ---
- This SP proposes an efficient supplemental method for non-AP AMP STAs that self-generate short IDs from their long IDs
(permanent IDs). If an AMP AP learns the self-generated short ID of a non-AP AMP STA from a “bonding” relationship or from an inventory procedure, and if the self-generated short ID can be used by the AMP AP in 1:1 communication with the non-AP AMP STA without
collision or anti-tracking privacy requirements, the proposed method won’t be invoked.
- The short ID assignment method can work with and without security requirement, with and without privacy requirement.
It is not tied with security and/or privacy.
- If security is required, the AMPSTAShortIDAssignment field in the first downlink frame is not protected because no key
has been agreed yet, so it needs to be included in the MIC calculation in the first uplink frame for the AMP AP to verify the non-AP AMP STA has received the value sent by the AMP AP. The reason for not including AMPSTAShortIDAssignment in the first uplink
frame is to avoid the burden of sending 10-20 octets in the uplink, which is a nontrivial overhead for the non-AP AMP STA.
Best regards,
Hui Luo
Infineon Technologies
SP 26/0942.
Do you agree to add the following text into the 11bp SFD ? [Jun 4, 2026;]
- 802.11bp shall specify a short ID assignment method embedded in the first downlink AMP frame in 1:1 AMP communication by the following:
- If an AMP AP knows the long ID of a non-AP AMP STA and if one of the following conditions is met: (1) the non-AP AMP STA does not have a short
ID but needs one for the 1:1 communication, (2) the non-AP AMP STA has a short ID in collision with another non-AP AMP STA and needs to be fixed for the 1:1 communication, or (3) the non-AP AMP STA’s short ID should be changed for privacy reason, the AMP AP
includes an “AMPSTAShortIDAssignment” field in the first downlink AMP frame of the 1:1 AMP communication session with the non-AP AMP STA, where the “AMPSTAShortIDAssignment” contains the non-AP AMP STA’s long ID (if no privacy concern) or the (truncated) hash
value of the long ID with the rest of the frame (if privacy for long ID is needed), and a short ID assigned to the non-AP AMP STA.
- If the non-AP AMP STA has NVRAM and saved the assigned short ID in NVRAM, it includes an “AMPSTAShortIDSaved” field in the first uplink AMP frame
in case of no security requirement, or in the second uplink AMP frame after the non-AP AMP STA authenticates the AMP AP by verifying the MIC of the second downlink AMP frame.
- In case the “AMPSTAShortIDAssignment” is included in the first downlink AMP frame of a 1:1 secure AMP communication session, the non-AP AMP STA
includes the “AMPSTAShortIDAssignment” in MIC calculation for the first uplink AMP frame, and the AMP AP includes it in MIC calculation when verifying the MIC of the first uplink AMP frame.
- If the AMP AP receives the AMPSTAShortIDSaved, it creates a profile for the non-AP AMP STA, saves <non-AP AMP STA’s long ID, assigned short ID
in NVRAM> in the profile, and uses the assigned short ID in future communications with the non-AP AMP STA without including the “AMPSTAShortIDAssignment” field in the first downlink AMP frame.
- Note: the above protocol does not apply to mono-static backscatter non-AP AMP STAs
To unsubscribe from the STDS-802-11-TGBP list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBP&A=1
|