Re: [Rfced-future] Historical Properties

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 24 November 2021 15:47 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BC833A081C for <rfced-future@ietfa.amsl.com>; Wed, 24 Nov 2021 07:47:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.95
X-Spam-Level:
X-Spam-Status: No, score=-3.95 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, NICE_REPLY_A=-1.852, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fi60AMGXXd5w for <rfced-future@ietfa.amsl.com>; Wed, 24 Nov 2021 07:47:12 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D58B33A081A for <rfced-future@iab.org>; Wed, 24 Nov 2021 07:47:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4HzlkS0lVHz1pKDf; Wed, 24 Nov 2021 07:47:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1637768832; bh=iVzWtmJhIJHFrJNUGsHnKrIboZYtpWblDyLdHQayAp0=; h=Date:Subject:To:References:From:In-Reply-To:From; b=iynANkG5Wz4bVSwYjfn1Kog6DNwj2f2Fm2phDNgd83FHePqElo9ShtuQnTemk63B8 L+9U8wHRK5BIopNa4Qr9Td5nxeBXh4a6mL9A4C52FH+/Vb3unWf/1HYgYzzQJCqnre cqROiptYRSxQ4plXxlE5N/XXVjAccEM2l85SA/DQ=
X-Quarantine-ID: <JooDlfV1iRzF>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.22.111] (50-233-136-230-static.hfc.comcastbusiness.net [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 4HzlkR4QGbz1pKHZ; Wed, 24 Nov 2021 07:47:11 -0800 (PST)
Message-ID: <15999ff1-df92-0dda-6332-ac93c0b3f0c8@joelhalpern.com>
Date: Wed, 24 Nov 2021 10:47:10 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.2
Content-Language: en-US
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, rfced-future@iab.org
References: <c5bf4074-acf7-ffb2-2bfe-f68beb3117b1@gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <c5bf4074-acf7-ffb2-2bfe-f68beb3117b1@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/KNRE0jwhPO0k3a7Kdo1UMz8Qxqc>
Subject: Re: [Rfced-future] Historical Properties
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Nov 2021 15:47:17 -0000

It seems to me that some version of stable document references / 
unmodifiabl / archival belongs in that list.  (Archival is in the 
introduction.  Repeating here seems sensible to me.)

Yours,
Joel

On 11/23/2021 10:43 PM, Brian E Carpenter wrote:
> At the risk of finding a lot of messages in my inbox tomorrow,
> here's a proposed shorter alternative to Mike's "RFC Principles".
> Obviously a different slant, and I'm sure Peter will spot
> some overlaps with existing text:
> 
> # Historical Properties of the RFC Editor Series
> 
> The following describes some historical properties of
> the RFC Series. Proposals to modify any of these properties
> should not be taken forward without a strong community consensus
> including not only active RSWG/RSAB members but also the user
> community of each RFC stream.
> 
> ## Availability
> 
> The RFC series documents have been freely available digitally for more
> than 35 years, with no fee for access. The IETF Trust [legal provisions]
> (https://trustee.ietf.org/documents/trust-legal-provisions/) apply.
> 
> ## Accessibility
> 
> There is a general goal to make the RFC series documents as accessible
> as possible to communities that have special needs, e.g., for those
> with impaired sight.
> 
> ## Publication Language
> 
> The publication language of the series is English. Although
> translations of RFCs into other languages are welcomed, the
> English version is normative.
> 
> ## Diversity of Interests
> 
> In addition to Internet standards, the RFC series has published
> procedural and informational documents, thought experiments, speculative
> ideas, research papers, histories, humor [RFC1149, RFC2549], and even
> eulogies [RFC2468].  Various communities have contributed to the rich 
> history
> of the RFC series, and to its somewhat human-centric take on networking.
> This why several streams of RFCs exist in addition to the IETF stream,
> and why the RFC "brand" is wider than the IETF. This is also why the
> series does not have a "house style" and allows for individual expression.
> 
> ## Document Quality
> 
> Nevertheless, since RFCs need to be archived indefinitely and must
> be of use to a widespread international community, quality, readability
> and accuracy are key to the success of the RFC Series. It is
> understood that sometimes this stands in the way of rapid publication.
> 
>     Brian C
>