ietf-smime
[Top] [All Lists]

Re: A contradiction between RFC3852 and RFC3278

2009-03-16 13:26:23

Maxim,

The paragraph now says:

signatureAlgorithm contains the signature algorithm identifier (see Section 7.1.3): ecdsa-with-SHA1, ecdsa-with-SHA224, ecdsa-with-SHA256, ecdsa-with-SHA384, or ecdsa-with-SHA512.

How about we add the following to the end of it:

The hash algorithm identified in the name of the signature algorithm MUST be the same as the digestAlgorithm (e.g., digestAlgorithm is id-sha256 therefore signatureAlgorithm is ecdsa-with-SHA256).

spt


Maxim Masiutin wrote:
Hello Sean,

Maybe we should alter the description of signatureAlgorithm in section 2.1.1 of 
draft-smime-3278bis, to the following:

- signatureAlgorithm contains the signature algorithm identifier (see Section 7.1.3) where the public key part of it is ECDSA and the hash part MUST refer to the same algorithm as specified in the digestAlgorithm field. signatureAlgorithm MUST be one of the following ecdsa-with-SHA1, ecdsa-with-SHA224, ecdsa-with-SHA256, ecdsa-with-SHA384, or ecdsa-with-SHA512.


<Prev in Thread] Current Thread [Next in Thread>