Re: How we are planning to embed HTML in messages

Ben Liblit <liblit@zex.z-code.com> Tue, 16 May 1995 22:31 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13452; 16 May 95 18:31 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13447; 16 May 95 18:31 EDT
Received: from dimacs.rutgers.edu by CNRI.Reston.VA.US id aa15905; 16 May 95 18:31 EDT
Received: (from daemon@localhost) by dimacs.rutgers.edu (8.6.10+bestmx+oldruq+newsunq+grosshack/8.6.10) id RAA28814 for ietf-822-list; Tue, 16 May 1995 17:32:05 -0400
Received: from welch.ncd.com (root@welch.ncd.com [192.43.160.250]) by dimacs.rutgers.edu (8.6.10+bestmx+oldruq+newsunq+grosshack/8.6.10) with ESMTP id RAA28811 for <ietf-822@dimacs.rutgers.edu>; Tue, 16 May 1995 17:32:00 -0400
Received: from zex (zex.z-code.com [192.82.56.53]) by welch.ncd.com (8.6.9/8.6.6) with ESMTP id OAA00114 for <@internetgate.ncd.com:ietf-822@dimacs.rutgers.edu>; Tue, 16 May 1995 14:31:51 -0700
Received: by zex (950215.SGI.8.6.10/940406.SGI.AUTO) for ietf-822@dimacs.rutgers.edu id OAA21979; Tue, 16 May 1995 14:32:41 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Ben Liblit <liblit@zex.z-code.com>
Message-Id: <9505161432.ZM21977@zex.z-code.com>
Date: Tue, 16 May 1995 14:32:34 -0700
In-Reply-To: Chris Newman <chrisn+@CMU.EDU> "Re: How we are planning to embed HTML in messages" (May 16, 3:53pm)
References: <9505161451.AA07561@Accurate.COM> <800653998.3401.0@nifty.andrew.cmu.edu>
Reply-To: Ben Liblit <liblit@zex.z-code.com>
X-Mailer: Z-Mail (3.3dev.213 13feb95)
To: ietf-822@dimacs.rutgers.edu
Subject: Re: How we are planning to embed HTML in messages
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

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>:

       Abstract

       The Multipart/Related content-type provides a common
       mechanism for representing objects that are aggregates of
       related MIME body parts.  This document defines the
       Multipart/Related content-type and provides examples of its
       use.

This draft even gives an example of embedded images, though in that case it is
a JPEG embedded within a general SGML document.