IETF Logo Mail Archive

Re: How we are planning to embed HTML in messages

Chris Newman <chrisn+@cmu.edu> Wed, 17 May 1995 17:31 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08302; 17 May 95 13:31 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08298; 17 May 95 13:31 EDT
Received: from dimacs.rutgers.edu by CNRI.Reston.VA.US id aa10618; 17 May 95 13:31 EDT
Received: (from daemon@localhost) by dimacs.rutgers.edu (8.6.10+bestmx+oldruq+newsunq+grosshack/8.6.10) id MAA14250 for ietf-822-list; Wed, 17 May 1995 12:08:01 -0400
Received: from po8.andrew.cmu.edu (PO8.ANDREW.CMU.EDU [128.2.10.108]) by dimacs.rutgers.edu (8.6.10+bestmx+oldruq+newsunq+grosshack/8.6.10) with ESMTP id MAA14246 for <ietf-822@dimacs.rutgers.edu>; Wed, 17 May 1995 12:07:59 -0400
Received: (from postman@localhost) by po8.andrew.cmu.edu (8.6.12/8.6.12) id MAA07114 for ietf-822@dimacs.rutgers.edu; Wed, 17 May 1995 12:06:35 -0400
Received: via switchmail; Wed, 17 May 1995 12:06:30 -0400 (EDT)
Received: from nifty.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/service/mailqs/testq0/QF.AjiVveu00WA7ACik4W>; Wed, 17 May 1995 12:06:03 -0400 (EDT)
Received: via niftymail; Wed, 17 May 1995 12:05:59 -0400 (EDT)
X-Orig-Sender: Chris Newman <chrisn+@cmu.edu>
Date: Wed, 17 May 1995 12:05:59 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Chris Newman <chrisn+@cmu.edu>
Subject: Re: How we are planning to embed HTML in messages
To: ietf-822@dimacs.rutgers.edu
In-Reply-To: <9505161432.ZM21977@zex.z-code.com>
References: <9505161451.AA07561@Accurate.COM> <800653998.3401.0@nifty.andrew.cmu.edu> <9505161432.ZM21977@zex.z-code.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-ID: <800726759.3401.0@nifty.andrew.cmu.edu>

 "Ben Liblit" <liblit@zex.z-code.com> writes:
> On May 16,  3:53pm, Chris Newman wrote:
> > Perhaps a simpler and better approach would be to have a new
> > multipart type, say "multipart/embedded", where the first part is a
> > hypermedia format (e.g. text/html) with references to the other parts.
> For an existing proposal along these lines, see
> <draft-ietf-mimesgml-multipart-rel-00.txt>:
> ...
> This draft even gives an example of embedded images, though in that case it
> is a JPEG embedded within a general SGML document.

I'm aware of multipart/related, and feel the optional "start"
parameter makes it unnecessarily complex.  In order to parse a
multipart/related with a start parameter, you need to make multiple
passes across the message.
-----
Chris Newman		     WWW - http://www.contrib.andrew.cmu.edu/usr/cn0h/

v2.23.0 | Report a Bug | By Email