RFC 9838: Group Key Management Using the Internet Key Exchange Protocol Version 2 (IKEv2)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9838
- Published
- November 2025
- Authors
- V. Smyslov; B. Weis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 66
- Also known as
- —
- Obsoletes:
- RFC 6407
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3547 (2003)
- RFC 6407 (2011)
- RFC 9838 (2025)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9846The Transport Layer Security (TLS) Protocol Version 1.3Current
July 2026
- RFC 9847IANA Registry Updates for TLS and DTLSCurrent
December 2025
- RFC 9848Bootstrapping TLS Encrypted ClientHello with DNS Service BindingsCurrent
March 2026
- RFC 9827Renaming the Extended Sequence Numbers (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2)Current
November 2025
- RFC 9849TLS Encrypted Client HelloCurrent
March 2026
- RFC 9850The SSLKEYLOGFILE Format for TLSCurrent
July 2026
- RFC 9851TLS 1.2 is in Feature FreezeCurrent
July 2026
- RFC 9852New Protocols Using TLS Must Require TLS 1.3Current
July 2026
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?