Re: sntrup761x25519-sha512
"Mark Baushke (ietf)" <[email protected]> Mon, 15 May 2023 12:45:43 -0700
| Newsgroups | gmane.ietf.curdle,gmane.ietf.secsh |
|---|---|
| Message-ID | <[email protected]> |
Hi, > On May 15, 2023, at 6:52 AM, Salz, Rich <rsalz=40akamai.com-Tr9gZwTxerDR74oF6e/[email protected]> wrote: > >> (Work on how to use those curves can start earlier, but publication > should wait until algorithms are official. > > Can't do interop experiments without putting entries in the IANA registries which often require some kind of documentation (depending on what the registry says). I believe that interoperability testing is already possible using sntrup761x25519-sha512-ZT/[email protected] (as of OpenSSH 9.3 released 2023-03-15). As this identifier is a proper "PRIVATE USE" extension, it is not suitable for Key Exchange Method Names in the IANA (URL: https://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml#ssh-parameters-16 ) table. An RFC, such as draft-josefsson-ntruprime-ssh-00, would be needed to define the table entry for sntrup761x25519-sha512 for IANA to update the Key Exchange Method Names table. I personally believe that using the @openssh.com extension is sufficient until final NIST candidate parameters are published. Be safe, stay healthy -- Mark