[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: ISAKMP Oakley resolution and ipsec doi document questions

To: "'baiju@ideal.jf.intel.com'" <baiju@ideal.jf.intel.com>, "'ipsec@tis.com'" <ipsec@tis.com>, "'Edward A. Russell'" <erussell@ftp.com>
Subject: RE: ISAKMP Oakley resolution and ipsec doi document questions
From: Roy Pereira <rpereira@TimeStep.com>
Date: Mon, 16 Jun 1997 10:26:19 -0400
Sender: owner-ipsec@ex.tis.com

>>
>>2. in the doi document, who's port number is specified in
>>the identification payload? (initiator or reviver?)
>>The protocol ID and port are also in the field marked
>>reserved in the ISAKMP document. Is this intentional?
>>In my view, this should be consistent.
>
>The port is 500 for sending
>The port is 500 for receiving
>The port is 500 ONLY.
>I believe this came out of Memphis.

This change was due to some implementations only accepting ISAKMP
exchanges if both the source and destination ports were 500.  
>

Prev by Date: AH/ESP loose ends
Next by Date: RE: ISAKMP Oakley resolution and ipsec doi document questions
Prev by thread: Re: ISAKMP Oakley resolution and ipsec doi document questions
Next by thread: RE: ISAKMP Oakley resolution and ipsec doi document questions
Index(es):
- Main
- Thread