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

Carl Malamud <carl@media.org> Sat, 11 September 2004 19:09 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 PAA03711; Sat, 11 Sep 2004 15:09:11 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C6DJd-0005Pp-Ui; Sat, 11 Sep 2004 15:13:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C6DCX-0006ZS-4N; Sat, 11 Sep 2004 15:06:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C6D88-00026l-Js for ietf@megatron.ietf.org; Sat, 11 Sep 2004 15:01:48 -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 PAA02979 for <ietf@ietf.org>; Sat, 11 Sep 2004 15:01:47 -0400 (EDT)
Received: from bulk.resource.org ([192.101.98.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C6DCT-0005KJ-0b for ietf@ietf.org; Sat, 11 Sep 2004 15:06:17 -0400
Received: from bulk.resource.org (localhost.resource.org [127.0.0.1]) by bulk.resource.org (8.12.2/8.12.2) with ESMTP id i8BJ1F6Y004017; Sat, 11 Sep 2004 12:01:15 -0700 (PDT)
Received: (from carl@localhost) by bulk.resource.org (8.12.2/8.12.2/Submit) id i8BJ1FvZ004015; Sat, 11 Sep 2004 12:01:15 -0700 (PDT)
From: Carl Malamud <carl@media.org>
Message-Id: <200409111901.i8BJ1FvZ004015@bulk.resource.org>
In-Reply-To: <20040911122512.119BF889BC@newdev.harvard.edu>
To: scott bradner <sob@harvard.edu>
Date: Sat, 11 Sep 2004 12:01:15 -0700
Organization: Memory Palace Press
X-Winch: Warn 9.5i
X-Mailer: ELM [version 2.4ME+ PL94 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit
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>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Content-Transfer-Encoding: 7bit

Hi Scott -

Thanks for pointing out the proceedings.  Having the i-d's published
there certainly demonstrates how futile it is to pretend that we
can erase history.  The position that Bill Manning and Joe Touch are
taking reminds of when I was ordered by the Secretary-General of
the ITU to erase all Internet copies of their standards.

I was a little puzzled by the strong reaction of both Bill Manning
and Joe Touch.  They seem to be bringing up two points:

1. Bill has pointed out that some I-D's are *not* offered in
accordance with section 10 of rfc2026 and thus, as I understand
his reasoning, he only granted a 6-month license to publish.

2. Joe seems to take a stronger position, which is all I-D's are
(or have been) granted only a 6-month license to publish.

I went back and reviewed the RFC's (many of which you wrote),
and they are extremely unclear on the subject.  In fact, 2026
makes it clear that all the I-D's will be archived.  Earlier
docs don't touch on the subject.  And, the preamble appended
to every draft is pretty unclear.

What is clear is that an I-D is "valid" for only six months.
As I understand that term it means "on the table for consideration
by the IESG or others as a possible standard."

With all due respect, it seems to me that there is no prior
policy on this subject and the texts are very much subject to
differing interpretations.  I believe both Bill and Joe are taking
very extreme positions on the subject and I'm not sure their views
reflect anything resembling a prior policy, or even a universal
understanding.  It seems like a very legalistic interpretation
of a very vague policy, and (imho) that policy goes against
core values like openess, and transparency.

In any case, it does sound like decomposing the problem into two
pieces makes sense:

1. make a clear going-forward "keep all drafts in an archive" policy
2. figure out if there might be a community consensus to decide
   what the prior policy was, perhaps using a mechanism such as
   opt-out if there is a vocal but very small minority who disagrees.

Regards,

Carl

> 
> Something was pointed out to me in private mail that I should have 
> remembered but did not.
> 
> Since Aug 1998 the IETF proceedings have included the then-current 
> Internet drafts (except for one meeting which seems to be missing).
> 
> As I recall, this was started when the secretariat started offering CDs 
> of the proceedings and there was extra space on the CDs. It was 
> decided to include the IDs since the space was there to do so. 
> (My memory is that Steve Coya suggested this to the IESG and the 
> IESG thought it was a good idea.)
> 
> Anyway - that means that most IDs since mid 1998 are already posted on
> the IETF web site, they are just not posted in an easy to use way.
> 
> see
> 
> http://www.ietf.org/proceedings/98aug/I-D/
> http://www.ietf.org/proceedings/98dec/I-D/ 
> http://www.ietf.org/proceedings/99mar/I-D/ 
> http://www.ietf.org/proceedings/99jul/I-D/
> http://www.ietf.org/proceedings/99nov/I-D/
> 00mar - missing
> http://www.ietf.org/proceedings/00jul/I-D/
> http://www.ietf.org/proceedings/00dec/I-D/
> http://www.ietf.org/proceedings/01mar/I-D/
> http://www.ietf.org/proceedings/01aug/I-D/
> http://www.ietf.org/proceedings/01dec/I-D/
> http://www.ietf.org/proceedings/02mar/I-D/
> http://www.ietf.org/proceedings/02nov/I-D/
> http://www.ietf.org/proceedings/03mar/I-D/
> http://www.ietf.org/proceedings/03jul/I-D/
> http://www.ietf.org/proceedings/03nov/I-D/
> http://www.ietf.org/proceedings/04mar/I-D/
> 
> Scott
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> 

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