| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
That is an accurate recollection. But my contention is that in a reasonable enterprise network PMKs live long enough cache hits are frequent. So this benefit is somewhat tempered by the fact that there isn’t a significant increase in the
number of messages that would be sent with a non-integrated version. On the other hand, the cost of doing integrated PMK caching is that it is always wasteful. One either throws away the CPace data or the ephemeral ML-KEM and ECC data. And furthermore, integrated
PMK caching has problems with password identifier privacy, it makes it much more difficult.
Jouni, what are your thoughts on password identifiers? Regards, Dan. -- “the object of life is not to be on the side of the majority, but to escape finding oneself in the ranks of the insane.” – Marcus Aurelius On 11/10/26, 5:52 PM, "TaoChun Lee (李道軍)" <000062f6c3142c4b-dmarc-request@xxxxxxxxxxxxxxxxx>
wrote: I recalled integrated PMK caching has the benefits of reducing messages sent over the air, though this depends on cache refresh rate. Jay, Jarkko, what are your thoughts on password identifiers? --
Tao Chun Lee | Tech Manager, Standards
| Communication System Design, MediaTek Inc. Email:
TaoChun.Lee@xxxxxxxxxxxx
| Phone: +886 3 560 0868 | Website: www.mediatek.com From: Harkins, Dan <daniel.harkins@xxxxxxx>
Hi TaoChun, On 11/10/26, 3:20 PM, "TaoChun Lee (李道軍)" <TaoChun.Lee@xxxxxxxxxxxx>
wrote: Glad we converge on this. Another point I see from today’s PQC PAKE session is that
Integrated PMK caching and password identifiers are important 802.11 use cases that might break the CPACE-OQUAKE blackbox approach?! So it seems the group needs to converge on a “greybox” approach that modifies CPACE-OQUAKE with integrated PMK caching and password
identifiers. Thoughts? Yes, I think it would be better if the group converged on an approach that uses CPace-OQuake with password identifiers as a PAKE and that there is a separate PMK caching option that is not specific to the particular
exchange that created the PMK. In fact, I recall that someone else said at the mic that this direction was preferred. The lack of password identifiers was a show stopper and a separate PMK caching protocol was preferred. I certainly did not take away any feeling
that there was consensus on an integrated PMK caching approach. Regards, Dan. -- “the object of life is not to be on the side of the majority, but to escape finding oneself in the ranks of the insane.” – Marcus Aurelius --
Tao Chun Lee | Tech Manager, Standards
| Communication System Design, MediaTek Inc. Email:
TaoChun.Lee@xxxxxxxxxxxx
| Phone: +886 3 560 0868 | Website: www.mediatek.com From: Harkins, Dan <00003862fd143b8a-dmarc-request@xxxxxxxxxxxxxxxxx>
HI TaoChun, Crypto agility is very important and I don’t see any short comings on that front with 0089. Regards, Dan. -- “the object of life is not to be on the side of the majority, but to escape finding oneself in the ranks of the insane.” – Marcus Aurelius On 11/10/26, 10:26 AM, "TaoChun Lee (李道軍)" <000062f6c3142c4b-dmarc-request@xxxxxxxxxxxxxxxxx>
wrote: Hi Dan, I didn’t find crypto agility design (which seems to gain consensus in the group) in 11-26/0089r8, what are your thoughts there? --
Tao Chun Lee | Tech Manager, Standards
| Communication System Design, MediaTek Inc. Email:
TaoChun.Lee@xxxxxxxxxxxx
| Phone: +886 3 560 0868 | Website: www.mediatek.com From: Harkins, Dan <daniel.harkins@xxxxxxx>
Wow, that would’ve been a good lunch discussion to take part in.
Dan. -- “the object of life is not to be on the side of the majority, but to escape finding oneself in the ranks of the insane.” – Marcus Aurelius On 11/10/26, 9:16 AM, "TaoChun Lee (李道軍)" <000062f6c3142c4b-dmarc-request@xxxxxxxxxxxxxxxxx>
wrote: I recalled there was a lunch discussion (Montreal?), and the consensus was to move to CPACE-OQUAKE-based mechanisms. --
Tao Chun Lee | Tech Manager, Standards
| Communication System Design, MediaTek Inc. Email:
TaoChun.Lee@xxxxxxxxxxxx
| Phone: +886 3 560 0868 | Website: www.mediatek.com From:
Hui.Luo@xxxxxxxxxxxx <Hui.Luo@xxxxxxxxxxxx>
Hi TaoChun, Yes, EPPKE with SAE is part of it. Please see my uploaded contribution for details. I think it can readily serve as an interim method based on what
we already have, so 11bt experts can take more time to define a good PQC PAKE method instead of rushing it. Thanks, Hui From: TaoChun Lee (李道軍)
<TaoChun.Lee@xxxxxxxxxxxx>
Hi Hui, By “An existing WPA3 method” you meant SAE? PQC PAKE path finding is on its next generation, with major focus on 1. Efficient signaling 2. 11-bt ownership vs external reference trade-off 3. Crypto agility …
and more. --
Tao Chun Lee | Tech Manager, Standards
| Communication System Design, MediaTek Inc. Email:
TaoChun.Lee@xxxxxxxxxxxx
| Phone: +886 3 560 0868 | Website: www.mediatek.com From: Hui Luo <0000594db8d8d1cb-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Stephen, If possible, could you add 11-25/2327 “An Existing WPA3 Method That Can Be Used For PQC Password Authentication” to PAKE discussion? I only need 5 minutes.
It is for supporting the view that we can afford to take time to develop a good PQC PAKE method. Thanks, Hui From: Stephen Orr (sorr) <000015666257037f-dmarc-request@xxxxxxxxxxxxxxxxx>
Thanks Mark, POCs that I have already spoken with:
1.
Mike Montemurro - POC for PASN and Unauthenticated Access
2.
Jay Yang - POC for MAPC/MBSS
3.
Jouni - POC from the discussion yesterday
4.
Stephen Orr for PAKE Those are the big items. I think we may still need some discussion on some of the others that we classified as PDTs as we may be able to
move them forward with individual contributions Stephen To unsubscribe from the STDS-802-11-TGBT list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBT&A=1 To unsubscribe from the STDS-802-11-TGBT list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBT&A=1 ************* MEDIATEK Confidentiality Notice ******************** The information contained in this e-mail message (including any attachments) may be confidential, proprietary, privileged, or otherwise exempt from disclosure under applicable laws. It is intended to be conveyed only to the designated recipient(s). Any use, dissemination, distribution, printing, retaining or copying of this e-mail (including its attachments) by unintended recipient(s) is strictly prohibited and may be unlawful. If you are not an intended recipient of this e-mail, or believe that you have received this e-mail in error, please notify the sender immediately (by replying to this e-mail), delete any and all copies of this e-mail (including any attachments) from your system, and do not disclose the content of this e-mail to any other person. Thank you! To unsubscribe from the STDS-802-11-TGBT list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBT&A=1 To unsubscribe from the STDS-802-11-TGBT list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBT&A=1 To unsubscribe from the STDS-802-11-TGBT list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBT&A=1 ************* MEDIATEK Confidentiality Notice ******************** The information contained in this e-mail message (including any attachments) may be confidential, proprietary, privileged, or otherwise exempt from disclosure under applicable laws. It is intended to be conveyed only to the designated recipient(s). Any use, dissemination, distribution, printing, retaining or copying of this e-mail (including its attachments) by unintended recipient(s) is strictly prohibited and may be unlawful. If you are not an intended recipient of this e-mail, or believe that you have received this e-mail in error, please notify the sender immediately (by replying to this e-mail), delete any and all copies of this e-mail (including any attachments) from your system, and do not disclose the content of this e-mail to any other person. Thank you! To unsubscribe from the STDS-802-11-TGBT list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBT&A=1 To unsubscribe from the STDS-802-11-TGBT list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBT&A=1 |