Re: TO COMPRESS OR NOT TO CMPRS (please reply)

Bob Monsour <rmonsour@earthlink.net> Wed, 19 February 1997 15:14 UTC

Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id KAA23799 for ipsec-outgoing; Wed, 19 Feb 1997 10:14:26 -0500 (EST)
Message-Id: <3.0.32.19970219071752.0094a7e0@earthlink.net>
X-Sender: rmonsour@earthlink.net
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Wed, 19 Feb 1997 07:17:54 -0800
To: perry@piermont.com
From: Bob Monsour <rmonsour@earthlink.net>
Subject: Re: TO COMPRESS OR NOT TO CMPRS (please reply)
Cc: Bob Monsour <rmonsour@earthlink.net>, ipsec@tis.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ipsec@ex.tis.com
Precedence: bulk

At 09:22 AM 2/19/97 -0500, Perry E. Metzger wrote:
>I see you haven't heard of SSL, eh?

I am very aware of SSL (and it provides support for compressing prior to
encrypting).

>Certainly at 28.8kbps the added CPU burden is unnoticeable, so why
>*not* encrypt everything?

The issue for doing the work is less a burden for the client than it is for
the server. I completely agree that at the client end, the overhead is
unnoticeable. However, at the server/aggregation points for all these
clients, the workload would be substantial, if not overwhelming (i.e.,
without hardware assist). This is true in the case for compression today.
In some routers that support PPP compression today, if the load on the
router becomes too great so that the network pipe can't be kept saturated,
the compression is turned off.

-Bob