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

kaih@khms.westfalen.de (Kai Henningsen) Wed, 15 September 2004 08:02 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 EAA10400; Wed, 15 Sep 2004 04:02:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C7Uph-0005fZ-Iq; Wed, 15 Sep 2004 04:08:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C7Uiv-0004JV-0H; Wed, 15 Sep 2004 04:01:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C7UYp-0001uv-K5 for ietf@megatron.ietf.org; Wed, 15 Sep 2004 03:50:39 -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 DAA09672 for <ietf@ietf.org>; Wed, 15 Sep 2004 03:50:37 -0400 (EDT)
Received: from colo.khms.westfalen.de ([213.239.196.208] ident=Debian-exim) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C7Udt-0005H6-O3 for ietf@ietf.org; Wed, 15 Sep 2004 03:55:54 -0400
Received: from khms.vpn ([10.172.192.2]:47367 helo=khms.westfalen.de ident=Debian-exim) by colo.khms.westfalen.de with asmtp (TLS-1.0:RSA_ARCFOUR_SHA:16) (Exim 4.34) id 1C7UXb-0000xC-4z for ietf@ietf.org; Wed, 15 Sep 2004 09:49:24 +0200
Received: from root (helo=khms.westfalen.de) by khms.westfalen.de with local-bsmtp (Exim 4.34) id 1C7LIp-0003hF-5R for ietf@ietf.org; Tue, 14 Sep 2004 23:57:31 +0200
Received: by khms.westfalen.de (CrossPoint v3.12d.kh14 R/C435); 14 Sep 2004 23:49:14 +0200
Date: Tue, 14 Sep 2004 20:55:00 +0200
From: kaih@khms.westfalen.de
To: ietf@ietf.org
Message-ID: <9GqMax3Hw-B@khms.westfalen.de>
In-Reply-To: <5.2.1.1.2.20040913130620.02e34200@boreas.isi.edu>
X-Mailer: CrossPoint v3.12d.kh14 R/C435
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Organization: Organisation? Me?! Are you kidding?
References: <5.2.1.1.2.20040913130620.02e34200@boreas.isi.edu>
X-No-Junk-Mail: I do not want to get *any* junk mail.
Comment: Unsolicited commercial mail will incur an US$100 handling fee per received mail.
X-Fix-Your-Modem: +++ATS2=255&WO1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
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: 244a2fd369eaf00ce6820a760a3de2e8

braden@ISI.EDU (Bob Braden)  wrote on 13.09.04 in <5.2.1.1.2.20040913130620.02e34200@boreas.isi.edu>:

> > > I have yet to see a coherent argument for keeping the ID series if it's
> > > archived publicly. Why do we need to see the entire process - in public
> > > - of editing and revision? And if we do, why do we need two separate
> > > series to do this?
> >
> >It's not a document series, it's preserving history - exactly the same way
> >that the mailing list archives do, using the exact same arguments. (And
> >incidentally, the exact same situation wrt. "getting published".)
> >
> >If you argue that you want to abolish the mailing list archives, I think
> >you'll find strong opposition; I certainly do not see why the I-D
> >situation is any different.

> This "preserving history" notion is an obfuscation.  If there is a stable
> reference to each particular I-D, then the set of I-Ds with those stable
> references necessarily form an archival document series.

You might as well claim that the mailing list archives create an archival  
document series. That is nothing but a red herring.

> The Original Intent of the IETF founding fathers was that the RFCs should
> form the stable, archival document series for the Internet technology,
> containing its entire intellectual history (to use Scott's term), while
> I-Ds were to be
> ephemeral.  This is analogous to academic publication; we archive only
> the finished papers, not the 17 drafts that go into the production of each
> paper.

But neither are those 17 drafts published, while the 17 I-Ds are. So, for  
that matter, is all the mailing list discussion around those drafts.

The situation is not even remotely parallel.

> Publication in a conference or journal is a filter that keeps us from
> hopelessly
> garbaging up the intellectual record.  The FFs believed that preserving
> I-Ds would
> lead to such a garbage pile with piles of chaff for every grain of wheat.

How on earth do I-Ds "hopelessly garbage up the intellectual record" when  
mailing list archives don't?! That doesn't even begin to make any sense.

> Of course, the IETF has drifted far away from this OI.
>
> But then, you knew all that.

"[T]hat the RFCs should form the stable, archival document series for the  
Internet technology" is certainly still true.

The "containing its entire intellectual history" part was never true, as  
far as I can tell, nor does that claim seem at all sensible. You cannot  
get the entire intellectual history from only looking at the end results.  
That much certainly should be obvious.

It seems to me your definition of "entire" must be really strange.

MfG Kai

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