Hi,
RFC 4543 specifies how to use AES-GMAC mode in AH and ESP and how to
negotiate them in IKEv1 and IKEv2 (see Section 5, 1st paragraph).
However, as Soo-Fei Chew pointed out, the IANA considerations text in
the final document didn't actually ask IANA to assign the numbers for
IKEv1.
Here's my
pasi.ero...@nokia.com writes:
> (1) ask IANA to assign the four missing numbers (after IESG approval).
> (2) submit an RFC Editor errata, saying something like this:
> (3) ask IANA to include a pointer to this errata in the isakmp-registry
> entries.
>
> Does this sound like a reasonable plan?
I
pasi.ero...@nokia.com writes:
> RFC 4543 specifies how to use AES-GMAC mode in AH and ESP and how to
> negotiate them in IKEv1 and IKEv2 (see Section 5, 1st paragraph).
>
> However, as Soo-Fei Chew pointed out, the IANA considerations text in
> the final document didn't actually ask IANA to assign
; To: Eronen Pasi (Nokia-NRC/Helsinki)
> Cc: ipsec@ietf.org
> Subject: [IPsec] Transform IDs for AES-GMAC in IKEv1
>
> pasi.ero...@nokia.com writes:
> > RFC 4543 specifies how to use AES-GMAC mode in AH and ESP and how to
> > negotiate them in IKEv1 and IKEv2 (see Section 5,
with the details!)
Best regards,
Pasi
> -Original Message-
> From: ipsec-boun...@ietf.org [mailto:ipsec-boun...@ietf.org] On Behalf
> Of Eronen Pasi (Nokia-NRC/Helsinki)
> Sent: 30 April, 2009 12:28
> To: ipsec@ietf.org
> Subject: [IPsec] Transform IDs for AES-GMAC in I
