IETF Logo Mail Archive

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

"Theodore Ts'o" <tytso@mit.edu> Mon, 13 September 2004 19:53 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 PAA01390; Mon, 13 Sep 2004 15:53:42 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C6wy0-0008Tv-Id; Mon, 13 Sep 2004 15:58:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C6wfR-00075e-2A; Mon, 13 Sep 2004 15:39:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C6wbu-0004sd-Mf for ietf@megatron.ietf.org; Mon, 13 Sep 2004 15:35:35 -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 PAA00245 for <ietf@ietf.org>; Mon, 13 Sep 2004 15:35:28 -0400 (EDT)
Received: from [69.25.196.29] (helo=thunker.thunk.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C6wgL-00089v-VV for ietf@ietf.org; Mon, 13 Sep 2004 15:40:26 -0400
Received: from dsl092-109-027.nyc2.dsl.speakeasy.net ([66.92.109.27] helo=thunk.org) authenticated as tytso by thunker.thunk.org with asmtp (tls_cipher TLSv1:RC4-SHA:128) (Exim 3.35 #1 (Debian)) id 1C6wKg-0005AX-00; Mon, 13 Sep 2004 15:17:46 -0400
Received: from tytso by thunk.org with local (Exim 4.34) id 1C6wKf-0006rI-Gy; Mon, 13 Sep 2004 15:17:45 -0400
Date: Mon, 13 Sep 2004 15:17:45 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Joe Touch <touch@ISI.EDU>
Message-ID: <20040913191745.GA26277@thunk.org>
References: <72911B66-0506-11D9-B4E7-000A95E35274@cisco.com> <4144C796.7020200@isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4144C796.7020200@isi.edu>
User-Agent: Mutt/1.5.6+20040818i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Melinda Shore <mshore@cisco.com>, 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>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

On Sun, Sep 12, 2004 at 03:03:02PM -0700, 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.
> 
> Put them up in a public archive and that assertion is no longer true. It 
> becomes appropriate to use them as normative refs.
> 

Private correspondence does not be come citable as a normative
reference just because someone makes a web-archive of their e-mail
available.  Neither does making I-D's publically available past their
expiration point make it "legal" for them to be referrenced in RFC's. 

If you are referring to people outside of the standards process
referencing expired I-D's, there are people doing this today, and even
shipping product today, based on expired I-D's.  It seems unlikely to
me that making such an archive available in a public fashion
(especially given that they are available today already if you know
where to look in the .iso images of the IETF proceedings-on-cdrom)
will likely change the future frequency of such "illegal" references
to I-D's.

						- Ted

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

v2.23.0 | Report a Bug | By Email