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

RE: IPCOMP and IPSEC

To: Stephen Waters <Stephen.Waters@digital.com>
Subject: RE: IPCOMP and IPSEC
From: Eric Dean <edean@gip.net>
Date: Sat, 30 May 1998 17:15:32 -0400 (EDT)
cc: Avram Shacham <shacham@cisco.com>, ipsec@tis.com, ippcp@external.cisco.com
In-Reply-To: <250F9C8DEB9ED011A14D08002BE4F64C01A23E5D@wade.reo.dec.com>
Sender: owner-ipsec@ex.tis.com

> 
> 	I've worked full-time from home for a few years now - using a
> direct dial ISDN link over which the 
> 	average compression seems to stay stubbornly on 2:1.  I'll load
> up the IPPCP image and share the results
> 	once I have a decent sample.  Not a bad case study considering
> the use of IPPCP in the short term -
> 	i.e. remote-access for laptops/SOHOs.
> 

For reasons stated in my previous message, as you move closer to the core 
of the Internet where traffic is highly uncorrelated, you will find 
relatively poor cases for stateful compression.  (I am aware that 
stateless compression is the proposed method for IPPCP.)

As you move far to the edge of the Internet, at the modem layer, you find 
that packets are highly correlated and tend to benefit from current stateful 
compression methodologies.

-eric

Prev by Date: RE: IPCOMP and IPSEC
Next by Date: Socket level have implemented interface for IPSEC????
Prev by thread: RE: IPCOMP and IPSEC
Next by thread: RE: IPCOMP and IPSEC
Index(es):
- Main
- Thread