RFC Errata
Found 1 record.
Status: Verified (1)
RFC 5934, "Trust Anchor Management Protocol (TAMP)", August 2010
Source of RFC: pkix (sec)
Errata ID: 2668
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:
ORIG-1
CONTENT-TYPE ::= TYPE-IDENTIFIER
ORIG-2
tamp-status-query CONTENT-TYPE ::=
{ TAMPStatusQuery IDENTIFIED BY id-ct-TAMP-statusQuery }
ORIG-3
tamp-status-response CONTENT-TYPE ::=
{ TAMPStatusResponse IDENTIFIED BY id-ct-TAMP-statusResponse }
ORIG-4
tamp-update CONTENT-TYPE ::=
{ TAMPUpdate IDENTIFIED BY id-ct-TAMP-update }
ORIG-5
tamp-update-confirm CONTENT-TYPE ::=
{ TAMPUpdateConfirm IDENTIFIED BY id-ct-TAMP-updateConfirm }
ORIG-6
tamp-apex-update CONTENT-TYPE ::=
{ TYPE TAMPApexUpdate IDENTIFIED BY id-ct-TAMP-apexUpdate }
ORIG-7
tamp-apex-update-confirm CONTENT-TYPE ::=
{ TAMPApexUpdateConfirm IDENTIFIED BY
id-ct-TAMP-apexUpdateConfirm }
ORIG-8
tamp-community-update CONTENT-TYPE ::=
{ TAMPCommunityUpdate IDENTIFIED BY id-ct-TAMP-communityUpdate }
ORIG-9
tamp-community-update-confirm CONTENT-TYPE ::=
{ TAMPCommunityUpdateConfirm IDENTIFIED BY
id-ct-TAMP-communityUpdateConfirm }
ORIG-10
tamp-sequence-number-adjust CONTENT-TYPE ::=
{ SequenceNumberAdjust IDENTIFIED BY id-ct-TAMP-seqNumAdjust }
ORIG-11
tamp-sequence-number-adjust-confirm CONTENT-TYPE ::=
{ SequenceNumberAdjustConfirm IDENTIFIED BY
id-ct-TAMP-seqNumAdjustConfirm }
ORIG-12
tamp-error CONTENT-TYPE ::=
{ TAMPError IDENTIFIED BY id-ct-TAMP-error }
It should say:
INSERT IN THE IMPORTS SECTION BEFORE THE FINAL SEMI-COLON
CONTENT-TYPE
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) }
ORIG-2
tamp-status-query CONTENT-TYPE ::=
{ TYPE TAMPStatusQuery IDENTIFIED BY id-ct-TAMP-statusQuery }
ORIG-3
tamp-status-response CONTENT-TYPE ::=
{ TYPE TAMPStatusResponse IDENTIFIED BY id-ct-TAMP-statusResponse }
ORIG-4
tamp-update CONTENT-TYPE ::=
{ TYPE TAMPUpdate IDENTIFIED BY id-ct-TAMP-update }
ORIG-5
tamp-update-confirm CONTENT-TYPE ::=
{ TYPE TAMPUpdateConfirm IDENTIFIED BY id-ct-TAMP-updateConfirm }
ORIG-6
tamp-apex-update CONTENT-TYPE ::=
{ TYPE TAMPApexUpdate IDENTIFIED BY id-ct-TAMP-apexUpdate }
ORIG-7
tamp-apex-update-confirm CONTENT-TYPE ::=
{ TYPE TAMPApexUpdateConfirm IDENTIFIED BY
id-ct-TAMP-apexUpdateConfirm }
ORIG-8
tamp-community-update CONTENT-TYPE ::=
{ TYPE TAMPCommunityUpdate IDENTIFIED BY id-ct-TAMP-communityUpdate }
ORIG-9
tamp-community-update-confirm CONTENT-TYPE ::=
{ TYPE TAMPCommunityUpdateConfirm IDENTIFIED BY
id-ct-TAMP-communityUpdateConfirm }
ORIG-10
tamp-sequence-number-adjust CONTENT-TYPE ::=
{ TYPE SequenceNumberAdjust IDENTIFIED BY id-ct-TAMP-seqNumAdjust }
ORIG-11
tamp-sequence-number-adjust-confirm CONTENT-TYPE ::=
{ TYPE SequenceNumberAdjustConfirm IDENTIFIED BY
id-ct-TAMP-seqNumAdjustConfirm }
ORIG-12
tamp-error CONTENT-TYPE ::=
{ TYPE TAMPError IDENTIFIED BY id-ct-TAMP-error }
Notes:
This errata addresses two different issues:
1. The exact same class definition, not a clone, must be used in order to have the ASN.1 object sets work correctly. This is the reason for the change in the definition of the CONTENT-TYPE class.
2. An errata on RFC5911 added the keyword TYPE so that a content type can be defined as not having an associated ASN.1 type (either because it is raw data or is a different structured data type such as XML). This means that all objects of the CONTENT-TYPE class need to have the word TYPE added to them.
Note also that the text is removed and not replaced for ORIG-1
