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

Melinda Shore <mshore@cisco.com> Fri, 10 September 2004 14:18 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 KAA29561; Fri, 10 Sep 2004 10:18:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5mIM-0007KK-0H; Fri, 10 Sep 2004 10:22:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5m7N-0000kT-5r; Fri, 10 Sep 2004 10:11:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5lvT-0003rE-Q2 for ietf@megatron.ietf.org; Fri, 10 Sep 2004 09:58:55 -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 JAA26982 for <ietf@ietf.org>; Fri, 10 Sep 2004 09:58:53 -0400 (EDT)
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5lzW-0006wY-Fl for ietf@ietf.org; Fri, 10 Sep 2004 10:03:08 -0400
X-BrightmailFiltered: true
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i8ADwILp016636; Fri, 10 Sep 2004 06:58:18 -0700 (PDT)
Received: from cisco.com ([10.25.65.178]) by mira-sjc5-c.cisco.com (MOS 3.4.5-GR) with SMTP id AYW92173; Fri, 10 Sep 2004 06:58:16 -0700 (PDT)
Date: Fri, 10 Sep 2004 09:57:49 -0400
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v553)
To: sob@harvard.edu
From: Melinda Shore <mshore@cisco.com>
In-Reply-To: <20040910133022.46082861D6@newdev.harvard.edu>
Message-Id: <66EDBDB3-0331-11D9-B4E7-000A95E35274@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Cc: harald@alvestrand.no, 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: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit

On Friday, September 10, 2004, at 09:30 AM, scott bradner wrote:
> but, to me, its quite silly to pretend that IDs actually disapear
> from the net just because teh IETF takes it off of our web site

I don't think anybody's pretending that, but if there's an agreement
between the IETF and people who submit ids that the documents are
going to be disappeared from the IETF archive in six months, I think
it's kind of a problem to change that agreement retroactively.

On the other hand, I'd hate to see indecision about what to do
about old ids seep into indecision about what to do about new
ids going forward.  It seems to me that a new policy saying that
any ids submitted in the future will be archived by the IETF unless
the authors object is far better than allowing the current
situation to continue.  That wouldn't prevent us from going back
and revisiting the problem of old drafts at some future time,
either.

Melinda


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