Hi Toerless, On Mon, 23 Feb 2026, 1:49 pm Toerless Eckert, <[email protected]> wrote:
> > At minimum, it would be lovely to have at least ONE example in the RFC, > how the > added amount of storage and compute for ECDHE in the hybrid solution is > significant, given how (in my laymen understanding), both storage and > compute > would predominatly be determined by MLKEM. Else the intro claim "targeting > smaller key > sizes or less computation" is just marketing that should be removed. Compute in the hybrid solution would predominantly be determined by ECDHE, not ML-KEM. See e.g. [0] [1] for numbers. Cheers, Jack [0] https://arxiv.org/html/2508.01694v3 [1] https://blog.cloudflare.com/pq-2024/#ml-kem-versus-x25519 > > Or to paraphrase Uncle Ben: > > With great power over crypto comes great responsibility to explain better. > > Cheers > Toerless > > On Thu, Feb 12, 2026 at 11:05:22AM -0800, Joseph Salowey wrote: > > This message starts the second Working Group Last Call for the pure > ML-KEM > > document (draft-ietf-tls-mlkem-07). > > > > > > The file can be retrieved from: > > > > https://datatracker.ietf.org/doc/draft-ietf-tls-mlkem/ > > > > The diff with the previous WGLC draft (-05) is here: > > > > > > > https://author-tools.ietf.org/iddiff?url1=draft-ietf-tls-mlkem-05&url2=draft-ietf-tls-mlkem-07&difftype=--html > > < > https://author-tools.ietf.org/iddiff?url1=draft-ietf-tls-mlkem-05&url2=draft-ietf-tls-mlkem-06&difftype=--html > > > > > > > > The main focus of this WGLC is to review new text providing more context > > around the use of pure ML-KEM. For those who indicated they wanted this > > text, please let us know if the new text satisfies you and if you support > > publication. This working group last call will end on February 27, 2026. > > > > > > Thank You. > > -- > --- > [email protected] > > _______________________________________________ > TLS mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
