Paul Wouters writes: > In addition, IANA has added this RFC as a reference to both the ESP > Reference and IKEv2 Reference columns for ENCR_AES_GCM entries, while > keeping the existing references there. Also, IANA has added this RFC > as a reference to the ESP Reference column for ENCR_CAMELLIA_CCM > entries, while keeping the existing reference there. > > The text describes doing the wrong thing, but implies this was > already done by IANA? But that might just be the writing style > (blame me) and we just told them to do the wrong thing.
The iana considerations sections are written based on the final result, i.e., where all the changes to the registries has already been done by IANA. For example RFC7296 IANA considerations says: IANA has updated all references to RFC 5996 to point to this document. etc... And the actual reason why the references for AES-GCM and CAMELLIA-CCM was added was because they were renamed: This document renames some of the names in the "Transform Type 1 - Encryption Algorithm Transform IDs" registry of the "Internet Key Exchange Version 2 (IKEv2) Parameters". All the other names have ENCR_ prefix except 3, and all other entries use names in the format of uppercase words separated with underscores except 6. This document changes those names to match others. I think we actually planned doing this just by asking IANA to modify the registry, but IANA requested that we should instead put it in some RFC so there will be history explaining the situation, thus we added IANA considerations to the RFC8247 to do the renaming. -- [email protected] _______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
