Hi Bo,
Could you stick with your previous agenda plan (SP then contribution) or grant a priority for my security SP below? It has been deferred a number of times and has reached consensus
based on offline discussions to my best knowledge. I need to get it done before I can work on PDT security in order to make the Draft 1.0 requirement by IEEE May meeting.
Thanks,
Hui
SP in 11-26/0598r1
Do you agree to add the following text in the TGbp SFD --- 802.11bp shall specify the following secure AMP communication method, in which
- A non-AP AMP STA has a high-entropy PSK and may have a high-entropy PMKv1 stored in persistent memory. An AMP AP (denoted as AP1) has a parameter
Modifier1 and a PMK1, with PMK1 = hash(Modifier1, PMKv1) if the non-AP AMP STA has the PMKv1 or PMK1 = hash(Modifier1, PSK) otherwise, where PMKv1 or PSK is unknown to AP1.
- AP1 sends an ANonce and the Modifier1 in a downlink AMP frame to the non-AP AMP STA.
- Upon receiving the downlink AMP frame, the non-AP AMP STA generates an SNonce, computes PMK1 = hash(Modifier1, PMKv1) if it has the PMKv1 stored
in its persistent memory or PMK1 = hash(Modifier1, PSK) otherwise, derives a PTK using the PMK1, the ANonce, the SNonce, an Authenticator Address (AA), and a Supplicant Address (SA), generates a MIC using a KCK derived from the PTK, and sends back the SNonce
and the MIC in an uplink AMP frame to AP1.
- If the uplink AMP frame is carrying any UL data, the data payload portion of the uplink AMP frame may be protected using the TK derived from
the PTK.
- AP1 computes a PTK using the PMK1, the ANonce, the SNonce, the AA, and the SA, and verifies the MIC using the KCK derived from the PTK. If the
MIC is invalid, AP1 aborts.
- If the uplink AMP frame contains protected data, the AMP AP processes the UL data using the TK derived from the PTK. If there are any subsequent
AMP frames to be exchanged, the AMP frames may be protected using the TK derived from the PTK.
Note: this does not apply to mono-static backscatter non-AP STAs
Reference: 11-26/0598, 11-26/0118, 11-26/1437
From: sun.bo1@xxxxxxxxxxxxxxxx <sun.bo1@xxxxxxxxxxxxxxxx>
Sent: Monday, March 30, 2026 11:32 AM
To: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBP] Agenda of TGbp TC on Mar 31 is updated
|
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.
|
The agenda for the coming TGbp TC on Mar 31 was updated and uploaded to the server.
- since it's a little bit difficult to control the time of the SP discussion, the PDT/Tech contributions' discussion is arranged before the SPs, e.g. the first hour
will be for PDT/Tech contributions and the second hour will be for SPs.
- a SP that was discussed in past TCs and deferred could be brought back to the end of the pending SP list with a SP request to the reflector.
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
|