Re: [TLS] draft-rescorla-tls-suiteb-06.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [TLS] draft-rescorla-tls-suiteb-06.txt



Rob Dugal wrote:
> 
> From section 4:
>    Server and client certificates used to establish a Suite B-compliant
>    connection MUST be signed with ECDSA.  For certificates used at the
>    128-bit security level, the subject public key MUST use the P-256
>    curve, and the digital signature MUST be calculated using the P-256
>    curve and the SHA-256 hash algorithm.  For certificates used at the
>    192-bit security level, the subject public key MUST use the P-384
>    curve, and the digital signature MUST be calculated using the P-384
>    curve and the SHA-384 hash algorithm.
> 
> 
> Does this only apply to the client/server certificates or every
> certificate in the client/server chain?

Intuitively I would expect an exact match requirement for the
end-entity cert and a "at least" requirement for the CA hierarchy
up to and including the TA or rootCA cert.

The description should probably be expanded and the requirements for
the CAs / path certs explicitly described to clarify the situation.


-Martin
_______________________________________________
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.