Path: utzoo!attcan!uunet!cs.utexas.edu!usc!orion.oac.uci.edu!ucivax!gateway
From: jwagner@princeton.edu
Newsgroups: comp.protocols.iso.x400
Subject: Re: DATA Compression and X400 standards
Message-ID: <9011051504.AA02887@idunno>
Date: 5 Nov 90 15:08:16 GMT
Lines: 13
Approved: usenet@ICS.UCI.EDU
In-Reply-To: Your message of 01 Nov 90 16:19:21 +0000.
             <2279@excelan.COM>

> I really vote for the Sending and Receiving UAs to do the compression.
> It calls for a little bit of intelligence on the UA part.  It also
> makes sense.  The message originator knows about the types of body-parts
> and the compresss algorithm used.  The receiving UA has to do the
> uncompress operation.  The job of MTA is to transfer the message rather
> than changing/modifying it on the fly.  If the receiving UA can handle
> the new compress method, all the MTAs in the route need not change at

While this approach seems attractive to me also, how does the sending UA know
the receiving UA can handle the compresssion?  This becomes even more
important if the sending UA is isolated (for example on a BITNET node).

   John Wagner