[TLS] Fwd: Re: WG Last Call: draft-ietf-tls-mlkem-05 (Ends 2025-11-26)

[Keegan Dasilva Barbosa <[e-mail]>]

It just came to my attention that I missed the inclusion of the tls mailing
list. Sorry about that, forwarding for transparency.

Reiterating: I support the publication of this document, as it aligns with
the government of Canada's plans to include the use of pure ML-KEM within
our guidance documentation.

Keegan Dasilva Barbosa
Canadian Centre for Cyber Security


---------- Forwarded message ---------
From: Keegan Dasilva Barbosa <[e-mail]>
Date: Wed, Nov 12, 2025 at 10:08 AM
Subject: Re: [TLS] Re: WG Last Call: draft-ietf-tls-mlkem-05 (Ends
2025-11-26)
To: Sean Turner <[e-mail]>, [e-mail] <
[e-mail]>, [e-mail] <[e-mail]>


I support the publication of this document. The government of Canada plans
to include the use of pure ML-KEM within our cryptographic guidance
documentation.

Keegan Dasilva Barbosa
Canadian Centre for Cyber Security


On Mon, Nov 10, 2025 at 11:44 AM Rebecca Guthrie <rmguthr=
[e-mail]> wrote:

> I support publication of the document.
>
> Rebecca Guthrie
> she/her
> Center for Cybersecurity Standards (CCSS)
> Cybersecurity Collaboration Center (CCC)
> National Security Agency (NSA)
>
> -----Original Message-----
> From: Sean Turner via Datatracker <[e-mail]>
> Sent: Wednesday, November 5, 2025 1:51 PM
> To: [e-mail]; [e-mail]; [e-mail]
> Subject: [TLS] WG Last Call: draft-ietf-tls-mlkem-05 (Ends 2025-11-26)
>
>
> Subject: WG Last Call: draft-ietf-tls-mlkem-05 (Ends 2025-11-26)
>
> This message starts a 3-week WG Last Call for this document.
>
> Abstract:
>    This memo defines ML-KEM-512, ML-KEM-768, and ML-KEM-1024 as
>    NamedGroups and and registers IANA values in the TLS Supported Groups
>    registry for use in TLS 1.3 to achieve post-quantum (PQ) key
>    establishment.
>
> File can be retrieved from:
> https://datatracker.ietf.org/doc/draft-ietf-tls-mlkem/
> Please review and indicate your support or objection to proceed with the
> publication of this document by replying to this email keeping
> [e-mail] in copy. Objections should be motivated and suggestions to
> resolve them are highly appreciated.
>
> Authors, and WG participants in general, are reminded again of the
> Intellectual Property Rights (IPR) disclosure obligations described in BCP
> 79 [1]. Appropriate IPR disclosures required for full conformance with the
> provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of
> any. Sanctions available for application to violators of IETF IPR Policy
> can be found at [3].
>
> Thank you.
>
> [1] https://datatracker.ietf.org/doc/bcp78/
> [2] https://datatracker.ietf.org/doc/bcp79/
> [3] https://datatracker.ietf.org/doc/rfc6701/
>
>
>
> _______________________________________________
> TLS mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>
> _______________________________________________
> TLS mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>