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

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



Hi Dan,

Thank you for the response.
I do not see any necessary to define a new feature for this if the baseline feature defined by the 11bi SPEC (see Section 12.4.3 "Representation of a passwords and password identifiers") can meet all the requirements. I suggest reusing the current feature as much as possible, as you advocate reusing H2E in PQC PAKE.
Alternatively, the question is back to you: do you see any significant gain in your proposal compared with the baseline feature? do you see any issue to reuse the baseline feature in PQC PAKE? If yes, I would like some comparsion first.
One thing I am not sure about is whether we need to duplicate the whole feature of SAE password identifier protection to the 11bt draft, as the current SAE password identifier is combined with the SAE protocol at this moment. Or, can we make some changes in Subclause (12.4.3 "Representation of a passwords and password identifiers") to meet the requirements of both SAE and PQC PAKE?
In 11-26/1203r5, I duplicate the general description from (12.4.3 "Representation of a passwords and password identifiers"), and reuse the PASN enrypted data element.

Welcome more insights on this from you and other memebers.



Thanks


Best Regards


Jay Yang (杨志杰)



Original
From: Harkins,Dan <daniel.harkins@xxxxxxx>  
To: 杨志杰10343608;  
Cc: TaoChun.Lee@xxxxxxxxxxxx <TaoChun.Lee@xxxxxxxxxxxx>;STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx>;jkneckt@xxxxxxxxx <jkneckt@xxxxxxxxx>;
Date: 2026年11月10日 19:26  
Subject: Re: [STDS-802-11-TGBT] PQC PAKE convergence  

 

  It’s not the naming issue, it’s that it’s unnecessary. Do you have a problem with the technical approach of 11-26/0089r8? Can you explain why you don’t want to do it that way?

 

--

“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, 6:23 PM, "yang.zhijie@xxxxxxxxxx" <yang.zhijie@xxxxxxxxxx>  wrote:

 

PASN encrypted data elements is not equal to PASN protocol, if anyone has the naming issue, we can rename it like, encrypted data elements, or define another encrypted data element, just it.

 

 

 

 

 

发自我的zMail

 

 

Original

From:Harkins,Dan<daniel.harkins@xxxxxxx>

To:杨志杰10343608;TaoChun.Lee@xxxxxxxxxxxx<TaoChun.Lee@xxxxxxxxxxxx>;

Cc:STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx;jkneckt@xxxxxxxxx;

Date:2026-11-10 18:11:22

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

 

  The PAKE should not require the use of PASN simply to protect password identifiers. There is a very good definition of how to protect password identifiers and a way to statelessly regenerate them for the STA in  a manner that precludes tracking. Not only is it a good definition, it has been implemented and I demonstrated it in the demo this afternoon.

 

  Check out 11-26/0089r8. That’s how password identifier protection should be done.

 

  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, 6:01 PM, "yang.zhijie@xxxxxxxxxx" <yang.zhijie@xxxxxxxxxx>  wrote:

 

Hi Taochun,

 

Thanks for reaching out to me.

 

I'm open to this. If the group has a strong preference to add the password identifier, I can help Jarkko integrate it into his contribution.

The password identifier and its protection have been added into 11-26/1203r5, in which the current PASN Encrypted Data element is leveraged  to include the new password identifier provided by the AP to the STA in the last authentication frame. And such idea is quite similar to the SAE password identifier protection defined in 11bi SPEC. Please help review it.

 

 

杨志杰10343608

 

Thanks

 

Best Regards

 

Jay Yang (杨志杰)

 

 

Original

From: TaoChunLee(李道軍)  <TaoChun.Lee@xxxxxxxxxxxx>  

To: Harkins, Dan <daniel.harkins@xxxxxxx>;STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx  <STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx>;  

Cc: TaoChun Lee (李道軍)  <TaoChun.Lee@xxxxxxxxxxxx>;杨志杰10343608;Jarkko  Kneckt <jkneckt@xxxxxxxxx>;

Date: 2026年11月10日  18:52  

Subject: RE: [STDS-802-11-TGBT] PQC PAKE convergence  

 

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!
************* 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