IETF Logo Mail Archive

[Gendispatch] Re: Archival Dysfunction

Joel Halpern <jmh@joelhalpern.com> Wed, 10 July 2024 16:15 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC130C169405 for <gendispatch@ietfa.amsl.com>; Wed, 10 Jul 2024 09:15:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H7pH1fz1gtSS for <gendispatch@ietfa.amsl.com>; Wed, 10 Jul 2024 09:15:08 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E346FC18DBBA for <gendispatch@ietf.org>; Wed, 10 Jul 2024 09:15:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4WK2y43VVCz1q2Fc; Wed, 10 Jul 2024 09:15:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1720628108; bh=FOkXdgbHQQTw12Z17w7ziiGRzHYGlvUr2iPl7/ItgT8=; h=Date:Subject:To:References:From:In-Reply-To:From; b=NzdIjAUfd0sVQ2dNBQqdPSItlwKnv1oRhEsChYmw8qJYRD9YJ+OtRAZLJg/VRMEQM Be8UkTxeI2mwhDD/fdrKeQbUwmsvvOdEyGLh++P/ltvqniBFZAYxNA0PVAwkj6nKCE kWGr6RQXGqAYpf3DwotCBOjHy8pdtr1S5fXHsSPg=
X-Quarantine-ID: <z6AobNnnz8iQ>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.22.41] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4WK2y408Dqz1ntTl; Wed, 10 Jul 2024 09:15:07 -0700 (PDT)
Message-ID: <9c783e3d-f140-48fd-84ae-76c7a3a378a7@joelhalpern.com>
Date: Wed, 10 Jul 2024 12:15:07 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "gendispatch@ietf.org" <gendispatch@ietf.org>
References: <9442CCBF-EDF4-4FD7-AFBA-29EA301FB3DA@akamai.com> <4c00d259-653f-43d1-973e-2f9d38876585@gmail.com> <924C56EF-6EA5-4B7D-BC29-DD6710816692@akamai.com>
Content-Language: en-US
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <924C56EF-6EA5-4B7D-BC29-DD6710816692@akamai.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: REFKO7CFTDYZ2HBZMZJJLSMDONVXOFBE
X-Message-ID-Hash: REFKO7CFTDYZ2HBZMZJJLSMDONVXOFBE
X-MailFrom: jmh@joelhalpern.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Gendispatch] Re: Archival Dysfunction
List-Id: General Area Dispatch <gendispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/Qb7iIadYFnEcYDZNwwVGTDOulxQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Owner: <mailto:gendispatch-owner@ietf.org>
List-Post: <mailto:gendispatch@ietf.org>
List-Subscribe: <mailto:gendispatch-join@ietf.org>
List-Unsubscribe: <mailto:gendispatch-leave@ietf.org>

As John Levine suggests, there are a lot of ways for us to maintain 
history.

And, to get to the issue more directly, being unable to find and 
understand the history of how we reached conclusions (about process, 
policy, or technical substance) is distinctly problematic and invites 
repeating discussions even more often than we already do.

Yours,

Joel

On 7/10/2024 11:12 AM, Salz, Rich wrote:
>> I think the idea behind RFC4693 was fundamentally sound: if we don't treat this class of material as a formal series with archival properties, there will be information loss.
> Many influential people in the IETF have this strongly-held feeling that everything we do must be archived and forever available. That places an exceedingly high burden on our practices and processes. I'd even say it could lead to ossification.
>
>

v2.46.0 | Report a Bug | By Email | System Status