[smime] [Errata Verified] RFC3183 (3757)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 03 December 2013 17:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: smime@ietfa.amsl.com
Delivered-To: smime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC4611ACCE5; Tue, 3 Dec 2013 09:17:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ukn238bXVZIh; Tue, 3 Dec 2013 09:17:25 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:126c::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 356221AC499; Tue, 3 Dec 2013 09:17:25 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 514CC72E0D9; Tue, 3 Dec 2013 09:16:51 -0800 (PST)
To: housley@vigilsec.com, tbdean@QinetiQ.com, wjottaway@QinetiQ.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20131203171651.514CC72E0D9@rfc-editor.org>
Date: Tue, 03 Dec 2013 09:16:51 -0800
Cc: rfc-editor@rfc-editor.org, iesg@ietf.org, smime@ietf.org
Subject: [smime] [Errata Verified] RFC3183 (3757)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime/>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Dec 2013 17:17:27 -0000

The following errata report has been verified for RFC3183,
"Domain Security Services using S/MIME". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3183&eid=3757

--------------------------------------
Status: Verified
Type: Technical

Reported by: Russ Housley <housley@vigilsec.com>
Date Reported: 2013-10-18
Verified by: Sean Turner (IESG)

Section: 3.1.2

Original Text
-------------
   An S/MIME signed attribute is used to indicate the type of signature.
   This should be used in conjunction with the naming conventions
   specified in the previous section.  When an S/MIME signed message
   containing the signature type attribute is received it triggers the
   software to verify that the correct naming convention has been used.

   The ASN.1 [4] notation of this attribute is: -

      SignatureType ::= SEQUENCE OF OBJECT IDENTIFIER


Corrected Text
--------------
   An S/MIME signed attribute is used to indicate the type of signature.
   This should be used in conjunction with the naming conventions
   specified in the previous section.  When an S/MIME signed message
   containing the signature type attribute is received it triggers the
   software to verify that the correct naming convention has been used.

   The following object identifier identifies the SignatureType
   attribute:

      id-aa-signatureType OBJECT IDENTIFIER ::= { iso(1) 
          member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9) 28 }

   The ASN.1 [4] notation of this attribute is:

      SignatureType ::= SEQUENCE OF OBJECT IDENTIFIER


Notes
-----
The specification provides the syntax for the SignatureType attribute,
but it fails to provide the object identifier for the attribute.  The object
identifier was assigned, but for some reason it is not provided in the
document.

--------------------------------------
RFC3183 (draft-ietf-smime-domsec-09)
--------------------------------------
Title               : Domain Security Services using S/MIME
Publication Date    : October 2001
Author(s)           : T. Dean, W. Ottaway
Category            : EXPERIMENTAL
Source              : S/MIME Mail Security
Area                : Security
Stream              : IETF
Verifying Party     : IESG