[Rfced-future] Historical Properties

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 24 November 2021 03:43 UTC

Return-Path: <brian.e.carpenter@gmail.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 4B0C63A095D for <rfced-future@ietfa.amsl.com>; Tue, 23 Nov 2021 19:43:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 k7bVFYaaHjat for <rfced-future@ietfa.amsl.com>; Tue, 23 Nov 2021 19:43:29 -0800 (PST)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 157583A095A for <rfced-future@iab.org>; Tue, 23 Nov 2021 19:43:29 -0800 (PST)
Received: by mail-pj1-x1031.google.com with SMTP id nh10-20020a17090b364a00b001a69adad5ebso1343674pjb.2 for <rfced-future@iab.org>; Tue, 23 Nov 2021 19:43:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=NU0B2J1C1Aem0CLgZJ3t6vmxk9+07pRb21Y/NgVugjw=; b=OWI/Jx794l7KWx0ZAEw+RDWP1oQgqHhXY5rxw1CHlBdUx8T/pcjb1tE+TrVuZky2Ji Pzq0HW4R/kNSvTOX3Wf49KWz5cMJza38bJ9i1BEBlb2rMVYqtGqYGtOE8KiajIDWTLI1 pfuBYfSxsREhRugjMi6hhn0czEZQBBlrB43nWXBWYOp/aarqP4SwpKG4WDXIRF0r/GpI Dm8Susu2Z5sL4I2K0Ecdizt+AejzbtfiN72O8OmHVKOCcLOlSoh3KhoydTmOITaIGCDV /34SS1lO6FlX/6aVjhgqHexCroTcTOcP/ZGDPLWXc5+fUtoKTFqM0dWJ1brB4sru2YGj LUrg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=NU0B2J1C1Aem0CLgZJ3t6vmxk9+07pRb21Y/NgVugjw=; b=zS901OYgxLvhg0H9/WsZajA555J3AcqOyKRmRPDpYtFsJlBeHPzvqOd1Ijk0bRWEji dP5g1TTcD5n6J63fIcRVWfMTsmcoYvQarmZ0i501kYfM2k3YGPkWBunnKZkwQjs0mvvD kWqhgxXfY7ABHKgRyxTuW9cngffK6MlBkkev9npjndvuXATjEqTDjtRpvrGL0CDToB2O 98mG2AIyZRLhNSza6AZxvGVYgLGV1NDlrOjo20mZ6k+JErWjIxyKBJzRysgwkGkytwwe siKHjAnmTCkyajzR6VtSrYubJh7cESoOjbZa7QwJWNkOe9biAeSof4W4BAgXYYwDiJ6b i1jA==
X-Gm-Message-State: AOAM531MGoevqqlFuLtAdnFaEIaqCykK1gitRt69H4Nc/VLmUz/38lwU YNRodJutP1pno4ggPXG33B5yyqKEqhTq+w==
X-Google-Smtp-Source: ABdhPJwYyJmkhFTFwql+6TuIFEkAH77sY5u1Hxp82Kc/7zY5qQ+qH9+zJqlBEfWu/oxFVBHcYpU/9w==
X-Received: by 2002:a17:90a:6f61:: with SMTP id d88mr4161939pjk.109.1637725406907; Tue, 23 Nov 2021 19:43:26 -0800 (PST)
Received: from ?IPv6:2406:e003:102d:e801:80b2:5c79:2266:e431? ([2406:e003:102d:e801:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id nn15sm2776726pjb.11.2021.11.23.19.43.25 for <rfced-future@iab.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 23 Nov 2021 19:43:26 -0800 (PST)
To: rfced-future@iab.org
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <c5bf4074-acf7-ffb2-2bfe-f68beb3117b1@gmail.com>
Date: Wed, 24 Nov 2021 16:43:21 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/nsL6kmPaL8m7Q2BD4oaVUw8xzWg>
Subject: [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 03:43:33 -0000

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