A new Request for Comments is now available in online RFC libraries.
RFC 9867
Title: Mixing Preshared Keys in the
IKE_INTERMEDIATE and CREATE_CHILD_SA Exchanges of
the Internet Key Exchange Protocol Version 2 (IKEv2)
for Post-Quantum Security
Author: V. Smyslov
Status: Standards Track
Stream: IETF
Date: November 2025
Mailbox: [email protected]
Pages: 12
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ipsecme-ikev2-qr-alt-10.txt
URL: https://www.rfc-editor.org/info/rfc9867
DOI: 10.17487/RFC9867
An Internet Key Exchange Protocol Version 2 (IKEv2) extension defined
in RFC 8784 allows IPsec traffic to be protected against someone
storing VPN communications and decrypting them later, when (and if) a
Cryptographically Relevant Quantum Computer (CRQC) is available. The
protection is achieved by means of a Post-quantum Preshared Key (PPK)
that is mixed into the session keys calculation. However, this
protection does not cover an initial IKEv2 Security Association (SA),
which might be unacceptable in some scenarios. This specification
defines an alternative way to provide protection against quantum
computers, which is similar to the solution defined in RFC 8784, but
it also protects the initial IKEv2 SA.
RFC 8784 assumes that PPKs are static and thus they are only used
when an initial IKEv2 SA is created. If a fresh PPK is available
before the IKE SA expires, then the only way to use it is to delete
the current IKE SA and create a new one from scratch, which is
inefficient. This specification defines a way to use PPKs in active
IKEv2 SAs for creating additional IPsec SAs and rekey operations.
This document is a product of the IP Security Maintenance and Extensions
Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org
