[smime] [Errata Held for Document Update] RFC5753 (4777)

RFC Errata System <rfc-editor@rfc-editor.org> Sun, 28 December 2025 15:14 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: smime@ietf.org
Delivered-To: smime@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 65470A0093DD; Sun, 28 Dec 2025 07:14:39 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 3832BC000CD7; Sun, 28 Dec 2025 07:14:39 -0800 (PST)
To: ietf@augustcellars.com, turners@ieca.com, dbrown@certicom.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20251228151439.3832BC000CD7@rfcpa.rfc-editor.org>
Date: Sun, 28 Dec 2025 07:14:39 -0800
Message-ID-Hash: FPS32SHD55C2URG3OWSF4SBNUQZ5EZJZ
X-Message-ID-Hash: FPS32SHD55C2URG3OWSF4SBNUQZ5EZJZ
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-smime.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: debcooley1@gmail.com, iesg@ietf.org, smime@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [smime] [Errata Held for Document Update] RFC5753 (4777)
List-Id: SMIME Working Group <smime.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/3SgFyZVQs_RXWCfBpmOq7YI4bMk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/smime>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Owner: <mailto:smime-owner@ietf.org>
List-Post: <mailto:smime@ietf.org>
List-Subscribe: <mailto:smime-join@ietf.org>
List-Unsubscribe: <mailto:smime-leave@ietf.org>

The following errata report has been held for document update 
for RFC5753, "Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid4777

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Jim Schaad <ietf@augustcellars.com>
Date Reported: 2016-08-13
Held by: Deb Cooley (IESG)

Section: 3.1.1

Original Text
-------------
-  originator MUST be the alternative originatorKey.  The
      originatorKey algorithm field MUST contain the id-ecPublicKey
      object identifier (see Section 7.1.2).  The parameters associated
      with id-ecPublicKey MUST be absent, ECParameters, or NULL.  The
      parameters associated with id-ecPublicKey SHOULD be absent or
      ECParameters, and NULL is allowed to support legacy
      implementations.  The previous version of this document required
      NULL to be present.  If the parameters are ECParameters, then they
      MUST be namedCurve.  The originatorKey publicKey field MUST
      contain the DER encoding of the value of the ASN.1 type ECPoint
      (see Section 7.2), which represents the sending agent's ephemeral
      EC public key.  The ECPoint in uncompressed form MUST be
      supported.

Corrected Text
--------------
-  originator MUST be the alternative originatorKey.  The
      originatorKey algorithm field MUST contain the id-ecPublicKey
      object identifier (see Section 7.1.2).  The parameters associated
      with id-ecPublicKey MUST be absent, ECParameters, or NULL.  The
      parameters associated with id-ecPublicKey SHOULD be absent or
      ECParameters, and NULL is allowed to support legacy
      implementations.  The previous version of this document required
      NULL to be present.  If the parameters are ECParameters, then they
      MUST be namedCurve.  The originatorKey publicKey field MUST
      contain the encoded public key as defined in [X9.62].  The hybred
      form MUST NOT be used.  The ECPoint in uncompressed form MUST be
      supported.  This mirrors the same format used in public key 
      certificates as defined in Section 2.2 of [RFC5480].

Notes
-----
There is a problem in that for ECPoints, the public key is defined to be encoded differently in this document than it is in a public key certificate.  The difference is the presence of the ASN.1 OCTET STRING wrapper.

OpenSSL and BouncyCastle both use the unwrapped version per Dr. Stephen Henson note to me in mail.

This error is also present in sections 3.1.2, 3.1.3, 3.2.1, 3.2.2, 7.2

--------------------------------------
RFC5753 (draft-ietf-smime-3278bis-09)
--------------------------------------
Title               : Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)
Publication Date    : January 2010
Author(s)           : S. Turner, D. Brown
Category            : INFORMATIONAL
Source              : S/MIME Mail Security
Stream              : IETF
Verifying Party     : IESG