RE: IPCOMP and IPSEC

Eric Dean <edean@gip.net> Mon, 01 June 1998 12:07 UTC

Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id IAA10292 for ipsec-outgoing; Mon, 1 Jun 1998 08:07:52 -0400 (EDT)
Date: Sat, 30 May 1998 17:09:50 -0400
From: Eric Dean <edean@gip.net>
To: Avram Shacham <shacham@cisco.com>
cc: Stephen Waters <Stephen.Waters@digital.com>, ipsec@tis.com, ippcp@external.cisco.com
Subject: RE: IPCOMP and IPSEC
In-Reply-To: <3.0.2.32.19980529133701.006b1dd8@airedale.cisco.com>
Message-ID: <Pine.SOL.3.91.980530165844.3686A-100000@yaway.gsl.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-ipsec@ex.tis.com
Precedence: bulk

> >comparing different compression algorithms in a stateful environment; 
>                                                  ^^^^^^^^ how comes?

Looking at the queue state of a typical Internet router, there is next to 
no correlation of any packets within the queue.  Therefore, maintaining a 
state (or history) is not of significant value because the patterns are 
random.  For instance, I rarely have two packets belonging to the same 
flow (or session) in my queue at the same time.

Now, if one were to FTP some files, one at a time, and have no other 
concurrent activity, then the queue serving the local segment would 
contain only packets from the single session.  These packets would be 
highly correlated and therefore should compress relatively well (assuming 
that they are not already compressed).

>From a packet compression perspective, the Internet is a stateless 
environment.  Now if one were to build VPN's with IPSEC, then one might 
achieve better compression ratios.

-eric