Re: MIME implementation documentation
Dave Crocker <dcrocker@brandenburg.com> Fri, 16 August 1996 15:32 UTC
Received: from ietf.org by ietf.org id aa18763; 16 Aug 96 11:32 EDT
Received: from cnri by ietf.org id aa18756; 16 Aug 96 11:32 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa08950;
16 Aug 96 11:31 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net
(8.6.12/8.6.12) with SMTP id LAA09739; Fri, 16 Aug 1996 11:24:28 -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 LAA09722 for
<ietf-822@list.cren.net>; Fri, 16 Aug 1996 11:24: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 IAA25948;
Fri, 16 Aug 1996 08:27:47 -0700 (PDT)
Message-Id: <v03007830ae3a3db930d0@[205.214.160.106]>
Date: Fri, 16 Aug 1996 08:05:41 -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: Harald.T.Alvestrand@uninett.no
Cc: John C Klensin <klensin@mail1.reston.mci.net>,
Ned Freed <Ned.Freed@innosoft.com>, ietf-822@list.cren.net
Subject: Re: MIME implementation documentation
In-Reply-To: <9548.840179611@domen.uninett.no>
References: Your message of "Fri, 16 Aug 1996 00:11:05 EDT."
<SIMEON.9608160005.D@white-box.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
Harald, At 12:13 AM -0700 8/16/96, Harald.T.Alvestrand@uninett.no wrote: >That is, does "remove" mean "remove from specification", "move to a >document with another status", or "mark as not part of the standard"? I believe this one is easy. We make ALL of a document a standard, so we must remove from that document anything which does not qualify. I don't know that we've ever attended to the question of where to put excised parts, other than drop them on the floor. But as you observe, they might still have benefit, just not enough for standardization. In such cases, a new and separate document seems the right venue. >Shucks, we don't even have a feature list! > >The IESG vote is scheduled for next week. Do we have a volunteer to >do some work on this? >If not, I'm strongly tempted to declare that this document was already >at Draft, so we're just continuing a historical mistake..... Not so much a mistake as an intentional looseness. We take folks' word that they tested what they are supposed to test. This looseness has served us pretty well, I think. One always needs to look for checks and balances and in this case the primary forcing function is claims from others that one or another feature isn't really implemented or used. What's wrong with that mechanism? E.g., note that John K. raised a question about binary and Ned F. responded. Further discussion should/will take place about it as needed. Seems pretty diligent, to me. 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
- 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