[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: I-D ACTION:draft-ietf-asid-mime-direct-02.txt

To: Frank Dawson <fdawson@xxxxxxxxxxxxxxx>, "Alec Dun (Exchange)" <AlecDu@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: I-D ACTION:draft-ietf-asid-mime-direct-02.txt
From: Robert Moskowitz <rgm3@xxxxxxxxxxxx>
Date: Wed, 28 Aug 1996 07:40:01 -0400
Cc: "'Harald.T.Alvestrand@xxxxxxxxxx'" <Harald.T.Alvestrand@xxxxxxxxxx>, "'Tim Howes'" <howes@xxxxxxxxxxxx>, "'ietf-asid@xxxxxxxxx'" <ietf-asid@xxxxxxxxx>, "'ietf-calendar@xxxxxxx'" <ietf-calendar@xxxxxxx>
Reply-to: rgm3@xxxxxxxxxxxx
Sender: owner-ietf-calendar@xxxxxxx

At 01:05 PM 8/26/96, Frank Dawson wrote:
>
>The other concern is that MIME content types are now being used outside of a 
>MIME email transport environment. This is great! However, it also places 
>additional design considerations on our work. All problems are not just solved 
>by a "hammer" or in this case an email solution domain.

Excuse me for only joining this list now.

I have seen content types in HTTP as well, particularly if you use the
file-upload feature.  So what's the deal?

Robert Moskowitz
Chrysler Corporation
(810) 758-8212

Prev by Date: C&S Overview
Next by Date: Re: Cool Features - Was: (Re: Examples Are Somewhat Confusing)
Previous by thread: RE: I-D ACTION:draft-ietf-asid-mime-direct-02.txt
Next by thread: Re: I-D ACTION:draft-ietf-asid-mime-direct-02.txt
Index(es):
- Date
- Thread