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

sob@harvard.edu (scott bradner) Fri, 10 September 2004 19:44 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 PAA26810; Fri, 10 Sep 2004 15:44:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5rOE-0006Jr-NQ; Fri, 10 Sep 2004 15:48:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5r7S-0007hX-FA; Fri, 10 Sep 2004 15:31:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5qyU-0001bo-L1 for ietf@megatron.ietf.org; Fri, 10 Sep 2004 15:22:22 -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 PAA24999 for <ietf@ietf.org>; Fri, 10 Sep 2004 15:22:19 -0400 (EDT)
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5r2a-0005kS-UI for ietf@ietf.org; Fri, 10 Sep 2004 15:26:38 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501) id 4468B87159; Fri, 10 Sep 2004 15:21:49 -0400 (EDT)
To: ietf@ietf.org
Message-Id: <20040910192149.4468B87159@newdev.harvard.edu>
Date: Fri, 10 Sep 2004 15:21:49 -0400
From: sob@harvard.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
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: 0a7aa2e6e558383d84476dc338324fab

Bob sez:
> On the other hand, the expiration does (should) limit
> the ability to reference I-Ds as if they really existed. 

my experience is far more "should" than "does"

as an editor I'm getting more and more manuscripts that refer to
IDs by file name (I ask that the references be changed but ...) and
I'm seeing more and more such references in publications all the time

> in real academic publishing, as well
> as in IETF documents 10 years later, then the referenced documents MUST
> be archival. 

that would be nice but the growing number of URLs in such documents
seems to be a sad fact of life (inlcuding in court decisions!)

> Are you, or are you not, suggesting
> that I-Ds should become archival in this very important sense?

this is a hard question (I know, that is why you asked it)
clearly, making an archive of old IDs available on the IETF web site
would encourage people to see them as archive but I'm not sure
how much more encouragement that is over today's reality - there are
also much technology that is only available in expired IDs (and many
lessons on what not to do could be learned by seeing what did not 
make it through to the final RFC)

The reasons I'd like to see an offical archive are:
 1/ to make IPR prior art searches a little bit easier (at least the
    archive would be in an easy to find place)

 2/ make it easier for the IETF to respond to discovery requests 
    we could get some of the way there by just having the 
    archive maintained "in the normal course of business" but not
    made public but if the material is actually public then 
    we do not have to do anthing more than saying "look on
    our offical site" for that info and we do not need to
    produce the bits directly to the lawyers (responding to
    the discovery demands in the cases where I was involved 
    took quite a bit of work at Foretec - they did it and did 
    it well but it took them away from doing other things - and
    I do not expect that the IETF will stop getting requests
    in the future.

 3/ these documents are part of the intellectual history of the IETF
    and its sad that we are hiding that

the question of creating an assumption of archiveless is a byproduct
of the above is a real question and I do not know the answer

Scott


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