[CFRG] Re: [saag] Re: [MSEC]Fwd: New Liaison Statement, "LS on PQC transition for RFC 6509"

Watson Ladd <watsonbladd@gmail.com> Mon, 17 November 2025 19:00 UTC

Return-Path: <watsonbladd@gmail.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 4A1658B2A8C8 for <cfrg@mail2.ietf.org>; Mon, 17 Nov 2025 11:00:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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=gmail.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 FMAisr0WUR3C for <cfrg@mail2.ietf.org>; Mon, 17 Nov 2025 11:00:56 -0800 (PST)
Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 402F38B2A835 for <cfrg@irtf.org>; Mon, 17 Nov 2025 11:00:41 -0800 (PST)
Received: by mail-wm1-x32a.google.com with SMTP id 5b1f17b1804b1-4779cc419b2so22611255e9.3 for <cfrg@irtf.org>; Mon, 17 Nov 2025 11:00:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1763406040; x=1764010840; darn=irtf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=YQUgtXbvHjTFPkzpaM1nhD0abeE6gjEwQvcuLfLzE+c=; b=UX2RM6eyKhIFCUIYMstk3d+ZKsne/0/YX6uNM3Gh8kXct4g4KD8gpsZER27ngCJkpG mp3Zkcc0iBXyvXUN7g+rlIcyyyj7BN6BTEhfyD/4vABZvnwJfGuk/+wcpagSHUuMs9bB YWxNdN/yF63xS8WejNkxEqU2A4JEdOmzJNxTJ7APRRDFz7MeGCu2nCAWtA77d+cjTdsD +MzgzGWOK1gzZfXqSbD49aapdzaHtyd5L4CyZgoh1PheQqNbZVGgrJhFkXMGdM668pSP 5ek+DvBDPfqvdBvWksrjewo/hCZIFvqxyyRNVjT4K6iuhtFdWG+v0lcwVa0yjzOHfjJY fiYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763406040; x=1764010840; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=YQUgtXbvHjTFPkzpaM1nhD0abeE6gjEwQvcuLfLzE+c=; b=g8UHmX4aDFN7npx3NNZdPODH3V1sXCM+ZkiiNe9lfcn5gTZlCAMseNoUwg+DBbhej4 HHqhdSaCRk4oPzh5VztGkVg1UgRyjuJbooAUa1/r99/P7sC8iFMuQksLTaHoGYIvxFe1 9pHB98AL9y60gDINF+DpTE1hK+1dXHm9M69P2poecfBP8gCwXH3g936i8yjjh4g+/4vp pqXtHbetizxhsnO7pIfRU5332/J+EGgyD8QvFxDC6mMANYbuZO4yl0/5Yjpieiui7G18 nl2x7nS93EkbA7L9V7iPqnKynNJwJ7Z5/Tzf1tSN6+vT/8SR7mXWWPO4vgXJ3OElxq+L 8EyA==
X-Forwarded-Encrypted: i=1; AJvYcCXQRtbQQnP5ylAE4obbzeVKAmE6g7Y/m/IoP0q992XO0w2sXQXpqgL9vrJSV6wJzUJSuGqS@irtf.org
X-Gm-Message-State: AOJu0Yx3QdRG+RE8tQypaNLSHrUoUIWnnnOYTjqtwN+7nimVcFWeer6X ZjDrozcA8UINnpHRxfQHxGi62Razh+Iy8bUT4l6nfg59z5ekhMFYUah1Gz+01kUvdl24vLhnUPX 0CD7FFoij5T/g4mT4Vr5pFPRz1b+co+Y=
X-Gm-Gg: ASbGncv2qOSwPdF+3HDPLPe1qIpuyQYInbhqg/ucxjjOfgmYKExAtT82lrdbd3+ghVE W0GFssOa8jaR5ze1lUvK2tx+ObkM1EjFkM5AZTKJYxIjolNIJX8gu0yJ6HD+t+0Qd42n11fSyV6 p8r53AorjV51VAzz9aDIFCwhi12tkqA6BZYbQCf2UEV1V3Ylw6t5tCP+QpjZXgrFRjE8BOsFd6k OZM8iLorYnZIuzcuowBYRQOQR19NpeYQ7Xuix2JVvkkptgBSVMnHjARlR9G0ZHDaZv4oySwLyZQ yk4Do+bEDsute/xhi4QU7huog5/WA7LnsvOC85FlI+jPVzOenwWh5tKCcn6L/sSEHUWj
X-Google-Smtp-Source: AGHT+IG2u3c2e/Qpjb1HpnzvgUNdiJrk/NGph4NbHHNHV1quKbj9Yn72SPXlfj/NJRRD83GGedxTxBdaqCgyo0qWR5c=
X-Received: by 2002:a05:600c:1910:b0:477:9e10:3e63 with SMTP id 5b1f17b1804b1-4779e103efamr58436695e9.35.1763406040122; Mon, 17 Nov 2025 11:00:40 -0800 (PST)
MIME-Version: 1.0
References: <176202487075.596.3319569057232958293@dt-datatracker-5df8666cb-7l4w5> <CAGgd1OctMg6=sB8vMPOXOpnP1DgbpvW97u963QGdsbJLJDYnkw@mail.gmail.com> <GVXPR07MB967811BEA156C0FCEC05DACD89CCA@GVXPR07MB9678.eurprd07.prod.outlook.com> <E2E757F9-B545-4A6A-84CA-19696B1E8617@vigilsec.com> <CAOjisRwFCO3nX9B7xLOHaFUfF7dEqpNZdVEp-64+9-C0qrm2ag@mail.gmail.com> <GVXPR07MB96783211A9B905B20AD9DF0D89CCA@GVXPR07MB9678.eurprd07.prod.outlook.com> <CACsn0cnYJhc9j6hnUdKLS3gwgBeTaSDGENGbm41HE4LgM_FfeA@mail.gmail.com> <cf7d2ac5a41f475d99b9f7f099652117@huawei.com>
In-Reply-To: <cf7d2ac5a41f475d99b9f7f099652117@huawei.com>
From: Watson Ladd <watsonbladd@gmail.com>
Date: Mon, 17 Nov 2025 11:00:28 -0800
X-Gm-Features: AWmQ_bkQiARTpXsHw9vqvgyGLY0YJjmiXkWg4P3PvSGbCJd78uMq1v7TpyEHaXE
Message-ID: <CACsn0cm8ZsCN5zgobJWBh8Xmru+L=Lyic9p8LpAn8zcAZY=T2g@mail.gmail.com>
To: "Liuchunchi(Peter)" <liuchunchi@huawei.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: QHNWTZCMWQGVDWG3YW4RFKLIREC64MIF
X-Message-ID-Hash: QHNWTZCMWQGVDWG3YW4RFKLIREC64MIF
X-MailFrom: watsonbladd@gmail.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: John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org>, Nick Sullivan <nicholas.sullivan@gmail.com>, IETF SAAG <saag@ietf.org>, IRTF CFRG <cfrg@irtf.org>, "msec@ietf.org" <msec@ietf.org>, "cfrg-chairs@ietf.org" <cfrg-chairs@ietf.org>, Charles Eckel <eckelcu@cisco.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [CFRG] Re: [saag] Re: [MSEC]Fwd: New Liaison Statement, "LS on PQC transition for RFC 6509"
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/GTmeNGXEQzbReuxnF-VEg_yR4VE>
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>

