Re: MIME implementation documentation
John C Klensin <klensin@mail1.reston.mci.net> Fri, 16 August 1996 09:57 UTC
Received: from ietf.org by ietf.org id aa07869; 16 Aug 96 5:57 EDT
Received: from cnri by ietf.org id aa07865; 16 Aug 96 5:57 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa04638;
16 Aug 96 5:56 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net
(8.6.12/8.6.12) with SMTP id FAA26127; Fri, 16 Aug 1996 05:48:24 -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 FAA26112 for <ietf-822@list.cren.net>;
Fri, 16 Aug 1996 05:47:54 -0400
Received: from white-box.jck.com ("port 2026"@white-box.jck.com)
by a4.jck.com (PMDF V5.0-5 #16053) id <0DW85VS9I006UB@a4.jck.com>; Fri,
16 Aug 1996 05:47 -0400 (EDT)
Message-Id: <SIMEON.9608160551.A@muahost.mail1.reston.mci.net>
Date: Fri, 16 Aug 1996 05:47:51 -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: Dave Crocker <dcrocker@brandenburg.com>
Cc: 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 Thu, 15 Aug 1996 23:01:25 -0700 Dave Crocker <dcrocker@brandenburg.com> wrote: > Yes, we need to audit functions not implemented and remove them > from the spec. do you have any candidates for removal? Just a hunch, based on MUAs I've looked at recently, but multipart/alternative and multipart/parallel are good starters. The only creation-implementations I know of either require either hand-fussing (e.g., editing proto-outgoing-messages from /mixed) or specialized assembly macros that are not what we normally consider MUAs (e.g., the process used to prepare the I-D announcements). The difficulty I'm having here is that I consider at least one of these to be a very valuable and important feature (which makes the question Harald asks about what we do about the stuff that we "remove" very important), but I wonder if we really have the implementations. Parallel is even worse, because I've been involved in several conversations (and imagine others have too) that question whether it really is the right design and contains the right information to permit a sender to convey adequate information to a receiver to make the thing useful. And we find that out only by implementing the thing and getting it out there widely enough to accumulate some serious operational experience. The problem here, obviously, is that coming up with an implementation of these things in the sense of some prototype- or demonstration-quality critter that can demonstrate the ability to put the right format out on the wire and then read it from the wire is trivial and uninteresting. Implementing to a level of quality needed to show actual utility -- that the feature has the right syntax and semantics to actually serve useful purpose as defined -- is, IMO, another matter and I'm not convinced that we are there yet. john
- 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