…e Revocation List (CRL) Profile", RFC 5280 , DOI 10.17487/RFC5280, May 2008, >. RFC5480 ] Turner, S., Brown, D., Yiu, K., Housley, R., and T. Polk, "Elliptic Curve Cryptography Subject Public Key Information", RFC 5480 , DOI 10.17487/RFC5480, March 2009, >. RFC5958 ] Turner, S., …

…field of spki is not equal to the id-ecPublicKey object identifier defined in [ RFC5480 ], then throw a DataError . If the parameters field of the algorithm AlgorithmIdentifier field of spki is absent, then throw a DataError . Let params be the parameters field of the algorithm A…

…2.3.1 of [ RFC3279 ] DSA See section 2.3.2 of [ RFC3279 ] EC See section 2 of [ RFC5480 ] Specifications that define additional key types should provide such a normative reference for their own key types where possible. Schema Definition : <!-- targetNamespace="http://www.w3.org/…

…field of spki is not equal to the id-ecPublicKey object identifier defined in [ RFC5480 ], then throw a DataError . If the parameters field of the algorithm AlgorithmIdentifier field of spki is absent, then throw a DataError . Let params be the parameters field of the algorithm A…

…R OPTIONAL, y CHOICE { b BOOLEAN, f FieldElement } OPTIONAL } I think using the RFC5480 in the Corrected Text would be cleaner than RFC4492, but the former is not an existing reference, so we would need to update section 12 also. RSASSA-PSS RSAE algorithms: Indicates a signature …

…yInfo that indicates an algorithm of id-ecPublicKey with namedCurves secp256r1 [RFC5480]; the public key format is uncompressed [RFC5480]; the hash algorithm is SHA-256; if included, the key usage extension indicates digitalSignature. Certificates MUST be signed with ECDSA using …

…al TLS ciphersuites in conjunction with a single server certificate. Given that RFC5480 section 3 explicitly permits digitalSignature+keyAgreement in an ECC leaf certificate, I think it's likely that my proposed Corrected Text conveys the RFC5280 authors' intended meaning. Errata…

…al TLS ciphersuites in conjunction with a single server certificate. Given that RFC5480 section 3 explicitly permits digitalSignature+keyAgreement in an ECC leaf certificate, I think it's likely that my proposed Corrected Text conveys the RFC5280 authors' intended meaning. Errata…