Hi, draft-ietf-ipsecme-ikev2-rename-esn-04 is in the RFC Editor queue now. It has already passed IANA review and the IANA actions listed in the draft were confirmed by the author (me).
However, in the process of IANA review of the G-IKEv2 draft, it came to light that some needed IANA actions were missing from draft-ietf-ipsecme-ikev2-rename-esn-04. The G-IKEv2 draft allocates a new value for the renamed "Sequence Numbers" transform, but it appears that all possible values apart from the two already allocated for this transform are marked as "Reserved" and cannot be used: https://www.iana.org/assignments/ikev2-parameters/ikev2-parameters.xhtml#ike v2-parameters-9 This registry is different from all other IKEv2 registries - it was created in such a way, that no new values can be allocated. The most probable reason for such a decision was that this transform type was originally intended to only indicate whether ESN was on or off, so no other values made sense, thus they were disabled to be allocated. Since the purpose of draft-ietf-ipsecme-ikev2-rename-esn is to use this transform type for more flexible control of the sequence numbers behavior, we do want to be able to allocate more values for it (like the G-IKEv2 draft does). To allow this, the "Reserved" range of values for this registry should have been re-classified to "Unassigned" and "Private Use" ranges by draft-ietf-ipsecme-ikev2-rename-esn draft. That didn't happen due to overlook from my side (as the author and one of the designated experts). This was also not noticed by reviewers. The proposed solution, as it was discussed with the chairs (one of which is the other designated expert for this registry) and with the responsible AD, is to request the RFC Editor to made the following changes in draft-ietf-ipsecme-ikev2-rename-esn-04: 1. In the Section 5, after the item: * The "Transform Type 5 - Extended Sequence Numbers Transform IDs" registry is renamed to "Transform Type 5 - Sequence Numbers Transform IDs". add a new item: * The "Reserved" range of numbers in the "Transform Type 5 - Sequence Numbers Transform IDs" registry is split into the "Unassigned" (2-1023) and the "Private Use" (1024-65535) ranges, each referencing [RFCXXXX]. 2. Add the following para at the end of Section 5: Numbers in the range 2-65635 were originally marked as "Reserved" referencing [RFC7296], and were re-classified as "Unassigned" and "Private Use" by [RFCXXXX]. These changes would allow the IANA to make new allocations for this registry, thus the mission of the draft-ietf-ipsecme-ikev2-rename-esn draft would be complete. Since formally these are technical changes to the document that has already passed all last calls and is in the RFC Editor queue, Tero and Deb asked me to inform the WG about the proposed changes. If anybody disagree with the proposed changes, please chime in. In this case another WGLC will have be needed. Regards, Valery. _______________________________________________ IPsec mailing list -- ipsec@ietf.org To unsubscribe send an email to ipsec-le...@ietf.org
