[IPsec] RFC 9370 on Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2)

rfc-editor@rfc-editor.org Mon, 22 May 2023 20:30 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71F7BC15109D; Mon, 22 May 2023 13:30:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Level:
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9V-dgTt3bTa2; Mon, 22 May 2023 13:30:39 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77F4BC151090; Mon, 22 May 2023 13:30:39 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 5F7BE119F1; Mon, 22 May 2023 13:30:39 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ipsec@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230522203039.5F7BE119F1@rfcpa.amsl.com>
Date: Mon, 22 May 2023 13:30:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/RLCN9b35mNUiRSR_TlNEVHjI6_I>
Subject: [IPsec] RFC 9370 on Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 May 2023 20:30:43 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9370

        Title:      Multiple Key Exchanges in the 
                    Internet Key Exchange Protocol Version 2 (IKEv2) 
        Author:     CJ. Tjhai,
                    M. Tomlinson,
                    G. Bartlett,
                    S. Fluhrer,
                    D. Van Geest,
                    O. Garcia-Morchon,
                    V. Smyslov
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2023
        Mailbox:    cjt@post-quantum.com,
                    mt@post-quantum.com,
                    graham.ietf@gmail.com,
                    sfluhrer@cisco.com,
                    daniel.vangeest.ietf@gmail.com,
                    oscar.garcia-morchon@philips.com,
                    svan@elvis.ru
        Pages:      29
        Updates:    RFC 7296

        I-D Tag:    draft-ietf-ipsecme-ikev2-multiple-ke-12.txt

        URL:        https://www.rfc-editor.org/info/rfc9370

        DOI:        10.17487/RFC9370

This document describes how to extend the Internet Key Exchange
Protocol Version 2 (IKEv2) to allow multiple key exchanges to take
place while computing a shared secret during a Security Association
(SA) setup.

This document utilizes the IKE_INTERMEDIATE exchange, where multiple
key exchanges are performed when an IKE SA is being established.  It
also introduces a new IKEv2 exchange, IKE_FOLLOWUP_KE, which is used
for the same purpose when the IKE SA is being rekeyed or is creating
additional Child SAs.

This document updates RFC 7296 by renaming a Transform Type 4 from
"Diffie-Hellman Group (D-H)" to "Key Exchange Method (KE)" and
renaming a field in the Key Exchange Payload from "Diffie-Hellman
Group Num" to "Key Exchange Method".  It also renames an IANA
registry for this Transform Type from "Transform Type 4 - Diffie-
Hellman Group Transform IDs" to "Transform Type 4 - Key Exchange
Method Transform IDs".  These changes generalize key exchange
algorithms that can be used in IKEv2.

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 rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC