Re: [TLS] Re: TLS 1.2 draft

Pasi.Eronen@nokia.com wrote:
>
> No, this is not exactly what pkcs-1v2-1errata.txt says; there
> is additional text in the errata:
> 
>   Exception: When formatting the DigestInfoValue in EMSA-PKCS1-V1.5 
>   (see 9.2), the parameters field associated with id-sha1, id-sha256, 
>   id-sha384 and id-sha512 SHALL have a value of type NULL. This is to 
>   maintain compatibility with existing implementations and with the 
>   numeric information values already published for EMSA-PKCS1-V1.5 
>   which are also reflected in IEEE 1363a-2004[27].
> 
> In other words: AlgorithmIdentifier is used in several different
> places, and the text "MUST accept both, SHOULD omit" applies to 
> all of those *except* one place (EMSA-PKCS1-V1.5). But that place
> happens to be the one we care about for TLS 1.2 (ServerKeyExchange
> and CertificateVerify messages)!

Pasi, you're right.  Thank you for correcting me.  I didn't
see the Exception paragraph.  This is complicated.

> I think we should follow pkcs-1v2-1errata.txt and IEEE 1363a-2004
> (which both agree) here, unless there are compelling arguments
> against it...

Since pkcs-1v2-1errata.txt (Dec. 2005) is newer in RFC 3447
(Feb. 2003), I agree with your recommendation.

Wan-Teh

_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls