Re: [IPsec] IANA port number assignment name for IKEv2

2010-10-13 Thread Alfred Hönes
On Sun, 10 Oct 2010 17:15:22 -0400, Micah Anderson wrote: On Sat, 9 Oct 2010 15:00:49 -0400, Dan McDonald wrote: ... Here are the entries in Solaris's /etc/services, e.g.: ike 500/udp ike # Internet Key Exchange ipsec-nat-t 4500/udp

Re: [IPsec] IANA port number assignment name for IKEv2

2010-10-10 Thread micah anderson
On Sat, 9 Oct 2010 15:00:49 -0400, Dan McDonald dan.mcdon...@oracle.com wrote: On Sat, Oct 09, 2010 at 12:56:04PM -0400, micah anderson wrote: SNIP! RFC2409 has been obsoleted by 4306 which was then obsoleted by 5996. My understanding of obsoleted rfcs means that what they contain is no

Re: [IPsec] IANA port number assignment name for IKEv2

2010-10-09 Thread micah anderson
Hello, On Fri, 8 Oct 2010 16:19:21 -0700 (PDT), Dan Harkins dhark...@lounge.org wrote: I'm not sure what non-backwards compatibility issue there is because the IKEv2 header is, intentionally, the same as the ISAKMP header. The former has MajVer as 2 and the latter has MajVer as 1. It's

Re: [IPsec] IANA port number assignment name for IKEv2

2010-10-09 Thread Dan McDonald
On Sat, Oct 09, 2010 at 12:56:04PM -0400, micah anderson wrote: SNIP! RFC2409 has been obsoleted by 4306 which was then obsoleted by 5996. My understanding of obsoleted rfcs means that what they contain is no longer valid. RFC 2409 used port 500 for ISAKMP, but RFC 5996 has overtaken that

Re: [IPsec] IANA port number assignment name for IKEv2

2010-10-08 Thread Dan Harkins
Hi, I'm not sure what non-backwards compatibility issue there is because the IKEv2 header is, intentionally, the same as the ISAKMP header. The former has MajVer as 2 and the latter has MajVer as 1. It's possible to demultiplex a packet unambiguously. I don't know what problem would be