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

Re: issues from the bakeoff

To: Dan Harkins <dharkins@network-alchemy.com>
Subject: Re: issues from the bakeoff
From: Anupama Potluri <anupama@trinc.com>
Date: Tue, 22 Jun 1999 11:19:39 +0530 (IST)
cc: ipsec@lists.tislabs.com
In-Reply-To: <199906151954.MAA21779@potassium.network-alchemy.com>
Sender: owner-ipsec@lists.tislabs.com


Hi,

While reading the ISAKMP RFC once again, I discovered that it is not
transform numbers alone but even the proposal numbers that can be changed
from what the initiator has sent. Is this being done by any
implementation? Do we need to support the change in the proposal number?
Combining this with the fact that some implementations change the order of
proposal payloads in the returned proposal, the checking of the proposal
against what the initiator sent can be extremely complex! Cant we mandate
that the proposal number MUST be the same as what the initiator sent
atleast?

thanks,
Anupama

References:

issues from the bakeoff

From: Dan Harkins <dharkins@network-alchemy.com>

Prev by Date: Re: draft-ietf-ipsec-notifymsg-00.txt
Next by Date: Re: draft-ietf-ipsec-notifymsg-00.txt
Prev by thread: Re: issues from the bakeoff
Next by thread: RE: issues from the bakeoff
Index(es):
- Main
- Thread