On 21 December 2016 at 01:45, Russ Housley wrote:
> I am curious about the choice of hash function for
> TLS_ECDHE_PSK_WITH_AES_256_CCM_8_SHA256. All of the other AES-256
> ciphersuites defined in this document that use SHA-384. Why does the one
> with a truncated authentication tag use SHA-2
> This is the working group last call for the "ECDHE_PSK with AES-GCM and
> AES-CCM CSs for TLS” draft
I am curious about the choice of hash function for
TLS_ECDHE_PSK_WITH_AES_256_CCM_8_SHA256. All of the other AES-256 ciphersuites
defined in this document that use SHA-384. Why does the one
This is the working group last call for the "ECDHE_PSK with AES-GCM and AES-CCM
CSs for TLS" draft available at
http://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-psk-aead/. Please review
the document and send your comments to the list by 9 December 2016.
Thanks,
J&S
___
