[pkix] [Technical Errata Reported] RFC5934 (2668)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 10 December 2010 00:39 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pkix@core3.amsl.com
Delivered-To: pkix@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 882E228C14B for <pkix@core3.amsl.com>; Thu, 9 Dec 2010 16:39:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.357
X-Spam-Level:
X-Spam-Status: No, score=-102.357 tagged_above=-999 required=5 tests=[AWL=0.243, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TBcH63iZXy5J for <pkix@core3.amsl.com>; Thu, 9 Dec 2010 16:39:12 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 64A0928B797 for <pkix@ietf.org>; Thu, 9 Dec 2010 16:39:12 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E8FC4E070A; Thu, 9 Dec 2010 16:40:42 -0800 (PST)
To: housley@vigilsec.com, srashmo@radium.ncsc.mil, cwallace@cygnacom.com, turners@ieca.com, tim.polk@nist.gov, kent@bbn.com, stefan@aaa-sec.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20101210004042.E8FC4E070A@rfc-editor.org>
Date: Thu, 09 Dec 2010 16:40:42 -0800
X-Mailman-Approved-At: Fri, 10 Dec 2010 07:38:59 -0800
Cc: pkix@ietf.org, ietf@augustcellars.com, rfc-editor@rfc-editor.org
Subject: [pkix] [Technical Errata Reported] RFC5934 (2668)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pkix>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Dec 2010 00:39:16 -0000
The following errata report has been submitted for RFC5934, "Trust Anchor Management Protocol (TAMP)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5934&eid=2668 -------------------------------------- Type: Technical Reported by: Jim Schaad <ietf@augustcellars.com> Section: A.1 Original Text ------------- 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 } Corrected Text -------------- INSERT IN THE 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) } ORIG-1 - text is removed and not replaced 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. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5934 (draft-ietf-pkix-tamp-08) -------------------------------------- Title : Trust Anchor Management Protocol (TAMP) Publication Date : August 2010 Author(s) : R. Housley, S. Ashmore, C. Wallace Category : PROPOSED STANDARD Source : Public-Key Infrastructure (X.509) Area : Security Stream : IETF Verifying Party : IESG
- [pkix] [Technical Errata Reported] RFC5934 (2668) RFC Errata System