RFC 9827 on Renaming the Extended Sequence Numbers (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2)

rfc-editor@rfc-editor.org Wed, 05 November 2025 18:07 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 2509383BE088; Wed, 5 Nov 2025 10:07:39 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id DB042C000CCC; Wed, 5 Nov 2025 10:07:38 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9827 on Renaming the Extended Sequence Numbers (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2)
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20251105180738.DB042C000CCC@rfcpa.rfc-editor.org>
Date: Wed, 05 Nov 2025 10:07:38 -0800
Message-ID-Hash: IR5UFRXMFNAPEAL66E325WY6PFDFGDLQ
X-Message-ID-Hash: IR5UFRXMFNAPEAL66E325WY6PFDFGDLQ
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/TOop2MHJziB69HH0x3HtGXNTanc>
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 9827

        Title:      Renaming the Extended Sequence Numbers (ESN)
                    Transform Type in the Internet Key
                    Exchange Protocol Version 2 (IKEv2) 
        Author:     V. Smyslov
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2025
        Mailbox:    svan@elvis.ru
        Pages:      8
        Updates:    RFC 7296

        I-D Tag:    draft-ietf-ipsecme-ikev2-rename-esn-05.txt

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

        DOI:        10.17487/RFC9827

This document clarifies and extends the meaning of Transform Type 5
in Internet Key Exchange Protocol Version 2 (IKEv2). It updates RFC
7296 by renaming Transform Type 5 from "Extended Sequence Numbers
(ESN)" to "Sequence Numbers (SN)". It also renames two currently
defined values for this Transform Type: value 0 from "No Extended
Sequence Numbers" to "32-bit Sequential Numbers" and value 1 from
"Extended Sequence Numbers" to "Partially Transmitted 64-bit
Sequential Numbers".

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