IETF Logo Mail Archive

Re: archives (was The other parts of the report....

Joe Touch <touch@ISI.EDU> Mon, 13 September 2004 00:50 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24207; Sun, 12 Sep 2004 20:50:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C6f7p-000341-GN; Sun, 12 Sep 2004 20:55:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C6f16-0005Sp-Ej; Sun, 12 Sep 2004 20:48:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C6ezx-0005LO-43 for ietf@megatron.ietf.org; Sun, 12 Sep 2004 20:47:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24076 for <ietf@ietf.org>; Sun, 12 Sep 2004 20:47:11 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C6f4W-000311-MZ for ietf@ietf.org; Sun, 12 Sep 2004 20:51:58 -0400
Received: from [128.9.168.55] (upn.isi.edu [128.9.168.55]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i8D0jxJ26809; Sun, 12 Sep 2004 17:45:59 -0700 (PDT)
Message-ID: <4144ED4E.2070900@isi.edu>
Date: Sun, 12 Sep 2004 17:43:58 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Melinda Shore <mshore@cisco.com>
References: <B0E95E23-0508-11D9-B4E7-000A95E35274@cisco.com>
In-Reply-To: <B0E95E23-0508-11D9-B4E7-000A95E35274@cisco.com>
X-Enigmail-Version: 0.84.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: ietf@ietf.org
Subject: Re: archives (was The other parts of the report....
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>
Content-Type: multipart/mixed; boundary="===============0720904328=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d


Melinda Shore wrote:

> On Sunday, September 12, 2004, at 06:03 PM, Joe Touch wrote:
> 
>> Even the IETF distinguishes between normative refs and non-normative 
>> (though it has a penchant for wanting to redefine those words too). 
>> Private correspondence is not citable as a normative ref, nor are 
>> (currently) IDs.
> 
> 
> IDs aren't citable in RFCs at all, so I'm not sure why you brought
> that up.  The distinction between normative
> references is not that normative references can only be to formal
> documents and informative references to more casual documents.  The
> distinction is role-based.  Check out 
> http://www.rfc-editor.org/policy.html#policy.refs
> 
>> Put them up in a public archive and that assertion is no longer true. 
>> It becomes appropriate to use them as normative refs.
> 
> 
> Sorry, not true.
> 
> Melinda

The terms normative and non-normative existed long before the IETF. The 
idea that IDs shouldn't be cited non-normatively is an IETF-ism only.

Joe



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

v2.46.0 | Report a Bug | By Email | System Status