RFC Errata
Found 2 records.
Status: Verified (2)
RFC 5636, "Traceable Anonymous Certificate", August 2009
Source of RFC: pkix (sec)
Errata ID: 5935
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Russ Housley
Date Reported: 2019-12-12
Verifier Name: Deb Cooley
Date Verified: 2025-01-24
Section Appendix A says:
-- Imports from RFC 3280 [PROFILE], Appendix A.1
AlgorithmIdentifier, Certificate, CertificateList,
CertificateSerialNumber, Name FROM PKIX1Explicit88
{ iso(1) identified-organization(3) dod(6)
internet(1) security(5) mechanisms(5) pkix(7)
mod(0) pkix1-explicit(18) }
-- Imports from CMS
ContentInfo, SignedData FROM
CryptographicMessageSyntax2004{ iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) modules(0) cms-2004(24)}
It should say:
-- Imports from CMS
ContentInfo, ContentType FROM
CryptographicMessageSyntax2004{ iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) modules(0) cms-2004(24)} ;
Notes:
None of the imports from RFC 3280 are used. The import list from RFC 3852 should not include SignedData, and it should include ContentType. A semi-colon is needed at the end of the IMPORTS statement.
Errata ID: 5936
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Russ Housley
Date Reported: 2019-12-12
Verifier Name: Deb Cooley
Date Verified: 2025-01-24
Section Appendix A says:
DEFINITIONS IMPLICIT TAGS ::=
It should say:
RFC5636Module DEFINITIONS IMPLICIT TAGS ::=
Notes:
A module name is needed for the module to properly compile.
