[CFRG] Re: RG Last Call on draft-irtf-cfrg-hybrid-kems-12 and draft-irtf-cfrg-concrete-hybrid-kems-04

Russ Housley <housley@vigilsec.com> Wed, 08 July 2026 14:47 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: cfrg@mail2.ietf.org
Delivered-To: cfrg@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A6CA511307561 for <cfrg@mail2.ietf.org>; Wed, 8 Jul 2026 07:47:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1783522054; bh=1V8RLodEAP7WEB6d3Fb4jvUfalDjFs3TMePsn0zeZZ0=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=rXHEKOnf0G4TbU/yauI0nFOTdsqBDMW9mvH/VrXeBhyjVe+8HLd8sxAQwNGc51RfY iq3kpwrMehG09plqb3IyizxShclFUP4gx7S13Pkwze2RoV9qxkA0eyip4MRUaHXhKm 2sR2g87aWBC7iU2a6kvt9+Y/3aimCLSbT9NSQZ1s=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 oMb9YFCfo5yN for <cfrg@mail2.ietf.org>; Wed, 8 Jul 2026 07:47:33 -0700 (PDT)
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 E501E113074E1 for <cfrg@irtf.org>; Wed, 8 Jul 2026 07:47:29 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id B95FA1A1878; Wed, 8 Jul 2026 10:47:29 -0400 (EDT)
Received: from smtpclient.apple (pfs.iad.rg.net [198.180.150.6]) (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 966F31A1DD7; Wed, 8 Jul 2026 10:47:29 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <69214A81-16EB-4A77-9179-E21E06AD23A5@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5DBE82B0-D516-43A3-87A5-9C8C929CC99B"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\))
Date: Wed, 08 Jul 2026 10:47:19 -0400
In-Reply-To: <CAOjisRyRbkNif7mGD5TcoEcUsmbfeKE_wVHq+JH8VMySLcC47g@mail.gmail.com>
To: Nick Sullivan <nicholas.sullivan@gmail.com>
References: <CAOjisRyRbkNif7mGD5TcoEcUsmbfeKE_wVHq+JH8VMySLcC47g@mail.gmail.com>
X-Mailer: Apple Mail (2.3864.600.51.1.1)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=from:message-id:content-type:mime-version:subject:date:in-reply-to:cc:to:references; s=pair-202402141609; bh=KhbS5y9FhueFL/e3bKhIqyCn25cOCEuCaoJEvh41aeo=; b=bw6R0z3u7Tm3ZEUghmQUbfX8YHDUi0lX+3uuGlYAqtgLBzGm6pJQ0p15dtETEvQ9jfg1Lp+wWG3+XKgHq4LjkChpSDRVuSdqASkh4X6ebOT80m13WoRbJPdSVsDMDeNZreNBihq5W7D173l12DYjWj5zbX50GVUmfabdRsXM6tZyTph73lUUnY+8smCuHVD9GINECac22rfMmWyVX3Gd5u3caz/ortUYdnaziDjzhb7XLWXAf13sjGDp94Z++AN25xU2DyLKux5zjup1anIhNiFFSF3xI9C7i1MBevMRKau4aRH9tIDJDYnZUHZD7qvF9tKLfIDNvNG1dmnmCkEYJQ==
X-Scanned-By: mailmunge 3.09
Message-ID-Hash: RHVB4ZPA63KK2CB2OT3FWVN3C25KWY2F
X-Message-ID-Hash: RHVB4ZPA63KK2CB2OT3FWVN3C25KWY2F
X-MailFrom: housley@vigilsec.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-cfrg.irtf.org-0; header-match-cfrg.irtf.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: CFRG <cfrg@irtf.org>, "cfrg-chairs@ietf.org" <cfrg-chairs@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [CFRG] Re: RG Last Call on draft-irtf-cfrg-hybrid-kems-12 and draft-irtf-cfrg-concrete-hybrid-kems-04
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/JojV9K8wLO1xPXSOY8gQKPI4vFw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Owner: <mailto:cfrg-owner@irtf.org>
List-Post: <mailto:cfrg@irtf.org>
List-Subscribe: <mailto:cfrg-join@irtf.org>
List-Unsubscribe: <mailto:cfrg-leave@irtf.org>

I do not think the IANA registry is needed.  At this point, there seems to
be a lot of acceptance of draft-ietf-lamps-pq-composite-kem.  Thus, It
seems unlikely that more combinations will be specified that require new
labels to be registered.  Perhaps a registry can be set up in the future
when new labels are actually needed.

Russ

> On Jul 8, 2026, at 6:24 AM, Nick Sullivan <nicholas.sullivan@gmail.com> wrote:
> 
> Dear CFRG,
> 
> This message starts a two-week RG Last Call on two related documents. The last
> call ends on Wednesday July 22, 2026:
> 
>   Hybrid PQ/T Key Encapsulation Mechanisms (generic constructions)
>   draft-irtf-cfrg-hybrid-kems-12
>   https://www.ietf.org/archive/id/draft-irtf-cfrg-hybrid-kems-12.html
> 
>   Concrete Hybrid PQ/T Key Encapsulation Mechanisms
>   draft-irtf-cfrg-concrete-hybrid-kems-04
>   https://www.ietf.org/archive/id/draft-irtf-cfrg-concrete-hybrid-kems-04.html
> 
> Both are intended as Informational RFCs. Please reply on-list with your position
> on each document: ready to publish as-is, ready with specific changes, or not
> ready, together with the technical reasons. This feedback will help the chairs
> judge whether the documents are ready for IRSG review and publication.
> 
> The scope and approach of this work were settled when the group adopted it well
> over a year ago, and both drafts have developed on the list in the open since
> then. This last call is about whether the text is technically correct and
> complete, so please ground any objection in a specific problem with the
> documents. Detailed comments are best filed as issues on the repositories
> (https://github.com/cfrg/draft-irtf-cfrg-hybrid-kems,
> https://github.com/cfrg/draft-irtf-cfrg-concrete-hybrid-kems) positions belong
> here on the list.
> 
> Both documents were reviewed by the CFRG Crypto Review Panel ahead of this last
> call. The reviews are on the CFRG and crypto-panel lists:
> 
>   Thomas Pornin (NCC Group), 3 June 2026, reviewed the generic framework with a
>   focus on the constructions and reductions, and concluded that it describes a
>   secure construction, with editorial and technical comments now reflected in -12.
> 
>   Virendra Kumar (Qualcomm), 8 June 2026, reviewed the generic framework for
>   clarity, with notational comments now reflected in -12.
> 
>   Russ Housley (Vigil Security), 2 June 2026, reviewed both drafts and found the
>   constructions and instantiations as specified.
> 
> The current revisions incorporate changes proposed by the panel's comments.
> 
> Thank you,
> Nick, for the CFRG chairs
> _______________________________________________
> CFRG mailing list -- cfrg@irtf.org
> To unsubscribe send an email to cfrg-leave@irtf.org