Re: Is it necessary to go through Standards Track to Get to Historic?

Brian E Carpenter <brc@zurich.ibm.com> Wed, 31 August 2005 09:32 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAOww-00018Z-1a; Wed, 31 Aug 2005 05:32:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAOwt-00018U-TX for ietf@megatron.ietf.org; Wed, 31 Aug 2005 05:32:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10126 for <ietf@ietf.org>; Wed, 31 Aug 2005 05:32:01 -0400 (EDT)
Received: from mtagate2.de.ibm.com ([195.212.29.151]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EAOyb-0007vg-Jt for ietf@ietf.org; Wed, 31 Aug 2005 05:33:51 -0400
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate2.de.ibm.com (8.12.10/8.12.10) with ESMTP id j7V9Vrd7089226 for <ietf@ietf.org>; Wed, 31 Aug 2005 09:31:53 GMT
Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228]) by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j7V9Vrk0156010 for <ietf@ietf.org>; Wed, 31 Aug 2005 11:31:53 +0200
Received: from d12av02.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av02.megacenter.de.ibm.com (8.12.11/8.13.3) with ESMTP id j7V9VruO023110 for <ietf@ietf.org>; Wed, 31 Aug 2005 11:31:53 +0200
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d12av02.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id j7V9Vq5l023102 for <ietf@ietf.org>; Wed, 31 Aug 2005 11:31:52 +0200
Received: from zurich.ibm.com (sig-9-145-128-129.de.ibm.com [9.145.128.129]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id LAA39504 for <ietf@ietf.org>; Wed, 31 Aug 2005 11:31:51 +0200
Message-ID: <43157907.2000106@zurich.ibm.com>
Date: Wed, 31 Aug 2005 11:31:51 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: ietf@ietf.org
References: <4amb37$aq8r8o@mx02.mrf.mail.rcn.net> <200508302229.12923@mail.blilly.com>
In-Reply-To: <200508302229.12923@mail.blilly.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Subject: Re: Is it necessary to go through Standards Track to Get to Historic?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Bruce Lilly wrote:
...
> Aside from the label -- and that's not a clear benefit because Historic is
> ambiguous -- I don't see much difference between Historic and an
> Informational RFC with a suitable IESG note (a "warning label" if you will).
> 

There's a difference. For example, imagine a media type called

   splat/illogical

that's been used for some years but is generally considered to be
illogically named, and a new media type has been defined to do the
same thing:

   splot/logical

It would then be reasonable to document splat/illogical as Historic
to explain its IANA registration, and to document splot/logical as
Informational.

But you're certainly correct that a health warning in the text of
the RFC is more important than a status marker in the index.

    Brian


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf