RE: IPCOMP and IPSEC
Paul Koning <pkoning@xedia.com> Fri, 05 June 1998 14:26 UTC
Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id KAA29829 for ipsec-outgoing; Fri, 5 Jun 1998 10:26:00 -0400 (EDT)
Date: Fri, 05 Jun 1998 10:39:51 -0400
Message-Id: <199806051439.KAA00557@tonga.xedia.com>
From: Paul Koning <pkoning@xedia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: shacham@cisco.com
Cc: rgm-sec@htt-consult.com, ipsec@tis.com, ippcp@external.cisco.com, Stephen.Waters@digital.com
Subject: RE: IPCOMP and IPSEC
References: <250F9C8DEB9ED011A14D08002BE4F64C01A23E5D@wade.reo.dec.com> <3.0.5.32.19980604120133.00a58c50@homebase.htt-consult.com> <3.0.2.32.19980604224547.006a18ec@airedale.cisco.com>
X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid
Sender: owner-ipsec@ex.tis.com
Precedence: bulk
>>>>> "Avram" == Avram Shacham <shacham@cisco.com> writes: Avram> At 12:01 PM 6/4/98 -0400, Robert Moskowitz wrote: >> TCPng needs to add intelligent compression (that is interact with >> the application). There is could have history. Avram> In previous discussions of compression at level 4, several Avram> people correctly pointed that TCP-compression may reduce the Avram> number of IP packets while IP compression can only reduce the Avram> size of each packet. Fewer IP packets may enhance performance Avram> even more than utilizing compression history. That's a very good point. Certainly sending the same number of bytes in a smaller number of packets is always a win. Avram> But - and this may be a BIG implementation obstacle - the Avram> current compression algorithms require ~16KB of compression Avram> and decompression context for _each_ connection. In other Avram> words, 16KB per socket... That's only a few millicents per socket. Avram> Also, UDP is still a useful L4 protocol and no stateful Avram> compression is possible here either. True, but for UDP packets that are larger than the MTU, the same IP packet reduction benefit applies.
- IPCOMP and IPSEC Stephen Waters
- Re: IPCOMP and IPSEC Daniel Harkins
- Re: IPCOMP and IPSEC Vach Kompella
- Re: IPCOMP and IPSEC Naganand Doraswamy
- RE: IPCOMP and IPSEC Roy Pereira
- Re: IPCOMP and IPSEC Daniel Harkins
- FW: IPCOMP and IPSEC Stephen Waters
- RE: IPCOMP and IPSEC Roy Pereira
- Re: IPCOMP and IPSEC Daniel Harkins
- RE: IPCOMP and IPSEC Roy Pereira
- Re: IPCOMP and IPSEC Marc Hasson
- Re: IPCOMP and IPSEC Daniel Harkins
- Re: IPCOMP and IPSEC Marc Hasson
- Re: IPCOMP and IPSEC Saroop Mathur
- RE: IPCOMP and IPSEC Stephen Waters
- Re: IPCOMP and IPSEC Eric Dean
- RE: IPCOMP and IPSEC Avram Shacham
- RE: IPCOMP and IPSEC Avram Shacham
- RE: IPCOMP and IPSEC Eric Dean
- RE: IPCOMP and IPSEC Stephen Waters
- RE: IPCOMP and IPSEC Eric Dean
- RE: IPCOMP and IPSEC Eric Dean
- Re: IPCOMP and IPSEC Stephen Kent
- RE: IPCOMP and IPSEC Robert Moskowitz
- RE: IPCOMP and IPSEC Avram Shacham
- RE: IPCOMP and IPSEC Paul Koning