Re: MIME implementation documentation

John C Klensin <klensin@mail1.reston.mci.net> Fri, 16 August 1996 17:46 UTC

Received: from ietf.org by ietf.org id aa23886; 16 Aug 96 13:46 EDT
Received: from cnri by ietf.org id aa23876; 16 Aug 96 13:46 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa10972; 16 Aug 96 13:46 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id NAA13140; Fri, 16 Aug 1996 13:38:37 -0400
Received: from a4.jck.com (ns.jck.com [206.99.215.40]) by list.cren.net (8.6.12/8.6.12) with ESMTP id NAA13122 for <ietf-822@list.cren.net>; Fri, 16 Aug 1996 13:38:24 -0400
Received: from white-box.jck.com ("port 2122"@white-box.jck.com) by a4.jck.com (PMDF V5.0-5 #16053) id <0DW8RO08T006UB@a4.jck.com>; Fri, 16 Aug 1996 13:38 -0400 (EDT)
Message-Id: <SIMEON.9608161323.A@muahost.mail1.reston.mci.net>
Date: Fri, 16 Aug 1996 13:38:23 -0400 (EDT)
Reply-To: John C Klensin <klensin@mail1.reston.mci.net>
X-Orig-Sender: owner-ietf-822@list.cren.net
Precedence: bulk
Sender: ietf-archive-request@ietf.org
From: John C Klensin <klensin@mail1.reston.mci.net>
To: Pete Resnick <presnick@qualcomm.com>
Cc: Dave Crocker <dcrocker@brandenburg.com>, Ned Freed <Ned.Freed@innosoft.com>, ietf-822@list.cren.net, Harald.T.Alvestrand@uninett.no
Subject: Re: MIME implementation documentation
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
X-Mailer: Simeon for Windows Version 4.1a5
X-Authentication: none
X-Listprocessor-Version: 8.0 -- ListProcessor(tm) by CREN

On Fri, 16 Aug 1996 09:43:55 -0500  Pete Resnick 
<presnick@qualcomm.com> wrote:
> Just to name names: I know that Cyberdog on the Macintosh and Microsoft's
> new mail and news offering (the latter for which I don't know the release
> status) both produce multipart/alternative by default (without "by-hand"
> user manipulation) for certain types of messages.

Well, that is considerable progress, although it would be nice 
to know
  -- what types of messages
and 
  -- what really acts on these on receipt, other than treating 
them as "mixed".

Note that we can't appeal to HTTP for validation of any of the 
multipart formats -- they quite aggressively don't use them.

   john