many of us like your compression addition and would like it widely (if
not ubiquitously!) implemented.
One perceived barrier to the adoption of s/mime is the expansion of
message size due to the repeated application of transfer (base64)
encoding at each wrap. Messaging system operators become alarmed when
told message sizes may more than double as a result. (Indeed the NIST
draft profile depreciates such coding of inner wraps to address this
The ability to offer compression also addresses overall message
expansion and will be an important capability to offer in compensation
when "marketing" the adoption of s/mime by large organizations.
[mailto:owner-ietf-smime(_at_)mail(_dot_)imc(_dot_)org] On Behalf Of Peter
Sent: July 9, 2002 4:49 AM
Subject: Re: I-D ACTION:draft-ietf-smime-rfc2633bis-01.txt
"Blake Ramsdell" <blake(_at_)brutesquadlabs(_dot_)com> writes:
I didn't see much uptake on this besides Russ saying "MAY", and I'm
about compatibility. I will put a slide in my presentation about this
AFAIK the major use at the moment is in EDI environments (large, highly-
compressible messages, and everything is "by prior arrangement" anyway).
are a couple of apps which support it out there though, so having it
would be nice just to let implementers know it's there.