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

[STDS-802-11-TGBP] Request for 11bp 6/9 teleconference

Hi Bo,

 

I cannot dial in 6/9 11bp teleconference due to WFA Boston meeting conflict. Please postpone my 11-26/1137 presentation to the next 11bp teleconference. It would be better if you can swap the order of 11-26/1137 and 11-26/1154 so that I can present 11-26/1154 earlier.

 

Additionally, could you put the following SFD SPs in MAC queue?

 

SP11-26/1154 SP1

 

Do you agree to add the following text in the TGbp SFD --- 802.11bp shall specify a protected security parameters indication method by including a STASecurityParameters field in the first AMP uplink frame of all secure AMP communications protocols, such that a non-AP AMP STA can indicate its security parameters (cipher algorithm, MIC algorithm, key sizes, etc.) to an AMP AP for carrying out the secure communication protocol.

Note: This does not apply to mono-static backscatter non-AP AMP STAs.

Reference: 11-26/1154, 11-26/0855, 11-25/2106

 

SP11-26/0942 SP1

 

Do you agree to add the following text in the TGbp SFD --- 802.11bp shall specify a short ID assignment method embedded in the first downlink AMP frame in 1:1 AMP communication by the following?

    1. 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, 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 or the (truncated) hash value of the long ID with the rest of the frame, and a short ID assigned to the non-AP AMP STA.
    2. 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.
    3. 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.
    4. 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.

Reference: 11-26/0942, 11-25/2106

 

Thanks,

 

Hui Luo

Infineon Technologies

 

 

From: Luo Hui (CSS ICW ENG WFS)
Sent: Monday, June 1, 2026 10:07 PM
To: 'sun.bo1@xxxxxxxxxxxxxxxx' <sun.bo1@xxxxxxxxxxxxxxxx>; STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBP] reminder of TGbp TC on May 26

 

Hi Bo,

 

Could you add the following technical contribution to the MAC/security queue?

 

11-26/1137, “Improvements on identity privacy and anti-tracking privacy for secure inventory”

 

Thanks,

 

Hui Luo

Infineon Technologies

 

 

From: sun.bo1@xxxxxxxxxxxxxxxx <sun.bo1@xxxxxxxxxxxxxxxx>
Sent: Monday, May 25, 2026 12:14 PM
To: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBP] reminder of TGbp TC on May 26

 

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, all, 

 

A tentative agenda for the coming TC is uploaded to the server, with focus on the pending SPs and one PDT proposal.

 

 

Best Regards,

Bo

 

Original

From: 孙波  

Date: 2026年05月22日 17:55  

Subject: [STDS-802-11-TGBP] reminder of TGbp TC on May 26  

Hello, all, 

 

I hope you have a safe travel back.

 

As annonced during the May interim week, we have planned several TGbp TCs till Jul plenay session and the next coming TC will be on May 26. 

 

The current TGbp submission list is empty but we do have lots of pending SFD SPs. So the TC agenda will consist of both pending SFD SPs and potential submissions including both PDT proposals and techn contributions. 

 

If you have submissions for the coming or following TCs, please announce your submission request to the reflector, so that I can setup the agenda for coming TCs. Thanks!

 

Best Regards,

Bo

 

 

 

 

 

 

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