RE: IPCOMP and IPSEC

Stephen Waters <Stephen.Waters@digital.com> Sat, 30 May 1998 09:46 UTC

Return-Path: Stephen.Waters@digital.com
Received: from beasley.cisco.com (mailgate-sj-2.cisco.com [171.69.2.135]) by ftp-eng.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id CAA05433 for <ippcp-archive-file@ftp-eng.cisco.com>; Sat, 30 May 1998 02:46:00 -0700 (PDT)
Received: from proxy3.cisco.com (proxy3.cisco.com [192.31.7.90]) by beasley.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id CAA19466 for <ippcp@external.cisco.com>; Sat, 30 May 1998 02:45:38 -0700 (PDT)
Received: (from smap@localhost) by proxy3.cisco.com (8.8.7/8.8.5) id CAA10625 for <ippcp@external.cisco.com>; Sat, 30 May 1998 02:45:38 -0700 (PDT)
Received: from mail11.digital.com(192.208.46.10) by proxy3.cisco.com via smap (V2.0) id xmaa10543; Sat, 30 May 98 09:45:37 GMT
X-SMAP-Received-From: outside
Received: from reohub2.reo.dec.com (reohub2.reo.dec.com [16.37.21.19]) by mail11.digital.com (8.8.8/8.8.8/WV1.0e) with ESMTP id FAA21124; Sat, 30 May 1998 05:41:49 -0400 (EDT)
Received: by reohub2.reo.dec.com with Internet Mail Service (5.5.1960.3) id <L4R2R4PH>; Sat, 30 May 1998 10:41:49 +0100
Message-ID: <250F9C8DEB9ED011A14D08002BE4F64C01A23E5D@wade.reo.dec.com>
From: Stephen Waters <Stephen.Waters@digital.com>
To: Avram Shacham <shacham@cisco.com>
Cc: ipsec@tis.com, ippcp@external.cisco.com
Subject: RE: IPCOMP and IPSEC
Date: Sat, 30 May 1998 10:38:53 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain

	I guess time will tell.  For remote-access VPN stuff (over the
Internet), there is no doubt that 
	stateless compression is what you use.  For some of the newer
VNP-focused providers offering
	QOS for LAN-to-LAN, it may be possible to use a history - even
for IPPCP.

	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.

	Cheers, Steve.


> ----------
> From: 	Avram Shacham[SMTP:shacham@cisco.com]
> Sent: 	Friday, May 29, 1998 9:37 PM
> To: 	Eric Dean
> Cc: 	Stephen Waters; ipsec@tis.com; ippcp@external.cisco.com
> Subject: 	RE: IPCOMP and IPSEC 
> 
> Eric,
> 
> At 04:20 PM 5/29/98 -0400, Eric Dean wrote:
> 
> >Streaming a contiguous file through a compression device is not 
> >indicative of real Internet traffic.  Packets of various application
> are 
> >interleaved within flows.  The Calgary files may be a good benchmark
> for 
> >comparing different compression algorithms in a stateful environment;
> 
>                                                  ^^^^^^^^ how comes?
> 
> >however, they do not represent the stateless environment that the 
> >Internet represents.
> 
> In my tests, I ftp-ed and http-ed random collection of files, with
> identical results, so it seems that the Calgary Files are a pretty
> good
> indication for non-pre-compressed files.
> 
> avram
> 
>