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

Re: (more#4 fwd from ipsec) Re: Handling of IPcomp in IKEv2

To: shacham@shacham.net
Subject: Re: (more#4 fwd from ipsec) Re: Handling of IPcomp in IKEv2
From: Paul Koning <pkoning@equallogic.com>
Date: Tue, 10 Dec 2002 14:10:50 -0500
Cc: mcr@sandelman.ottawa.on.ca, ipsec@lists.tislabs.com, ippcp@external.cisco.com
References: <200212100029.gBA0TRBx002980@sandelman.ottawa.on.ca><Pine.BSO.4.33.0212091652200.23209-100000@adsl-64-161-22-19.shacham.net>
Sender: owner-ipsec@lists.tislabs.com

>>>>> "Avram" == Avram Shacham <shacham@shacham.net> writes:

 Avram> As long as the generic case (i.e., negotiating a CPI) is also
 Avram> supported, all should be okay.

I think the whole point of the present proposal is that it eliminates
any purpose for negotiating a CPI.  I've read over your notes pretty
carefully but I haven't seen anything that refutes it.  If you
disagree, you might want to describe a (real world) usage scenario
that can't be supported by the proposal Charlie made.

     paul

Follow-Ups:
- Re: (more#4 fwd from ipsec) Re: Handling of IPcomp in IKEv2
  - From: Avram Shacham <shacham@shacham.net>

References:
- Re: (more#4 fwd from ipsec) Re: Handling of IPcomp in IKEv2
  - From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
- Re: (more#4 fwd from ipsec) Re: Handling of IPcomp in IKEv2
  - From: Avram Shacham <shacham@shacham.net>

Prev by Date: Re: Summary of revised identity changes
Next by Date: Re: Change of SA source IP address
Prev by thread: Re: (more#4 fwd from ipsec) Re: Handling of IPcomp in IKEv2
Next by thread: Re: (more#4 fwd from ipsec) Re: Handling of IPcomp in IKEv2
Index(es):
- Date
- Thread