RFC 4891:Using IPsec to Secure IPv6-in-IPv4 Tunnel...
RFC-Ref

IKE


Click on the red underlined text to get to the source

... establishment. Section 5 gives the details of Internet Key Exchange (IKE) and IP security (IPsec) exchange with packet formats ...


... IKE and IPsec Versions ...
... This section discusses the different versions of the IKE and IPsec security architecture and their applicability to this document. ...
... RFC2401] and is now superseded by [RFC4301]. IKE was originally defined in [RFC2409] (which is called IKEv1 ...


... 2 IPV4-TEP1 IPV4-TEP2 IKE BYPASS 3 IPv4 ...
... 2 IPV4-TEP2 IPV4-TEP1 IKE BYPASS 3 IPv4 ...
... In both SPD entries, "IKE" refers to UDP destination port 500 ...


... NAT traversal mechanism provided by IKEv2 introduces some weaknesses into IKE and IPsec. These issues are discussed in more detail in [RFC4306 ...


... Harkins, D. and D. Carrel, "The Internet Key Exchange (IKE)", RFC 2409(-> 4306prop), November 1998. ...


... The SPDs must be interface-specific. However, because IKE uses IPv4 but the tunnel ...
... 2 IPV6-EP1 IPV6-EP2 IKE BYPASS 3 IPv6 ...
... 2 IPV6-EP2 IPV6-EP1 IKE BYPASS 3 IPv6 ...
... IPV4-TEP1}) "IKE" refers to UDP destination port 500 and possibly also ...
... 2 IPV6-EP1 IPV6-EP2 IKE BYPASS 3 IPV6 ...
... 2 IPV6-EP2 IPV6-EP1 IKE BYPASS 3 ANY IPV6 ...


... IP payloads in the initial IKE_SA_INIT exchange. Once a NAT is detected and both endpoints ...
... However, simply discovering the tunnel endpoint is not sufficient for establishing an IKE session with the peer. The PAD information (see ...



Google
Web
RFC-Ref