Protocol Action: 'Renaming Extended Sequence Number (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2)' to Proposed Standard (draft-ietf-ipsecme-ikev2-rename-esn-04.txt)
The IESG <iesg-secretary@ietf.org> Thu, 06 February 2025 21:00 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from mail.ietf.org (ietfa.amsl.com [50.223.129.194]) (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 ietfa.amsl.com (Postfix) with ESMTPSA id 47687C2BD17E; Thu, 6 Feb 2025 13:00:33 -0800 (PST)
Received: from [10.244.8.212] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id A0032C2AC097; Thu, 6 Feb 2025 13:00:32 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'Renaming Extended Sequence Number (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2)' to Proposed Standard (draft-ietf-ipsecme-ikev2-rename-esn-04.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 12.35.0
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <173887563231.508.109234882005955258@dt-datatracker-75c44cbbdf-pxnd6>
Date: Thu, 06 Feb 2025 13:00:32 -0800
Message-ID-Hash: ZVXXAJDRNTLHCKB7AZN74NWY7KDA7KHY
X-Message-ID-Hash: ZVXXAJDRNTLHCKB7AZN74NWY7KDA7KHY
X-MailFrom: iesg-secretary@ietf.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: The IESG <iesg@ietf.org>, draft-ietf-ipsecme-ikev2-rename-esn@ietf.org, ipsec@ietf.org, ipsecme-chairs@ietf.org, kivinen@iki.fi, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/dLPjerDWHM-eRmVIMX2hsYHKWL8>
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>
The IESG has approved the following document: - 'Renaming Extended Sequence Number (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2)' (draft-ietf-ipsecme-ikev2-rename-esn-04.txt) as Proposed Standard This document is the product of the IP Security Maintenance and Extensions Working Group. The IESG contact persons are Paul Wouters and Deb Cooley. A URL of this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-ipsecme-ikev2-rename-esn/ Technical Summary This documents clarifies and extends the meaning of transform type 5 in IKEv2. It updates RFC 7296 by renaming the 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". Working Group Summary During the IETF last call of the g-ikev2 draft, there were comments about renaming IKEv2 IANA registries inside the large optional protocol. The renaming of the "Extended Sequence Numbers (ESN)" registry to "Sequence Numbers (SN)" would be better done in separate draft. There has been consensus in the WG to do this change. Document Quality As this does not change any bits on the wire, only names used in the IANA registries, all previous IPsec implementations work with this change. There might be minor user interface changes done by the implementations, and some of the implementations might want to rename their APIs or configuration files to match. Since this is just an IANA registry name change, no Yang modules are affected. Personnel The Document Shepherd for this document is Tero Kivinen. The Responsible Area Director is Deb Cooley. IANA Note (Insert IANA Note here or remove section)