[lamps] New Liaison Statement, "RE: PQC migration of CMS signatures"

Liaison Statement Management Tool <statements@ietf.org> Wed, 17 June 2026 21:39 UTC

Return-Path: <statements@ietf.org>
X-Original-To: spasm@ietf.org
Delivered-To: spasm@mail2.ietf.org
Received: from [10.244.21.151] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 0A42C102FC89F; Wed, 17 Jun 2026 14:39:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1781732392; bh=IdqQEiP5mEdgSDz/fU789UUTFAhUgUrzQ41QKNfITfY=; h=From:To:Cc:Subject:Date; b=EnRILuWceAAbxqO4TKQ9IHREn9vswC1zSKFliTyX7Xxu/I/o6pcpapXyTafNyQT8X B2lW7OE+a0mt6qVw9e44dPSLek5HRLugu1QQ/LdWlx0qn9EgK89Pws7jj8nQ/SGXIL QNGyZF7Nv+wnOqbnxW5oJbrWZfZH3WfvLZhzDrEc=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Liaison Statement Management Tool <statements@ietf.org>
To: ETSI ESIsupport <ESIsupport@etsi.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.67.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178173239172.696474.2012705891120657458@dt-datatracker-f9b87776f-8pmmg>
Date: Wed, 17 Jun 2026 14:39:51 -0700
Message-ID-Hash: TBMBLSDNUPSC6I4K2G5NFV2ILSXNLTRO
X-Message-ID-Hash: TBMBLSDNUPSC6I4K2G5NFV2ILSXNLTRO
X-MailFrom: statements@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-spasm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Christopher Inacio <stndrds-inacio@andrew.cmu.edu>, Deb Cooley <debcooley1@gmail.com>, Jean-Emmanuel Perez Hernandez <jean-emmanuel.perez.hernandez@nowina.lu>, LAMPS WG <spasm@ietf.org>, Lucas PRABEL <lucas.prabel@huawei.com>, Nick Pope <nick.pope@secstanassoc.com>, Russ Housley <housley@vigilsec.com>, Tim Hollebeek <tim.hollebeek@digicert.com>, liaison-coordination@iab.org
X-Mailman-Version: 3.3.9rc6
Subject: [lamps] New Liaison Statement, "RE: PQC migration of CMS signatures"
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/_FTjuA25FgIifrnYuGYqc_Y9-qc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Owner: <mailto:spasm-owner@ietf.org>
List-Post: <mailto:spasm@ietf.org>
List-Subscribe: <mailto:spasm-join@ietf.org>
List-Unsubscribe: <mailto:spasm-leave@ietf.org>

Title: RE: PQC migration of CMS signatures
Submission Date: 2026-06-17
URL of the IETF Web page: https://datatracker.ietf.org/liaison/2199/

To: ETSI TC ESI PQC WG
From: Limited Additional Mechanisms for PKIX and SMIME (lamps)
Purpose: In response


Email Addresses
---------------
From: Russ Housley <housley@vigilsec.com>
To: ETSI ESIsupport <ESIsupport@etsi.org>
Cc: Christopher Inacio <stndrds-inacio@andrew.cmu.edu>,Deb Cooley <debcooley1@gmail.com>
Response Contacts: Russ Housley <housley@vigilsec.com>, Tim Hollebeek <tim.hollebeek@digicert.com>, LAMPS WG <spasm@ietf.org>
Technical Contacts: Nick Pope <nick.pope@secstanassoc.com>, Jean-Emmanuel Perez Hernandez <jean-emmanuel.perez.hernandez@nowina.lu>, Lucas PRABEL <lucas.prabel@huawei.com>


Referenced liaison: PQC migration of CMS signatures (https://datatracker.ietf.org/liaison/2197/)

Body: Since the CAdES specifications rely in particular on RFC 5652, the LAMPS WG wants ETSI TC EIS to be aware of the work that has already been accomplished to prepare CMS for use with PQC algorithms.  First, RFC 9629 specifies the use of Key Encapsulation Mechanism (KEM) Algorithms in the CMS.  Second, several specifications for the use of PQC signature algorithms have been written, including: RFC 9708, RFC 9814, and RFC 9882.  More are on the way, including support for composite signature algorithms.  Third, several specifications for the use of PQC KEM algorithms have been written, including: RFC 9936.  More are on the way, including support for composite KEM algorithms.

Since the EN 319 412 technical specification series build on RFC 5280, the LAMPS WG wants ETSI TC EIS to be aware of the work that has already been
accomplished to prepare public key certificates for use with PQC algorithms. First, several specifications for the use of PQC signature algorithms have  been written, including: RFC 9802, RFC 9881, and RFC 9909.  More are on the way, including support for composite signature algorithms.  Second, RFC 9935 specifies the way to carry an ML-KEM public key as the certificate subject public key.  Similar specifications are on the way for other PQC KEMs, including support for composite KEM algorithms.

US NIST is assigning algorithm identifiers for PQC algorithms that they specify, and you will see that the RFCs listed above use these algorithm identifiers for these algorithms.

ISO has assigned algorithm identifiers for the FrodoKEM algorithm.  The LAMPS WG is considering adopting specifications related to this algorithm, and these use the ISO-assigned algorithm identifiers.

IANA has assigned algorithm identifiers for HSS/LMS, XMSS, XMSS^MT, composite KEM algorithms, and composite signature algorithms.  These algorithm identifiers are included in this registry:

https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.6

Best Regards,
Russ and Tim
Attachments:

No document has been attached