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

Dennis Glatting <dennis.glatting@plaintalk.bellevue.wa.us> Wed, 19 February 1997 20:34 UTC

Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id PAA26565 for ipsec-outgoing; Wed, 19 Feb 1997 15:34:43 -0500 (EST)
Message-Id: <199702192038.MAA00732@imo.plaintalk.bellevue.wa.us>
Content-Type: text/plain
MIME-Version: 1.0 (NeXT Mail 3.3 v118.2)
From: Dennis Glatting <dennis.glatting@plaintalk.bellevue.wa.us>
Date: Wed, 19 Feb 1997 12:38:52 -0800
To: EKR <ekr@terisa.com>
Subject: Re: TO COMPRESS OR NOT TO CMPRS (please reply)
cc: Bob Monsour <rmonsour@earthlink.net>, perry@piermont.com, ipsec@tis.com
Reply-To: dennis.glatting@plaintalk.bellevue.wa.us
References: <199702191743.JAA14968@itech.terisa.com>
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).
>
> Well, sort of:
>
> There is a socket for compression to be plugged into. There are
> no defined compression plugs (other than null) and I don't
> expect there to be any for some time.
>

There is a proposed compression scheme for TLS:
draft-sabin-lzs-tls-00.txt


-dpg