1996-02-28 - Re: RE: [ Death of MOSS? ]

Header Data

From: galvin@eit.com (James M. Galvin)
To: BKnowles@aol.net
Message Hash: a2f62a8ab5574d09eb2c3b7e523c5eb1d5f652eb2cc0db9c395c1df49cd6f234
Message ID: <v02140b20ad5a0a8da1cd@[153.37.6.9]>
Reply To: N/A
UTC Datetime: 1996-02-28 17:22:45 UTC
Raw Date: Thu, 29 Feb 1996 01:22:45 +0800

Raw message

From: galvin@eit.com (James M. Galvin)
Date: Thu, 29 Feb 1996 01:22:45 +0800
To: BKnowles@aol.net
Subject: Re: RE: [ Death of MOSS? ]
Message-ID: <v02140b20ad5a0a8da1cd@[153.37.6.9]>
MIME-Version: 1.0
Content-Type: text/plain


At 12:44 AM 2/28/96, Brad Knowles wrote:
>    And if you look at what I've said previously, it is my firm belief
>that if we are to succeed in giving users a truly interoperable secure
>email standard, then said standard must be fully and completely
>integrated into MIME and do everything it does in the proper MIME way,
>as opposed to just being security grafted on.

Allow me to make a contentious statement:

        MOSS is the only secure email protocol integrated with MIME.

You see, integrated to me means that the base is security aware.  MIME is
only security aware when the security multiparts are used.  In all other
cases, MIME is not security aware.

The use of the application content-type with experimentally defined
subtypes gives the appearance of MIME being security aware, but it provides
nothing more than a mechanism for carrying a protected object.  In
addition, the fact that the security service itself must do a callback in
order to support recursive services, unlike MOSS which uses the security
multiparts framework and thus lets MIME do all the work it was designed to
do, further supports my position.

Jim

----------------------------------------------------------------------------
James M. Galvin                                               galvin@eit.com
VeriFone/EIT, PO Box 220, Glenwood, MD 21738                 +1 410.795.6882







Thread