Renaming Extended Sequence Number (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2)
draft-ietf-ipsecme-ikev2-rename-esn-05

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, debcooley1@gmail.com, draft-ietf-ipsecme-ikev2-rename-esn@ietf.org, ipsec@ietf.org, ipsecme-chairs@ietf.org, kivinen@iki.fi, rfc-editor@rfc-editor.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)

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/

Ballot Text

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)

RFC Editor Note