[TLS] Review of draft-kato-tls-rfc4132bis-00
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[TLS] Review of draft-kato-tls-rfc4132bis-00
$Id: draft-kato-tls-rfc4132bis-00-rev.txt,v 1.1 2008/03/04 17:32:45 ekr Exp $
It's not clear to me why this document isn't simply an updated
cut-and-paste of RFC 4132 with additional ciphers. In particular,
this draft contains a large number of grammatical errors which
have already been ironed out of 4132.
It's not clear to me that we really need the combinatoric
explosion of all possible key exchange and signature
algorithms with Camellia.
I think it's a bad idea to specify HMAC-SHA-1 for use with
the SHA-1 cipher suites. Note that all the suites in
TLS 1.2 use SHA-256.
Why do we need a mandatory to implement Camellia cipher
suite? TLS is quite capable of negotiating this stuff.
-Ekr
_______________________________________________
TLS mailing list
TLS at ietf.org
https://www.ietf.org/mailman/listinfo/tls
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.