[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: Fri, 13 Dec 2002 12:32:42 -0500
Cc: henry@spsystems.net, ippcp@external.cisco.com, ipsec@lists.tislabs.com
References: <Pine.BSO.4.33.0212121037360.23252-100000@adsl-64-161-22-19.shacham.net><Pine.BSO.4.33.0212121055170.25348-100000@adsl-64-161-22-19.shacham.net>
Sender: owner-ipsec@lists.tislabs.com

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

 Avram> Even simpler is to keep existing IPComp implementations
 Avram> unchanged.

Not true.

That's valid if you leave IKE V1 in place.  IKEv2 is different code
(much simpler).  Trying to extract the gnarly IPcomp code within IKEv1
from the larger and even gnarlier IKEv1 body is a lot more work than
implementing the trivial mechanisms that Charlie & al. have proposed.

     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: Avram Shacham <shacham@shacham.net>

Prev by Date: RE: speaking of keys
Next by Date: Re: (more#4 fwd from ipsec) Re: Handling of IPcomp in IKEv2
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