[TLS] Re: Working Group Last Call for Post-quantum Hybrid ECDHE-MLKEM Key Agreement for TLSv1.3

[Joseph Salowey <[e-mail]>]

The WGLC for ECDHE-MLKEM key agreement has concluded.  The general
consensus expressed during the call was that the document is fine as is,
with all algorithms marked as N in an information document and should be
moved forward.  There was a contingent of participants who wanted to make
various changes to the Recommended column for one or more algorithms,
however, there was no consensus to be found as to which combination of
algorithms should be marked as Y or N.  There was no consensus to split the
document or to add algorithms. There was rough consensus on not delaying
the document any further.

Based on this the chairs feel that the action most reflective of working
group consensus is to progress the document with the Recommended column as
is (all algorithms set to N). The Recommended column can be updated in the
future based on standards action or IESG Approval.

Thanks,

Sean, Deirdre, and Joe

On Tue, Oct 7, 2025 at 6:46 AM Joseph Salowey <[e-mail]> wrote:

> This is the working group last call for Post-quantum hybrid ECDHE-MLKEM
> Key Agreement for TLSv1.3. Please review draft-ietf-tls-ecdhe-mlkem [1] and
> reply to this thread indicating if you think it is ready for publication or
> not.  If you do not think it is ready please indicate why.  This call will
> end on October 22, 2025.
>
> Please note that during the WG adoption call, Dan Bernstein pointed out
> some potential IPR (see [2]), but no IPR disclosure has been made in
> accordance with BCP 79.  Additional information is provided here; see [3].
>
> BCP 79 makes this important point:
>
>  (b) The IETF, following normal processes, can decide to use
>    technology for which IPR disclosures have been made if it decides
>    that such a use is warranted.
>
> WG members can take this information into account during the working group
> last call.
>
> Reminder:  This working group last call has nothing to do with picking the
> mandatory-to-implement cipher suites in TLS.
>
> Cheers,
> Joe & Sean
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-mlkem/
> [2] https://mailarchive.ietf.org/arch/msg/tls/mt4_p95NZv8duZIJvJPdZV90-ZU/
> [3]
> https://mailarchive.ietf.org/arch/msg/spasm/GKFhHfBeCgf8hQQvhUcyOJ6M-kI/
>
>