| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Hui,
Please see my reply to 1552. And in your 1060, I did not find any of my comments and your reply. Perhaps you did not attach the correct file? But essentially my comments in 1060 are the same as 1552 about AA and SA.
Thanks,
Sam
From: Hui Luo <0000594db8d8d1cb-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, September 2, 2026 2:44 PM To: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx> Subject: Re: [STDS-802-11-TGBP] PDT Security General Update Hi Sam,
Thanks for your comments! Please see my response next to your comments in the attached documents.
Best regards,
Hui
From: Sam Shi <Sam.Shi@xxxxxxxxxxxxxxxx>
Hi Hui,
Thanks for the contributions. Please see my comments regarding AA and SA for 11-26/1060, attached.
I also put my comments in 1552.
Thanks, Sam
From: Hui Luo <0000594db8d8d1cb-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Rojan, Guy,
I agree --- let’s focus on technical aspects. Please review the following security documents at a higher priority than the general description in 11-26/1060.
https://mentor.ieee.org/802.11/dcn/26/11-26-1552-04-00bp-pdt-amp-security-pmk-generation.docx https://mentor.ieee.org/802.11/dcn/26/11-26-1554-02-00bp-pdt-amp-security-data-exchange.docx https://mentor.ieee.org/802.11/dcn/26/11-26-1557-01-00bp-pdt-amp-security-profile.docx
Why I put 11-26/1060 (already motioned) to review again is to remove the “TBD”s. I agree this general description has too much details. We can simplify it after we reach consensus on above documents that address these details.
Best regards,
Hui
From: Rojan Chitrakar <00002005fb56ded7-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Guy,
My personal opinion is that we should focus our energy on agreeing/finalizing the technical aspects of AMP security PDTs for D1.0; the text is already “heavy” to review as is, at least for me 😊. We can always come back and fix the terminologies at a later stage (e.g., we could say AMP Security is based on existing RSNA security algorithms etc.). I think all of us are on the same page regarding not defining new terms. I still think Hui’s general section goes into way too much detail, which is better left to the other (non-general) section. More the (avoidable) text, more the likelihood of comments on the LB.
Best Regards, Rojan Chitrakar
From: Guy-Armand Kamendje <guy-armand@xxxxxxxx>
Hi Rojan, I see your point and I do share your concerns about the mandatory aspects of RSNA requirements. I wonder if there is an easy simple way to say that AMP uses RSNA security algorithms without coining a new word for this. G
On Tue, Sep 1, 2026 at 3:09 AM Rojan Chitrakar <rojan.chitrakar@xxxxxxxxxx> wrote:
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 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 |
Attachment:
11-26-1552-04-00bp-pdt-amp-security-pmk-generation_SS2_HL.docx
Description: 11-26-1552-04-00bp-pdt-amp-security-pmk-generation_SS2_HL.docx