RFC 9838 on Group Key Management Using the Internet Key Exchange Protocol Version 2 (IKEv2)
rfc-editor@rfc-editor.org Wed, 05 November 2025 21:34 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (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 AE9E783E7D8F; Wed, 5 Nov 2025 13:34:52 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 81D6AC000CCC; Wed, 5 Nov 2025 13:34:52 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9838 on Group Key Management Using the Internet Key Exchange Protocol Version 2 (IKEv2)
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20251105213452.81D6AC000CCC@rfcpa.rfc-editor.org>
Date: Wed, 05 Nov 2025 13:34:52 -0800
Message-ID-Hash: BSL32ZROBHFPYURKCRCE7BMKN5Z56IRT
X-Message-ID-Hash: BSL32ZROBHFPYURKCRCE7BMKN5Z56IRT
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ipsec@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/On2vZVEqc4UHthMburyKOXkmQ3U>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9838
Title: Group Key Management Using the
Internet Key Exchange Protocol Version 2 (IKEv2)
Author: V. Smyslov,
B. Weis
Status: Standards Track
Stream: IETF
Date: November 2025
Mailbox: svan@elvis.ru,
bew.stds@gmail.com
Pages: 66
Obsoletes: RFC 6407
I-D Tag: draft-ietf-ipsecme-g-ikev2-23.txt
URL: https://www.rfc-editor.org/info/rfc9838
DOI: 10.17487/RFC9838
This document presents an extension to the Internet Key Exchange
Protocol Version 2 (IKEv2) for the purpose of group key management.
The protocol is in conformance with the Multicast Security (MSEC)
Group Key Management architecture, which contains two components:
member registration and group rekeying. Both components are required
for a Group Controller/Key Server (GCKS) to provide authorized Group
Members (GMs) with IPsec Group Security Associations (GSAs). The GMs
then exchange IP multicast or other group traffic as IPsec packets.
This document obsoletes RFC 6407.
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