[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Initial Contact Message in IKE
This is from RFC2407:
4.6.3.3 INITIAL-CONTACT
The INITIAL-CONTACT status message may be used when one side wishes
to inform the other that this is the first SA being established with
the remote system. The receiver of this Notification Message might
then elect to delete any existing SA's it has for the sending system
under the assumption that the sending system has rebooted and no
longer has access to the original SA's and their associated keying
material. When used, the content of the Notification Data field
SHOULD be null (i.e. the Payload Length should be set to the fixed
length of Notification Payload).
When present, the Notification Payload MUST have the following
format:
o Payload Length - set to length of payload + size of data (0)
o DOI - set to IPSEC DOI (1)
o Protocol ID - set to selected Protocol ID from chosen SA
o SPI Size - set to sixteen (16) (two eight-octet ISAKMP cookies)
o Notify Message Type - set to INITIAL-CONTACT
o SPI - set to the two ISAKMP cookies
o Notification Data - <not included>
Is this not enough information?
-g
> -----Original Message-----
> From: owner-ipsec@lists.tislabs.com
> [mailto:owner-ipsec@lists.tislabs.com]On Behalf Of Rajesh Bhattacharya
> Sent: Monday, October 01, 2001 12:37 AM
> To: ipsec@lists.tislabs.com
> Subject: Initial Contact Message in IKE
>
>
> Hi Guys,
>
> Any pointer on ike's initial contact message?
> IKE or related rfcs don't give enough detail on that.
>
> Regards,
> Rajesh.
> --
> Rajesh Bhattacharya <rajub@intotoinc.com>
>
> Yesterday is not ours to recover,
> But today is ours to win or lose.
> So let's not waste today!!
>
References: