RFC Errata

Errata Search

Source of RFC  
Summary Table Full Records

RFC 5914, "Trust Anchor Format", June 2010

Source of RFC: pkix (sec)
See Also: RFC 5914 w/ inline errata

Errata ID: 2667
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Jim Schaad
Date Reported: 2010-12-09
Verifier Name: Tim Polk
Date Verified: 2011-03-26

Section A.1 says:


   trust-anchor-list PKCS7-CONTENT-TYPE ::=
       { TrustAnchorList IDENTIFIED BY id-ct-trustAnchorList }

It should say:

INSERT INTO IMPORTS SECTION before the final semi-colon

   FROM CryptographicMessageSyntax-2009 -- from [RFC5911]
      { iso(1) member-body(2) us(840) rsadsi(113549)
      pkcs(1) pkcs-9(9) smime(16) modules(0)
      id-mod-cms-2004-02(41) }


   trust-anchor-list CONTENT-TYPE ::=
       { TYPE TrustAnchorList IDENTIFIED BY id-ct-trustAnchorList }


The content type is designed to be placed into a CMS SignedData object. Since the exact same class definition (not a syntaxically identicial one) needs to be used to get object sets to work correctly, the defintion of the content type must be updated to reference the identical one defined in the CMS module.

A future version should additionally note that the content type is to be added to the ContentSet object set in the CMS module.

Report New Errata

Advanced Search