Re: MIME implementation documentation

Chris Newman <Chris.Newman@innosoft.com> Mon, 19 August 1996 23:43 UTC

Message-Id: <Pine.SOL.3.91.960819153244.4770A-100000@elbonia.innosoft.com>
Date: Mon, 19 Aug 1996 16:36:15 -0700 (PDT)
Precedence: bulk
Sender: ietf-archive-request@ietf.org
From: Chris Newman <Chris.Newman@innosoft.com>
To: Harald.T.Alvestrand@uninett.no, ietf-822@list.cren.net, moore@cs.utk.edu
Subject: Re: MIME implementation documentation
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Content-transfer-encoding: 7BIT

I believe Pine and IMAP4 servers (I know of at least 4 independant 
implementations) are examples of handling nested multiparts on the client 
side.  Pine numbers the parts in such a way that the nested structure is 
clearly visible to the user.  IMAP4 parses the MIME message into a 
hierarchical structure which preserves the nested represntation.

I am curious what will happen if the IESG rules that there isn't enough 
support for generation of arbitrary nested multiparts through a 
reasonable user interface.  The nesting structure of MIME is widely used, 
although it is usually used for special purpose sub-structure 
(multipart/appledouble, message/rfc822, multipart/security, etc) rather 
than general purpose hierarchy (although there seems to be plenty of 
support for displaying general purpose hierarchy in messages).

As for multipart/parallel, it does not seem to be widely implemented, nor 
does it seem to be an important part of the spec.  One reasonable option 
would be to remove the text from the spec and place it in the IANA media 
type registry.

Re: MIME implementation documentation Bart Schaefer
Re: MIME implementation documentation Chris Newman
Re: MIME implementation documentation Dave Crocker
Re: MIME implementation documentation Harald.T.Alvestrand
Re: MIME implementation documentation Bart Schaefer
Re: MIME implementation documentation Chris Newman
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation John C Klensin
Re: MIME implementation documentation Dave Crocker
Re: MIME implementation documentation Harald.T.Alvestrand
Re: MIME implementation documentation John C Klensin
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation Pete Resnick
Re: MIME implementation documentation John C Klensin
Re: MIME implementation documentation Dave Crocker
Re: MIME implementation documentation Dave Crocker
Re: MIME implementation documentation Dave Crocker
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation John C Klensin
Re: MIME implementation documentation Dave Crocker
Re: MIME implementation documentation Rens Troost
Re: MIME implementation documentation Pete Resnick
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation Pete Resnick
Re: MIME implementation documentation Jamie Zawinski
Re: MIME implementation documentation Pete Resnick
Re: MIME implementation documentation Harald.T.Alvestrand
Re: MIME implementation documentation ruth moulton
Re: MIME implementation documentation maf
Re: MIME implementation documentation Larry Masinter
Re: MIME implementation documentation Dave Crocker
Re: MIME implementation documentation Harald.T.Alvestrand
Re: MIME implementation documentation Harald.T.Alvestrand
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation Harald.T.Alvestrand
Re: MIME implementation documentation Valdis.Kletnieks
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation ruth moulton
Re: MIME implementation documentation John C Klensin
Re: MIME implementation documentation Harald.T.Alvestrand
Re: MIME implementation documentation Valdis.Kletnieks