Re: MIME implementation documentation

Dave Crocker <dcrocker@brandenburg.com> Fri, 16 August 1996 15:30 UTC

Received: from ietf.org by ietf.org id aa18674; 16 Aug 96 11:30 EDT
Received: from cnri by ietf.org id aa18670; 16 Aug 96 11:30 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa08917; 16 Aug 96 11:30 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id LAA09671; Fri, 16 Aug 1996 11:22:26 -0400
Received: from ng.netgate.net (root@ng.netgate.net [204.145.147.10]) by list.cren.net (8.6.12/8.6.12) with ESMTP id LAA09641 for <ietf-822@list.cren.net>; Fri, 16 Aug 1996 11:22:08 -0400
Received: from [205.214.160.106] (d26.netgate.net [205.214.160.58]) by ng.netgate.net (8.7.4/8.6.9) with ESMTP id IAA25964; Fri, 16 Aug 1996 08:27:59 -0700 (PDT)
Message-Id: <v03007832ae3a3f819c0f@[205.214.160.106]>
Date: Fri, 16 Aug 1996 08:12:10 -0700
X-Orig-Sender: owner-ietf-822@list.cren.net
Precedence: bulk
Sender: ietf-archive-request@ietf.org
From: Dave Crocker <dcrocker@brandenburg.com>
To: Ned Freed <Ned.Freed@innosoft.com>
Cc: John C Klensin <klensin@mail1.reston.mci.net>, Ned Freed <Ned.Freed@innosoft.com>, ietf-822@list.cren.net, Harald.T.Alvestrand@uninett.no
Subject: Re: MIME implementation documentation
In-Reply-To: <01I8BUQ1R3XU8Y50ZG@INNOSOFT.COM>
References: "Your message dated Fri, 16 Aug 1996 05:47:51 -0400 (EDT)" <SIMEON.9608160551.A@muahost.mail1.reston.mci.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Sender: dcrocker@ng.netgate.net
X-Listprocessor-Version: 8.0 -- ListProcessor(tm) by CREN

At 3:00 AM -0700 8/16/96, Ned Freed wrote:
>entirely misplaced. MIME exceeded its design goals and became a general data
>structuring format before the first set of MIME RFCs were even out. There are

	indeed it did and I agree that MUAs aren't the only place to look
for satisfaction of the implementation/use.  But the use needs to be real.
The fact that RFC and I-D announcements use /alternative is a good start,
for believing the contruct is a good one.  But what receiving software is
there that uses this contruct meaningfully?  Is it used elsewhere?  (For
reference, I really DO want the answer to be yes.  I think is is a
marvelous construct.)

>Perhaps we aren't, but it seems to me that you are reading an awful
>lot into the proposed-->draft step of the process.

	this step doesn't require implementation into production systems;
demonstration is fine.  on the other hand, MIME ain't new and a lack of
implementation in production systems by now is not a good sign.  no?

d/

--------------------
Dave Crocker                                            +1 408 246 8253
Brandenburg Consulting                             fax: +1 408 249 6205
675 Spruce Dr.                                 dcrocker@brandenburg.com
Sunnyvale CA 94086 USA                       http://www.brandenburg.com

Internet Mail Consortium               http://www.imc.org, info@imc.org