> -----Original Message----- > From: Cfrg <cfrg-boun...@irtf.org> On Behalf Of Salz, Rich > Subject: [Cfrg] NIST crypto group and HKDF (and therefore TLS 1.3) > > NIST SP 800-56C (Recommendation for Key-Derivation Methods in Key- > Establishment Schemes) is currently a draft in review.... with a deadline of > May 15. That is not a lot of time. The NIST crypto group is currently > unlikely > to include HKDF, which means that TLS 1.3 would not be part of FIPS. The > CMVP folks at NIST understand this, and agree that this would be bad; they > are > looking at adding it, perhaps via an Implementation Guidance update.
[DB] But NIST Draft SP 800-56Cr2 cites RFC 5869, which is HKDF, and says HKDF is a version of 56C Section 5.1. So, I had thought that 56C would allow HKDF. What am I missing? ---------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
