[Gen-art] draft-ietf-ipsecme-ikev2-pqc-auth-09 ietf last call Genart review

Gyan Mishra via Datatracker <noreply@ietf.org> Mon, 20 July 2026 00:40 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@mail2.ietf.org
Received: from [10.244.22.187] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 082EE119E41D3; Sun, 19 Jul 2026 17:40:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784508037; bh=mhVBC8s5CXzu9s29KLpptclIMw1ZmJMHFb+nsGGFdE8=; h=From:To:Cc:Subject:Reply-To:Date; b=vQJM3oUhWar3L3l67tdZWfKhgIvPozLfgeNpXBd0B78rNiKj8nZbidkPAWZcQJOpZ 66VCYYoCVndPb1NbWk2Y8RBZ5pFhWloxa3M1lLxyk23LdUuwrjw8its6DGp3Iw4HwB IuBiSSbh6KsU34Q6Ty2jbufvwv2nAgTQFlfuff8k=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Gyan Mishra via Datatracker <noreply@ietf.org>
To: gen-art@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.69.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178450803692.624.3889064403817965998@dt-datatracker-d4d6ff9d9-ql5mb>
Date: Sun, 19 Jul 2026 17:40:36 -0700
Message-ID-Hash: YDXFOQUMRFS7RIW2574E4LGAZ5VKLVOB
X-Message-ID-Hash: YDXFOQUMRFS7RIW2574E4LGAZ5VKLVOB
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-gen-art.ietf.org-0; header-match-gen-art.ietf.org-1; header-match-gen-art.ietf.org-2; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-ipsecme-ikev2-pqc-auth.all@ietf.org, ipsec@ietf.org, last-call@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Gyan Mishra <hayabusagsm@gmail.com>
Subject: [Gen-art] draft-ietf-ipsecme-ikev2-pqc-auth-09 ietf last call Genart review
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/IkSyrt0RcYgKjADhNTtf38VGs_o>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Owner: <mailto:gen-art-owner@ietf.org>
List-Post: <mailto:gen-art@ietf.org>
List-Subscribe: <mailto:gen-art-join@ietf.org>
List-Unsubscribe: <mailto:gen-art-leave@ietf.org>

Document: draft-ietf-ipsecme-ikev2-pqc-auth
Title: Signature Authentication in the Internet Key Exchange Version 2 (IKEv2)
using PQC Reviewer: Gyan Mishra Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-ipsecme-ikev2-pqc-auth-??
Reviewer: Gyan Mishra
Review Date: 2026-07-19
IETF LC End Date: 2026-07-31
IESG Telechat date: Not scheduled for a telechat

Summary:

Signature-based authentication methods are utilized in the Internet Key
Exchange Version 2 (IKEv2). The current version of the IKEv2 protocol,
specified in RFC 7296, supports traditional digital signatures.

This document specifies a generic mechanism for integrating post-quantum
cryptographic (PQC) digital signature algorithms into the IKEv2 protocol. The
approach allows for seamless inclusion of any PQC signature scheme within the
existing authentication framework of IKEv2. Additionally, it outlines how
Module-Lattice-Based Digital Signatures (ML-DSA) and Stateless Hash-Based
Digital Signatures (SLH-DSA), can be employed as authentication methods within
the IKEv2 protocol, as they have been standardized by US NIST.

I believe this specification is almost ready for publication.

One question I would like to ask the authors is related to any IANA code points
for the use of PQC for signature for IKEv2.

As this is standards track and a significant change to IKEv2 which does impact
all IPSEC implementations vendors supporting the PQM update feature.

To ensure standardization and forward and backward compatibility in the
implementation should there be a standard codepoint allocated for the drafts
update to IKEv2 for PQM signature signing.

What is the impact on SA security association rekeying during key update
intervals.  I do not see anything mentioned related but as we are using a new
PQM signing mechanism, I wonder if there is any impact and if so it should be
added to the considerations section.

Major issues:
None

Minor issues:
None

Nits/editorial comments:
None