Re: nonexistent-WG Last Call on MIME documents
Ned Freed <Ned.Freed@innosoft.com> Wed, 19 June 1996 22:13 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09962;
19 Jun 96 18:13 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09958;
19 Jun 96 18:13 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa29497;
19 Jun 96 18:13 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net
(8.6.12/8.6.12) with SMTP id RAA17889; Wed, 19 Jun 1996 17:50:03 -0400
Received: from THOR.INNOSOFT.COM (THOR.INNOSOFT.COM [192.160.253.66]) by
list.cren.net (8.6.12/8.6.12) with ESMTP id RAA17866 for
<ietf-822@list.cren.net>; Wed, 19 Jun 1996 17:49:34 -0400
Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V5.0-7 #8694)
id <01I638MX03K0ADBV7T@INNOSOFT.COM>; Wed, 19 Jun 1996 14:48:48 -0700 (PDT)
Message-Id: <01I63HP4N464ADBV7T@INNOSOFT.COM>
Date: Wed, 19 Jun 1996 14:38:21 -0700 (PDT)
X-Orig-Sender: owner-ietf-822@list.cren.net
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Ned Freed <Ned.Freed@innosoft.com>
To: Erik van der Poel <erik@netscape.com>
Cc: ietf-822@list.cren.net
Subject: Re: nonexistent-WG Last Call on MIME documents
In-Reply-To: "Your message dated Wed, 19 Jun 1996 14:20:32 -0700"
<31C86F20.FF6@netscape.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Listprocessor-Version: 8.0 -- ListProcessor(tm) by CREN
> Note: I'm not subscribed to this ietf-822 list.
> The non-ASCII headers document that used to be called MIME Part 2 is now
> called MIME Part 3. I think this would be confusing to many. Many people
> use the term "MIME Part 2 headers" or "MIME-2 headers".
Haven't heard this myself. The usual usage I hear is "1522 headers". Before the
RFC number was assigned it was "YYYY" ("XXXX" was the euphemism for MIME
Part I).
As a practical matter, however, the IETF deals with changed numbering all the
time and don't seem to have a problem with it. The entire RFC process
inherently assigns numbers to documents, these numbers can, and do, change all
the time, and people have to cope with this whether they like it or not.
In other words, I think this is a needless worry about something of little
consequence.
> I would suggest either:
> 1. Call it MIME Part 2 as is it used to be, and give some other
> document the name MIME Part 3.
Not possible. The ordering of the documents is very carefully worked out to
minimize (but not eliminate) forward references. It cannot be changed without
tons of work, and even with tons of work I'm reasonably sure that the result
would not make any sense.
> 2. Don't give them part numbers at all. Just give them more
> descriptive names such as "MIME Non-ASCII Headers" or something like
> that.
Well, you can take the numbers out of the titles, and perhaps the RFC
Editor should do that, but if you really are right about people calling
the parts by relative position numbers I would not expect this to make
any difference.
Put another way, if relative numbering really is used, people are just going to
have to live with change. And if relative number really isn't used, the titles
make no difference.
Ned
- nonexistent-WG Last Call on MIME documents Harald.T.Alvestrand
- Re: nonexistent-WG Last Call on MIME documents hansen
- Re: nonexistent-WG Last Call on MIME documents Patrik Faltstrom
- Re: nonexistent-WG Last Call on MIME documents John Gardiner Myers
- Re: nonexistent-WG Last Call on MIME documents Erik van der Poel
- Re: nonexistent-WG Last Call on MIME documents Einar Stefferud
- Content-Disposition Charset Punt Rens Troost
- Re: nonexistent-WG Last Call on MIME documents Rens Troost
- Re: nonexistent-WG Last Call on MIME documents Ned Freed
- Re: nonexistent-WG Last Call on MIME documents Ned Freed
- Re: nonexistent-WG Last Call on MIME documents Harald.T.Alvestrand
- Re: nonexistent-WG Last Call on MIME documents Pete Resnick
- Re: nonexistent-WG Last Call on MIME documents Ned Freed