[lamps] Re: I-D Action: draft-ietf-lamps-pq-composite-kem-12.txt

Russ Housley <housley@vigilsec.com> Thu, 08 January 2026 18:12 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@mail2.ietf.org
Delivered-To: spasm@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id D37B5A4EC156 for <spasm@mail2.ietf.org>; Thu, 8 Jan 2026 10:12:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=vigilsec.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J42eCrCVO-tE for <spasm@mail2.ietf.org>; Thu, 8 Jan 2026 10:12:49 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (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 36B90A4EC150 for <spasm@ietf.org>; Thu, 8 Jan 2026 10:12:49 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id DF45B1A0B85 for <spasm@ietf.org>; Thu, 8 Jan 2026 13:12:48 -0500 (EST)
Received: from smtpclient.apple (pool-96-255-71-95.washdc.fios.verizon.net [96.255.71.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id CDB291A1AEC for <spasm@ietf.org>; Thu, 8 Jan 2026 13:12:48 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Date: Thu, 08 Jan 2026 13:12:38 -0500
References: <176784783112.3939517.13561401651567448441@dt-datatracker-5656579b89-p6k4r>
To: spasm@ietf.org
In-Reply-To: <176784783112.3939517.13561401651567448441@dt-datatracker-5656579b89-p6k4r>
Message-Id: <63D87BF3-D1F7-463D-B4E8-638BAD43E06E@vigilsec.com>
X-Mailer: Apple Mail (2.3826.700.81)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=from:content-type:content-transfer-encoding:mime-version:subject:date:references:to:in-reply-to:message-id; s=pair-202402141609; bh=RBaW2xMWWiHb2x8JjL4csZmTKZ2Ny2T9zgVwGKpNaqs=; b=FMpAbWyeYxn3CPCyHgnoCjj2wMuyYbmD4yzzawx+fxz0WZAPaXbregwJtJ5gHx+0HMXPFh5lvhh3xCp1IMZHPxzEImIxDOkb1tP4W1l+jfFuY7kAoy2k+pPs1iWXzCT/j0v5M8ljZ2GX9O86t2XB/680s7Xear+K7BRDufAlv/uji+vIQS7XKPuL2AthxOm4h3uFyKXa5m2S9ry9cfgj4cOXmWB3gfP6vTfz+ywhzQoaNzyrrXlH2GU+/6tb0muIH6fSsGqsv/eubeyu/cAVJCtYLYpOpuVQF3gUoYKV4WTRGpiaUEFjrBdnEMyFnAJ2KzN5+Z7NL8E9mqcLKk8b9A==
X-Scanned-By: mailmunge 3.09
Message-ID-Hash: E7MPMTTPXSHKGKTK62TSEBH5HGYYQGPT
X-Message-ID-Hash: E7MPMTTPXSHKGKTK62TSEBH5HGYYQGPT
X-MailFrom: housley@vigilsec.com
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [lamps] Re: I-D Action: draft-ietf-lamps-pq-composite-kem-12.txt
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/tLPz7aueeqEANv92JJ3isR8aHPw>
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>

his revision include a new Section 3.1.1, and this sentence:

   In cases	
   where the private keys never leave the module or are otherwise not	
   required to interoperate with other cryptographic modules, it is not	
   required for interoperability for the private keys to match the	
   format described in this specification.

I think it would be better to say why a private key format is specified,
and then say when an implementation might do its own thing.

Russ


> On Jan 7, 2026, at 11:50 PM, internet-drafts@ietf.org wrote:
> 
> Internet-Draft draft-ietf-lamps-pq-composite-kem-12.txt is now available. It
> is a work item of the Limited Additional Mechanisms for PKIX and SMIME (LAMPS)
> WG of the IETF.
> 
>   Title:   Composite ML-KEM for use in X.509 Public Key Infrastructure
>   Authors: Mike Ounsworth
>            John Gray
>            Massimiliano Pala
>            Jan Klaussner
>            Scott Fluhrer
>   Name:    draft-ietf-lamps-pq-composite-kem-12.txt
>   Pages:   109
>   Dates:   2026-01-07
> 
> Abstract:
> 
>   This document defines combinations of US NIST ML-KEM [FIPS.203] in
>   hybrid with traditional algorithms RSA-OAEP, ECDH, X25519, and X448.
>   These combinations are tailored to meet security best practices and
>   regulatory guidelines.  Composite ML-KEM is applicable in any
>   application that uses X.509 or PKIX data structures that accept ML-
>   KEM, but where the operator wants extra protection against breaks or
>   catastrophic bugs in ML-KEM.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-lamps-pq-composite-kem/
> 
> There is also an HTMLized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-lamps-pq-composite-kem-12
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-lamps-pq-composite-kem-12
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> Spasm mailing list -- spasm@ietf.org
> To unsubscribe send an email to spasm-leave@ietf.org