Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-11-TGBP] SP text for 11-26/0118 and 11-25/1437

Hi Hui, the following sentences need clarification:

SP1

 


 

(1) an AMP AP receives a PSK modifier, a PSK identifier, and a PMK(AP, STA) from a configurator that knows the PSK and the PSK identifier from a non-AP AMP STA, where the PMK(AP, STA) is computed by the configurator from hash(PSK modifier, PSK);


[GK]: From the sentence, it seems like the non-AP AMP STA is the one sending the information.

 


SP2

 


 

(1) an AMP AP receives a PMK modifier, a PMK identifier, and a PMK(AP, STA) from a configurator that has generated a PMK(configurator, STA) identified by the PMK identifier into a non-AP AMP STA, where the PMK(AP, STA) is computed by the configurator from hash(PMK modifier, PMK(configurator, STA));

[GK] it seems that the information is receive into the non-AP AMP STA which does not make sense

 


 

(3) the non-AP AMP STA derives the same PMK(AP, STA) by hashing the received PMK modifier and the PMK(configurator, STA) identified by the PMK identifier, generates SNonce, and continues the AMP secure communication protocol using the PMK(AP, STA), ANonce, and SNonce; and

[GK] remove the and

 

(4) the configurator can disable the AMP AP from communicating with the non-AP AMP STA by updating the PMK(configurator, STA) in the non-AP AMP STA.

[GK] I think this one is not needed


On Thu, Jan 15, 2026 at 1:22 PM Hui Luo <Hui.Luo@xxxxxxxxxxxx> wrote:

Hi Bo,

 

The SP text has been updated based on offline discussions. If you have no time to update in your SFD SP deck, I will post it in Chat window in real time.

 

Thanks,

 

Hui

 

 

 

SP1

 

Do you agree to add the following text in the TGbp SFD? --- 802.11bp shall specify the following to facilitate scalable secure communications between multiple AMP APs and multiple non-AP AMP STAs:

 

(1) an AMP AP receives a PSK modifier, a PSK identifier, and a PMK(AP, STA) from a configurator that knows the PSK and the PSK identifier from a non-AP AMP STA, where the PMK(AP, STA) is computed by the configurator from hash(PSK modifier, PSK);

 

(2) the AMP AP sends the PSK modifier, the PSK identifier, and ANonce to the non-AP AMP STA; and

 

(3) the non-AP AMP STA derives the same PMK(AP, STA) by hashing the received PSK modifier and its PSK identified by the PSK identifier, generates SNonce, and continues the AMP secure communication protocol using the PMK(AP, STA), ANonce, and SNonce.

 

Notes:

 

(1) The secure AMP communication method is defined in Motion 64, 65, 66.

(2) This does not apply to mono-static backscatter non-AP STAs.

 

Reference: 11-26/0118, 11-25/1437.

 

 

SP2

 

Do you agree to add the following text in the TGbp SFD? --- 802.11bp shall specify the following to facilitate scalable secure communications between multiple AMP APs and multiple non-AP AMP STAs:

 

(1) an AMP AP receives a PMK modifier, a PMK identifier, and a PMK(AP, STA) from a configurator that has generated a PMK(configurator, STA) identified by the PMK identifier into a non-AP AMP STA, where the PMK(AP, STA) is computed by the configurator from hash(PMK modifier, PMK(configurator, STA));

 

(2) the AMP AP sends the PMK modifier, the PMK identifier, and ANonce to the non-AP AMP STA;

 

(3) the non-AP AMP STA derives the same PMK(AP, STA) by hashing the received PMK modifier and the PMK(configurator, STA) identified by the PMK identifier, generates SNonce, and continues the AMP secure communication protocol using the PMK(AP, STA), ANonce, and SNonce; and

 

(4) the configurator can disable the AMP AP from communicating with the non-AP AMP STA by updating the PMK(configurator, STA) in the non-AP AMP STA.

 

Notes:

 

(1) The secure AMP communication method is defined in Motion 64, 65, 66.

(2) The method for the configurator to generate or update PMK(configurator, STA) into the non-AP AMP STA is defined in Motion 158.

(3) This does not apply to mono-static backscatter non-AP STAs.

 

Reference: 11-26/0118, 11-25/1437.

 

 

 

From: Luo Hui (CSS ICW ENG WFS)
Sent: Wednesday, January 14, 2026 4:01 PM
To: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx
Subject: RE: SP text

 

Hi Bo,

 

Please add the following SPs to the SFD SP queue. SP1 was introduced in 11-26/0118 “A Scalable Low-Complexity Provisioning Method for Secure AMP Communication – Follow Up”. SP2 was deferred and modified from 11-25/1437 “A Scalable Low-Complexity Provisioning Method and Its Improvement for Secure AMP Communication”.

 

Dear All --- if you are interested in AMP security, please kindly let me know whether you have any comments or suggestions on these SPs before tomorrow’s SP session.

 

Thanks,

 

Hui

 

 

SP1

 

  • Do you agree to add the following text in the TGbp SFD --- 802.11bp shall specify a PMK input parameter field containing a PSK modifier and a PSK identifier in the Authentication Request frame, such that a non-AP AMP STA can derive a PMK for secure communication with an AMP AP by hashing the PSK modifier and a PSK of the non-AP AMP STA identified by the PSK identifier?
  • Note:
    • The secure AMP communication method is defined in Motion 64, 65, 66.
    • This does not apply to mono-static backscatter non-AP STAs.
  • Reference: 11-26/0118, 11-25/1437.

 

 

SP2

 

  • Do you agree to add the following text in the TGbp SFD --- 802.11bp shall specify a PMK input parameter field containing a PMK identifier and a PMK modifier in the Authentication Request frame, such that a non-AP AMP STA can derive a PMK for secure communication with an AMP AP by hashing the PMK modifier and an existing PMK in the non-AP AMP STA identified by the PMK identifier?
  • Note:
    • The secure AMP communication method is defined in Motion 64, 65, 66.
    • This does not apply to mono-static backscatter non-AP STAs.
  • Reference: 11-26/0118, 11-25/1437.

 

 

 

 

From: Amichai Sanderovich <00003126a116a6ee-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, January 14, 2026 12:13 PM
To: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBP] SP text

 

Caution: This e-mail originated outside Infineon Technologies. Please be cautious when sharing information or opening attachments especially from unknown senders. Refer to our intranet guide to help you identify Phishing email.

 

Hello,

 

I plan to run the following SPs, which were deferred from previous meeting.

Any feedback or concerns will be thankfully received.

 

SP1:

 

Do you agree to add the following text into the 11bp SFD: 

For all the data rates and/or MCSs that are defined for the active Tx non-AP AMP STA in 2.4GHz, the uplink transmitter symbol (chip) clock tolerance shall be ±104 ppm.

 

 

SP2:

 

Do you agree to add the following text into the 11bp SFD: 

802.11bp supports a one phase access mechanism for Active Tx non-AP AMP STAs, which includes:
An uplink payload transmitted in one of the random access time-slots indicated by an AMP trigger frame from an AMP AP

 

 

Best Regards

Amichai

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

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

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