From: Rick Busdiecker <rfb@lehman.com>
To: “Perry E. Metzger” <perry@imsi.com>
Message Hash: 9994d4d9d13d2151943f478aa2603e83dc47e12491a55024297a856d4bfa2b63
Message ID: <9502102043.AA11506@cfdevx1.lehman.com>
Reply To: <9502082303.AA10796@snark.imsi.com>
UTC Datetime: 1995-02-10 20:46:16 UTC
Raw Date: Fri, 10 Feb 95 12:46:16 PST
From: Rick Busdiecker <rfb@lehman.com>
Date: Fri, 10 Feb 95 12:46:16 PST
To: "Perry E. Metzger" <perry@imsi.com>
Subject: Re: MIME based remailing commands
In-Reply-To: <9502082303.AA10796@snark.imsi.com>
Message-ID: <9502102043.AA11506@cfdevx1.lehman.com>
MIME-Version: 1.0
Content-Type: text/plain
Date: Wed, 08 Feb 1995 18:03:57 -0500
From: "Perry E. Metzger" <perry@imsi.com>
xpat@vm1.spcs.umn.edu says:
> IMHO, an ideal message would have the ability to handle nested objects
> of varying types, MIME is only a start.
What is it precisely that you might want to encapsulate that MIME
can't encapsulate?
And in what way does MIME encapsulation aid in the privacy goals of
remailing?
It seems far more likely to require that you expose information which
you might prefer not to expose, much as the Privacy Enhanced Mail
standard does.
--
Rick Busdiecker <rfb@lehman.com> Please do not send electronic junk mail!
Lehman Brothers Inc.
3 World Financial Center "The more laws and order are made prominent, the
New York, NY 10285-1100 more thieves and robbers there will be." --Lao Tzu
Return to February 1995
Return to “xpat@vm1.spcs.umn.edu”