| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hello Dan,
I've made the modifications and will present an r1 in TGbt. I've haven't posted it yet to keep open the option for further modifications.
-Robert
From: Harkins, Dan <00003862fd143b8a-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, March 12, 2026 8:24 AM To: STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBT@xxxxxxxxxxxxxxxxx> Subject: Re: [STDS-802-11-TGBT] Liaison to IETF on support for draft-ietf-tls-mlkem
Robert,
Are you going to update r0 and change the sentence to what you are OK with? Looks like Stephen has a motion queued up for r0 in AM2 and it would be nice to not have a debate over that motion. Would you like me to update r0?
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
From:
"Stacey, Robert" <robert.stacey@xxxxxxxxx>
Hello Dan,
I am OK with: “We would further request that the IETF look at updating EAP-TLS once draft-ietf-tls-mlkem is published as this is one of the mechanisms
-Robert
From: Peter Yee <peter@xxxxxxxxxx>
Dan,
In fact, the EMU WG does have one proposal for an updated EAP-TLS (https://datatracker.ietf.org/doc/draft-reddy-emu-pqc-eap-tls/). That is, of course, a personal Internet-Draft and has not yet been adopted by the EMU WG. It’s also possible that some other approach will be taken for updating EAP-TLS.
Kind regards, -Peter
On 3/11/26, 11:38 AM, "Harkins, Dan" <00003862fd143b8a-dmarc-request@xxxxxxxxxxxxxxxxx> wrote:
Hi Robert,
It says, “We would further request that the IETF look at updating EAP-TLS once draft-ietf-tls-mlkem is published as this is the mechanism through which IEEE P802.11bt will use this work.” It is not “the mechanism”, it is “one of the mechanisms”. Also, “this is the mechanism…use this work” is a bit confusing. How about:
“We would further request that the IETF look at updating EAP-TLS once draft-ietf-tls-mlkem is published as this is one of the mechanisms which IEEE P802.11bt will use.”
We should also ask the IETF IEEE Liaison Officer about this seeing as he is the co-chair of the EAP Methods Update (EMU) working group of the IETF that will be doing the work 😊
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
From: "Stacey, Robert" <robert.stacey@xxxxxxxxx>
Hello Stephen,
I have uploaded a draft liaison to the IETF on support for the publication of draft-ietf-tls-mlkem as an RFC.
I would appreciate it if we could review this at the Thursday AM2 TGbt meeting. I would like the group to consider a motion to approve this (or a variant based on further discussion).
Regards, -Robert 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 |