The thread starts with “Due to this, Cisco has preliminarily considered Kyber
unusable”
This is obviously not true anymore as Scott very clearly stated that Cisco
wants to see both hybrid and non-hybrid ML-KEM standardized, and that they want
to implement and ship both. I agree with Scott. Also,
TL;DR: Historical notes: not important for the current discussion.
To be clear about whether Cisco (or actually, me – I don’t actually speak for
Cisco, but I like to think they listen to my advice) preferred NTRU or NTRU
Prime – I actually didn’t have a strong opinion. I advocated NTRU because
The IESG has received a request from the Transport Layer Security WG (tls) to
consider the following document: - 'TLS 1.2 is in Feature Freeze'
as Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comm
Hi all, since I am still on the CC list,
I took the question to be about how to organize the work. If everything is
a priority, there are no priorities.
That's why I want to do this one (and only this one), first:
https://datatracker.ietf.org/doc/draft-kwiatkowski-tls-ecdhe-mlkem/
Some of the ot
Issues
--
* tlswg/tls12-frozen (+3/-2/💬0)
3 issues created:
- Ref: 8446->844bis (by seanturner)
https://github.com/tlswg/tls12-frozen/issues/9
- Nits complaint: No Security Considerations Section (by seanturner)
https://github.com/tlswg/tls12-frozen/issues/8
- Nits complaint: 21
