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

"Perry E. Metzger" <perry@piermont.com> Wed, 19 February 1997 14:20 UTC

Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id JAA23399 for ipsec-outgoing; Wed, 19 Feb 1997 09:20:03 -0500 (EST)
Message-Id: <199702191422.JAA02189@jekyll.piermont.com>
X-Authentication-Warning: jekyll.piermont.com: [[UNIX: localhost]] didn't use HELO protocol
To: Bob Monsour <rmonsour@earthlink.net>
cc: ipsec@tis.com
Subject: Re: TO COMPRESS OR NOT TO CMPRS (please reply)
In-reply-to: Your message of "Tue, 18 Feb 1997 21:36:44 PST." <3.0.32.19970218213641.0092cc60@earthlink.net>
Reply-To: perry@piermont.com
X-Reposting-Policy: redistribute only with permission
Date: Wed, 19 Feb 1997 09:22:48 -0500
From: "Perry E. Metzger" <perry@piermont.com>
Sender: owner-ipsec@ex.tis.com
Precedence: bulk

Bob Monsour writes:
> While GIF files do likely make up a large percentage of traffic over
> dial-up links, I don't imagine that security functionality will be
> enabled/negotiated while viewing web pages.

I see you haven't heard of SSL, eh?

Security is very big on the web. People -- and I mean ordinary
consumers -- want to conduct transactions over it. With a reasonable
IPSec in place, SSL wouldn't have been necessary. SSL is used every
day by millions of people to keep their credit card data away from
prying eyes.

> I would expect that security functionality would be engaged wnnhen
> tunneling into the corporate network over the internet.

Security is useful most of the time, actually. I suspect that someday,
almost all traffic will be secure.

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

Perry