On Mon, Nov 17, 2025 at 12:36 AM Liuchunchi(Peter)
<liuchunchi@huawei.com> wrote:
>
> The cryptography of proof systems you need to do the zkps is very active thanks to cryptocurrency so plenty of options.
>
>
>
> Any pointers?

For instance we have https://eprint.iacr.org/2025/1187 which gets used
in https://eprint.iacr.org/2024/2010
>
>
>
> I think if would be good if CFRG started discussing quantum-resistant replacements for pairing-based cryptography. In addition to IBE and ABE, there is a lot of interest in zero-knowledge proofs and anonymous credentials with selective disclosure.
>
>
>
> Compared to their non-quantum-resistant properties, the more criticized aspects of IBE and ABE are that the master key being able to see everything. So a more general (and hopefully efficient) post quantum construction for zkps would be very attractive, permitting way more applications than IBE/ABE, and I do think such discussion in CFRG would be good and useful.
>
>
>
> Peter
>
>
>
> From: Watson Ladd <watsonbladd@gmail.com>
> Sent: Thursday, November 13, 2025 4:04 AM
> To: John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org>
> Cc: Nick Sullivan <nicholas.sullivan@gmail.com>; IETF SAAG <saag@ietf.org>; IRTF CFRG <cfrg@irtf.org>; msec@ietf.org; cfrg-chairs@ietf.org; Charles Eckel <eckelcu@cisco.com>
> Subject: [saag] Re: [CFRG] [MSEC]Fwd: New Liaison Statement, "LS on PQC transition for RFC 6509"
>
>
>
> The cryptography of proof systems you need to do the zkps is very active thanks to cryptocurrency so plenty of options. I don't think that was the deployment barrier. That conversation is happening to some extent in privacy pass.
>
>
>
> On Wed, Nov 12, 2025, 11:59 AM John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org> wrote:
>
> I think if would be good if CFRG started discussing quantum-resistant replacements for pairing-based cryptography. In addition to IBE and ABE, there is a lot of interest in zero-knowledge proofs and anonymous credentials with selective disclosure. I would be sceptical to deploy pairing-based crypto at the moment as long as it is uncertain if there will be PQC replacements before 2035 when most organisations will try to phase out all quantum-vulnerable crypto.
>
>
>
> John
>
>
>
> From: Nick Sullivan <nicholas.sullivan@gmail.com>
> Date: Wednesday, 12 November 2025 at 20:53
> To: Russ Housley <housley@vigilsec.com>
> Cc: John Mattsson <john.mattsson@ericsson.com>, Deb Cooley <debcooley1@gmail.com>, IETF SAAG <saag@ietf.org>, IRTF CFRG <cfrg@irtf.org>, msec@ietf.org <msec@ietf.org>, cfrg-chairs@ietf.org <cfrg-chairs@ietf.org>, Paul Wouters <paul.wouters@aiven.io>, Charles Eckel <eckelcu@cisco.com>
> Subject: Re: [CFRG] [MSEC]Fwd: New Liaison Statement, "LS on PQC transition for RFC 6509"
>
> My understanding is that there are a few preliminary options for PQC IBE systems, including this one (https://indico.math.cnrs.fr/event/11948/attachments/5546/9653/5_Julien_Cam.pdf) based on ML-KEM, but they are much less mature than the pairing-based systems.
>
>
>
> I would even consider the non-PQC pairing crypto we do have as experimental/new/risky. It’s not yet widely deployed in IETF protocols, and the CFRG is still working on a document to specify safe parameters (https://www.ietf.org/archive/id/draft-irtf-cfrg-pairing-friendly-curves-10.html)
>
>
>
> If someone in the CFRG wants to tackle the problem of specifying a PQC IBE system, I don’t see it as out of scope for the group. There would be some leg work and support needed by implementers to specify something, but even with that, it’s not clear there’s consensus even in academia about what the right approach is. I would consider it too early for the CFRG to make a considered recommendation today.
>
>
>
> Nick
>
>
>
> On Wed, Nov 12, 2025 at 2:31 PM Russ Housley <housley@vigilsec.com> wrote:
>
> I am unaware of any IBE PQC algorithms.  Is this something that CFRG is willing to work on?  Even if they are, I doubt we could give 3GPP a firm completion date.
>
>
>
> Russ
>
>
>
> On Nov 12, 2025, at 1:51 PM, John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org> wrote:
>
>
>
> Hi Deb,
>
>
>
> Yes, MIKEY (RFC 3830) was updated by three AD sponsored RFCs: MIKEY-TICKET (RFC 6043), MIKEY-IBAKE (RFC 6267), and MIKEY-SAKKE (RFC 6509). My reading of the LS is that 3GPP specifically asked for MIKEY-SAKKE (RFC 6509) which is an optional application layer for use by governments in mission critical 3GPP systems, but to my understanding, it is not widely deployed. RFC 6507 (ECCSI)) and RFC 6508 (SAKKE) are not formally related to MIKEY but are used in RFC 6509 (MIKEY-SAKKE).
>
>
>
> While 3GPP specifications also refer to RFC 3830 and RFC 6043, 3GPP only use symmetric algorithms/modes, which are already quantum-resistant.
>
>
>
> (MIKEY-)SAKKE is not using P-256, it uses pairing-based cryptography (E(F_p) x E(F_p) -> F_p^2, where p is a 1024 bit prime, and was not affected by SexTNSF.) Making the identity-based MIKEY-SAKKE quantum-resistant likely involves using not yet standardized lattice-based cryptography and is at least not easy. Any updates should likely be done in corporation with the governments interested in using them. MIKEY-SAKKE was authored by UK NCSC.
>
>
>
> For the non-identity-based parts of MIKEY, the symmetric parts are already quantum-resistant, and best current practice according to RFC 8862 is to mandate support of DTLS-SRTP, which is already being migrated to PQC by TLS WG.
>
>
>
> Cheers,
>
> John
>
>
>
> From: Deb Cooley <debcooley1@gmail.com>
> Date: Wednesday, 12 November 2025 at 14:52
> To: IETF SAAG <saag@ietf.org>, cfrg@irtf.org <cfrg@irtf.org>, msec@ietf.org <msec@ietf.org>
> Cc: cfrg-chairs@ietf.org <cfrg-chairs@ietf.org>, Charles Eckel (eckelcu) <eckelcu=40cisco.com@dmarc.ietf.org>, Paul Wouters <paul.wouters@aiven.io>
> Subject: [MSEC]Fwd: New Liaison Statement, "LS on PQC transition for RFC 6509"
>
> SAAG, CFRG and MSEC,
>
>
>
> The Sec ADs received the enclosed liaison request from 3GPP.  The subject is the PQ transition timeline for MIKEY-SAKKE (MIKEY was originally specified in RFC 3830, then updated and expanded in RFCs 6507, 6508, 6509) and whether the IETF plans to update this protocol to be PQ secure.
>
>
>
> From a quick skim of the RFCs (where the later RFCs are Informational and were AD sponsored), it appears that the basis of this protocol/algorithm is ECC P256/SHA-256 with a certificate-less Identity Based public key system.
>
>
>
> If there is anyone who is planning to do the update work, please speak up now.  [I'm not making any comments on how easy/hard this work might be.]
>
>
>
> Otherwise, we (IETF) will go back to 3GPP stating that we do not plan to update this protocol.
>
>
>
> Thanks,
>
>
>
> Deb Cooley
>
> Security Area Director
>
>
>
> ---------- Forwarded message ---------
> From: Liaison Statement Management Tool <statements@ietf.org>
> Date: Sat, Nov 1, 2025 at 3:21 PM
> Subject: New Liaison Statement, "LS on PQC transition for RFC 6509"
> To: Deb Cooley <debcooley1@gmail.com>, Paul Wouters <paul.wouters@aiven.io>
> Cc: Charles Eckel <eckelcu@cisco.com>, Deb Cooley <debcooley1@gmail.com>, Paul Wouters <paul.wouters@aiven.io>, The IETF Chair <chair@ietf.org>, <liaison-coordination@iab.org>
>
>
>
> Title: LS on PQC transition for RFC 6509
> Submission Date: 2025-10-30
> URL of the IETF Web page: https://datatracker.ietf.org/liaison/2070/
>
> To: Security Area (sec)
> From: 3GPP TSG SA WG3
> Purpose: For action
> Please reply by 2025-11-14
>
> Email Addresses
> ---------------
> From: Zander Lei <lei.zhongding@huawei.com>
> To: Paul Wouters <paul.wouters@aiven.io>,Deb Cooley <debcooley1@gmail.com>
> Cc: Deb Cooley <debcooley1@gmail.com>,Charles Eckel <eckelcu@cisco.com>,The IETF Chair <chair@ietf.org>,Paul Wouters <paul.wouters@aiven.io>
> Response Contacts: 3GPP Liaisons Coordinator <3GPPLiaison@etsi.org>
> Peter Schmitt <Peter.Schmitt@huawei.com>
> Technical Contacts:
>
>
> Body: 1 Overall description
>
> 3GPP SA3 has started a study on “Transitioning to Post Quantum Cryptography (PQC) in 3GPP”. This is to prepare the PQC transition for security protocols used in 3GPP systems. 3GPP SA3 has identified that the MIKEY-SAKKE protocol, which is used in 3GPP systems to transport cryptographic keys securely for Mission Critical Services, is specified in the IETF RFC 6509. Since it employs asymmetric cryptography for key distribution and may be vulnerable to quantum computing, SA3 would like to know whether there is any plan for IETF to update the RFC 6509 using PQC. If yes, SA3 appreciate if IETF can provide estimated timeline for the protocol update.
>
> 2       Actions
> To IETF SEC Area
> ACTION:         SA3 kindly request IETF to provide feedback on the question above.
>
> 3       Dates of next TSG SA WG 3 meetings
> SA3#125 17 – 21 November 2025           Dallas, US
> SA3#126 9 – 13 February 2026            India (TBD)
> Attachments:
>
>     LS on PQC transition for RFC 6509
>     https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2025-10-30-3gpp-tsg-sa-wg3-sec-ls-on-pqc-transition-for-rfc-6509-attachment-1.docx
>
> _______________________________________________
> CFRG mailing list -- cfrg@irtf.org
> To unsubscribe send an email to cfrg-leave@irtf.org
>
>
>
> _______________________________________________
> saag mailing list -- saag@ietf.org
> To unsubscribe send an email to saag-leave@ietf.org



-- 
Astra mortemque praestare gradatim