Comment by throw0101a

2 days ago

> While Kyber may have been the winning algorithm, there will be great preference in the community for Bernstein's NTRU Prime.

There's IETF WG drafts for use of Kyber / ML-KEM, but none for NTRU, so I'm not sure about that:

* https://datatracker.ietf.org/doc/draft-ietf-tls-mlkem/

* https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-mlkem/

* https://datatracker.ietf.org/doc/draft-ietf-tls-hybrid-desig...

* https://datatracker.ietf.org/doc/draft-ietf-ipsecme-ikev2-ml...

And given that NTRU made it to the third round, and NTRU Prime is labelled as an alternative, I'm not how strong a claim Bernstein can make to being ill-treated by NIST.

5 comments

throw0101a

Reply
chasil  1 day ago

The djb suites are well-represented both in TLS and SSH.

While NTRU Prime is not implemented in TLS, if it has even half the lifespan of DSA in SSH then it will be quite long lived.

  • throw0101a  1 day ago

    The context of the conversation is "Bernstein's NTRU Prime", which is not present for TLS in any draft, and for SSH there are only personal / non-WG drafts.

    So while some SSH folks just happened to pick NTRU after looking at the options at a particular point in time, some of the other most widely deployed systems (TLS, IPsec) will not be using it. So I'm not quite sure how defendable the "great preference" claim is.