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

Re: [STDS-802-11-TGBT] PQC PAKE convergence



 

I see your point, but given integrated PMK caching is the direction this group wants to go, password identifiers need to find their way in (still doable).

 

--

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>
Sent: Wednesday, November 11, 2026 10:05 AM
To: TaoChun Lee (
李道軍) <TaoChun.Lee@xxxxxxxxxxxx>; Mathy Vanhoef <mathy.vanhoef@xxxxxxxxxxx>; STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBT] PQC PAKE convergence

 

 

  TaoChun,

 

  What I said was, “integrated PMK caching has problems with password identifier privacy, it makes it much more difficult.” I didn’t say they were mutually exclusive. Nor did I say it was a “roadblock” (as Po-kai said).

 

  Think of how this works…

 

                “Hi, I’d like to do PMK caching with PKID=awurgigaew or PQCPAKE with password id=434ugfhwsao”

 

Access point selects PMK caching. 11bi PMKID protection will change that so next time the client says,

 

                “Hi, I’d like to do PMK caching with PKID=xaaa123122g or PQCPAKE with password id=434ugfhwsao”

 

Because he did not complete PQCPAKE he didn’t get a new password id. Now a tracker is able to connect the two attempts. Privacy is lost.

 

  Now of course it’s possible fix this with integrated PMK caching but as I have been saying it makes it much more difficult. It’s a problem that needs fixing. That is it. Not a roadblock. Not impossible. Not mutually exclusive. Just more difficult.

 

  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/11/26, 7:47 AM, "TaoChun Lee (李道軍)" <TaoChun.Lee@xxxxxxxxxxxx> wrote:

 

 

Hi Mathy,

 

Mmm, similar ideas along this line were discussed in 11-26/1385 (Montreal?), at the time was not well-received by the group.

 

Hi Dan,

 

For integrated PQC PAKE, are you saying PMK caching and password identifiers are mutual exclusive? Please elaborate.

 

I do see values that both are integrated in the PQC PAKE “greybox” approach.

 

--

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: Mathy Vanhoef <00006588701cd687-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, November 11, 2026 6:43 AM
To: STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBT] PQC PAKE convergence

 

External email : Please do not click links or open attachments until you have verified the sender or the content.

Hi all,

 

Would another option be to create a new 'PMKSA Caching element'?

 

A client can then decide on its own whether to include only the PQC Parameter element (which e.g. would encode each PAKE message) or only the PMKSA Caching element. And if the client isn't sure whether the PMKSA still exists and wants to reduce the possible number of messages, then it can include both elements.

 

Implementations can then decide on their own what their preference is, e.g., whether they want to perform the additional computation to include a fresh valid first CPaceOQUAKE handshake message alongside the PMKSA Caching element.

 

Best regards,

Mathy


From: Harkins, Dan <00003862fd143b8a-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: 10 November 2026 12:01
To: STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBT] PQC PAKE convergence

 

 

 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>
Sent: Tuesday, November 10, 2026 4:58 PM
To: TaoChun Lee (
李道軍) <TaoChun.Lee@xxxxxxxxxxxx>; STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx
Cc: Jay Yang <yang.zhijie@xxxxxxxxxx>; Jarkko Kneckt <jkneckt@xxxxxxxxx>
Subject: Re: [STDS-802-11-TGBT] PQC PAKE convergence

 

 

  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>
Sent: Tuesday, November 10, 2026 11:42 AM
To: STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBT] TGbt Nov meeting Agenda Posted

 

External email : Please do not click links or open attachments until you have verified the sender or the content.

 

  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>
Sent: Tuesday, November 10, 2026 10:21 AM
To: TaoChun Lee (
李道軍) <TaoChun.Lee@xxxxxxxxxxxx>; STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBT] TGbt Nov meeting Agenda Posted

 

 

  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>
Sent: Tuesday, November 10, 2026 10:07 AM
To: TaoChun Lee (
李道軍) <TaoChun.Lee@xxxxxxxxxxxx>; STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBT] TGbt Nov meeting Agenda Posted

 

External email : Please do not click links or open attachments until you have verified the sender or the content.

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>
Sent: Monday, November 9, 2026 8:18 PM
To: Luo Hui (ES ICW ENG WFS) <Hui.Luo@xxxxxxxxxxxx>; STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx
Cc: TaoChun Lee (
李道軍) <TaoChun.Lee@xxxxxxxxxxxx>
Subject: RE: [STDS-802-11-TGBT] TGbt Nov meeting Agenda Posted

 

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.

 

 

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>
Sent: Tuesday, November 10, 2026 9:01 AM
To: STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBT] TGbt Nov meeting Agenda Posted

 

External email : Please do not click links or open attachments until you have verified the sender or the content.

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>
Sent: Monday, November 9, 2026 1:15 PM
To: STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBT] TGbt Nov meeting Agenda Posted

 

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.

 

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 

 


From: mark.hamilton2152@xxxxxxxxx <mark.hamilton2152@xxxxxxxxx>
Date: Sunday, November 8, 2026 at 05:11
To: STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBT] TGbt Nov meeting Agenda Posted

Hi, Dan,

Those 4 CIDs are under the “PDT” process in https://mentor.ieee.org/802.11/dcn/26/11-26-1556-03-00bt-proposed-tgbt-procedure-for-comment-resolution.docx.  As such, the expectation is that the POC for each PDT (and these cross 4 PDTs) is who you should contact, to work through reaching consensus on your submissions.

 

Last I knew, we were waiting for Stephen to assign POCs - that's still the status, right?

 

Mark

 

From: Harkins, Dan <00003862fd143b8a-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Saturday, November 7, 2026 9:56 PM
To: STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBT] TGbt Nov meeting Agenda Posted

 

 

  Sorry, fat fingered…. Make that final question be “So what kind of submission do I need to come up with in order to satisfy a CID that requests incorporation of a submission that already exists into the draft?”

 

--

“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/8/26, 12:54 PM, "Harkins, Dan" <00003862fd143b8a-dmarc-request@xxxxxxxxxxxxxxxxx> wrote:

 

 

  Hi Stephen,

 

  I have 4 CIDs, 277, 278, 279, and 280 that all have a proposed change of “incorporate <an existing submission> into the draft” where each one has a valid submission that exists on mentor (and has for quite some time, like over a year). The status of each of them is “submission required”. So what kind of submission do I need to come up with in order to satisfy a submission that requests incorporation of a submission that already exists into the draft? Is there some meta-submission or what?

 

  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/8/26, 6:18 AM, "Stephen Orr (sorr)" <000015666257037f-dmarc-request@xxxxxxxxxxxxxxxxx> wrote:

 

All,

 

TGbt Agenda has been posted. 

 

11-26/2294r0

https://mentor.ieee.org/802.11/dcn/26/11-26-2294-00-00bt-agenda-2026-november-plenary.pptx

 

Those that have CIDs and requested agenda time are set to go first on Monday - we will get through as many as possible. 

 

Tuesday - we are going to focus on the PAKE discussion - we need to close on a direction.

 

If you have CIDs that you have signed up for, please send me an message with the status and when you want agenda time.

 

Thanks 

 

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


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


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


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