[Rfced-future] RFC Principles - long delayed
Michael StJohns <msj@nthpermutation.com> Thu, 11 November 2021 17:20 UTC
Return-Path: <msj@nthpermutation.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 CB7363A0D4E for <rfced-future@ietfa.amsl.com>; Thu, 11 Nov 2021 09:20:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=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=nthpermutation-com.20210112.gappssmtp.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 yzL2_KFIeENM for <rfced-future@ietfa.amsl.com>; Thu, 11 Nov 2021 09:20:55 -0800 (PST)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 A97843A0EC2 for <rfced-future@iab.org>; Thu, 11 Nov 2021 09:20:37 -0800 (PST)
Received: by mail-qt1-x82e.google.com with SMTP id l8so5969355qtk.6 for <rfced-future@iab.org>; Thu, 11 Nov 2021 09:20:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:content-language:to:from :subject:content-transfer-encoding; bh=eDtBJaqKOfh7ocWb01K+Dlc/yLBB3mrrPKsgKSg/jnQ=; b=S3aUYYxiz0yay/dEqELwB5vZnxKVZRQ/KsEHPCegC8vc8CMRBPTQhWsY1Eka0LPfbQ WKocCeutdeukDZMBrQ/8qQC+t+FV7vCHVHZrql4ZSe0e7nIVK63kaKmHCn5Wk/tGXO6X AlYrGlI04bp0wfajAMHvvrpasT5xCbFrHu2aNyinoRhZH9lndFqctlC70lPfyI/X3WJx c73giaMNqi/IVxUEKROnkgrPSGFjbOExZE9qvEB+a0jT+guHFqTt4hJuOZlt5yKomikJ h1IazND8UVFbFMe9ECA7pev1K1w/ZsRw7q4rfdUduLx/HWFtHuVMXTYr+EvYEebPWEn3 2fDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent :content-language:to:from:subject:content-transfer-encoding; bh=eDtBJaqKOfh7ocWb01K+Dlc/yLBB3mrrPKsgKSg/jnQ=; b=07NfADyXCHlHfT/p0VP6pMeVpRlTNXPyB8Do/wNSYO3zyFEYZoffYRwTWH4W5q61ZY EXJIoQb39RkMsx3OwOpFsHZmybcN0wqQhvrJCkWjT40RhkPXQbrwqHyuguvDV2NqR2nG K91Qeqk6zz8UyhrGqB1wLSHnegcZR31k0h7VKhOqeEiiVKeyaqPKHhAqWZz99JfLtJ4U 2JD4QEmIpg1C+zAlDGzCdlSuhWVMfT94Zw3+rbxeXBJjjaZL8WAu5BQc98TMUB5nOXx5 JGKVlpEq6BHvlCVwt9hk3m1TcDuLTmt95NEtjMCavgtSi6OFQXt1t6u5pzkK5qf8UDta CwSg==
X-Gm-Message-State: AOAM530STN9k2SQnbSstUuaifp5mOOc5hrwunYuW8s5dTZflG/uAAruh MJ1w5/h3kcBw8GnP+uaKCXDCEMIuJv6aHMUi
X-Google-Smtp-Source: ABdhPJwuUz/5jzljRnS4IvXCCgbw10R9jDh7dr8O87r2bezuuakdZAe7j28fuQbSBOHfgv3pi5QChg==
X-Received: by 2002:a05:622a:151:: with SMTP id v17mr9225999qtw.167.1636651234491; Thu, 11 Nov 2021 09:20:34 -0800 (PST)
Received: from [192.168.1.23] (pool-108-51-200-187.washdc.fios.verizon.net. [108.51.200.187]) by smtp.gmail.com with ESMTPSA id n13sm1982772qtx.68.2021.11.11.09.20.33 for <rfced-future@iab.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 11 Nov 2021 09:20:34 -0800 (PST)
Message-ID: <79d32c80-dd1d-daf4-ae8e-5064a7d41dba@nthpermutation.com>
Date: Thu, 11 Nov 2021 12:20:32 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0
Content-Language: en-US
To: "rfced-future@iab.org" <rfced-future@iab.org>
From: Michael StJohns <msj@nthpermutation.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/LndT5hdXvPZEnJx_HTA3y_lW4Xw>
Subject: [Rfced-future] RFC Principles - long delayed
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: Thu, 11 Nov 2021 17:21:00 -0000
I apologize for the delay in providing the following. This is the aftermath of Stephen's question/comment about heritage and it morphed into a document that attempts to describe current RFC series principles. I've passed this by 1/2dz or so folk and this incorporates their comments. # Principles for the RFC Editor Series The following principles provide some guidance as to the scope of documents that the RSWG may propose and the RSAB may approve. Documents or proposals which suggest modifications of any of the principles shall require additional approvals past that of the RSWG/RSAB, specifically consent from the IAB, IESG and the LLC and such approvals shall be granted only after gaining strong community consensus for such a change. ## Availability The RFC series documents have been freely available digitally for more than 35 years. No change shall be made to the model which would introduce fees for access to any or all of the RFC series documents. Distribution of RFCs shall continue to be subject to the Trust license<<REF: https://trustee.ietf.org/documents/trust-legal-provisions/>>. ## Accessibility There is a general goal to make the RFC series documents as accessible as possible to communities that have special needs - e.g. seeing impaired. Proposals that might negatively impact accessibility shall require the approvals of the IESG, IAB and LLC in addition to that of the RSAB. ## Publication Language The publication language of the series is, and shall remain, English. No action shall be taken which will prohibit the publication of translations of the RFC series in other languages, but the normative content language of an RFC shall remain English. ## Commonality of Purpose The RFC series is the general publication system for information related to the Internet, networking technology, and community discussions on those topics. Neither an expansion nor contraction of that scope is desired. ## Diversity of Interests The RFC series has published thought experiments, speculative ideas, research papers, histories, humor [RFC1149, RFC2549], and even eulogies [RFC2468]. And, more recently, Internet standards. Each of these RFCs and their communities have contributed to the rich history of the RFC series, and to its somewhat human-centric take on networking. If we did not acknowledge this and attempt to conserve the means of such expression we would probably be poorer for it. As the Independent Stream and IRTF Stream are the primary places that non-standards related conversations take place, and with a desire to maintain diversity of interests in the system, neither of these streams may be disestablished except by the approval of the IESG, IAB, LLC Board, and with strong community consensus. The RFC brand shall not be reserved at any time now or in the future solely to apply to a single community of interest i.e., IETF publications. ## Breadth of Expression While the RFC series has its own brand and style, the series is expected to account for individual expression where possible. ## Archival Quality Paraphrasing from the introduction to [RFC8153]: The RFC Editor System provides both publication and archival services for the RFC Series, although there is nothing prohibiting those roles being split apart. In the archival role the main goal is to preserve both the information described and the documents themselves for the indefinite future. To meet both publication and archival needs, the RFC Editor System must find the necessary balance between the publication needs of today and the archival needs of tomorrow, while acknowledging a finite set of resources to complete both aspects of the RFC Editor System functions. As there may be legal implications related to changes in archive policy, changes in the applicability of RFC8153 to the RFC Series, and/or changes to RFC8153 shall require the approvals of the IAB, IESG and LLC in addition to RSAB approval. ## World-class Publication As a world-class publication, quality, readability and accuracy are key to the success of the RFC Series. The publication process is designed in part to enhance those characteristics. Unfortunately, those ideals are sometimes at odds with a desire for an increase in speed of publication. Any RSWG proposals that promote speed at the expense of quality, readability or accuracy shall require the approvals of the IESG, IAB and LLC in addition to that of the RSAB.
- [Rfced-future] RFC Principles - long delayed Michael StJohns
- Re: [Rfced-future] RFC Principles - long delayed Eric Rescorla
- Re: [Rfced-future] RFC Principles - long delayed Joel M. Halpern
- Re: [Rfced-future] RFC Principles - long delayed Brian Rosen
- Re: [Rfced-future] RFC Principles - long delayed Eric Rescorla
- Re: [Rfced-future] RFC Principles - long delayed Adrian Farrel
- Re: [Rfced-future] RFC Principles - long delayed Carsten Bormann
- Re: [Rfced-future] RFC Principles - long delayed John C Klensin
- Re: [Rfced-future] RFC Principles - long delayed Salz, Rich
- Re: [Rfced-future] RFC Principles - long delayed John C Klensin
- Re: [Rfced-future] RFC Principles - long delayed Peter Saint-Andre
- Re: [Rfced-future] RFC Principles - long delayed Tommy Pauly
- Re: [Rfced-future] RFC Principles - long delayed John C Klensin
- Re: [Rfced-future] RFC Principles - long delayed Bob Hinden
- Re: [Rfced-future] RFC Principles - long delayed Stephen Farrell
- Re: [Rfced-future] RFC Principles - long delayed Carsten Bormann
- Re: [Rfced-future] RFC Principles - long delayed Scott Bradner
- Re: [Rfced-future] RFC Principles - long delayed Brian E Carpenter
- Re: [Rfced-future] RFC Principles - long delayed Salz, Rich
- Re: [Rfced-future] RFC Principles - long delayed Stephen Farrell
- Re: [Rfced-future] RFC Principles - long delayed Brian E Carpenter
- Re: [Rfced-future] RFC Principles - long delayed Tommy Pauly
- Re: [Rfced-future] RFC Principles - long delayed Adrian Farrel
- Re: [Rfced-future] RFC Principles - long delayed Jay Daley
- Re: [Rfced-future] RFC Principles - long delayed Christian Huitema
- Re: [Rfced-future] RFC Principles - long delayed Eric Rescorla
- Re: [Rfced-future] RFC Principles - long delayed Eric Rescorla
- Re: [Rfced-future] RFC Principles - long delayed Brian E Carpenter
- Re: [Rfced-future] RFC Principles - long delayed Mark Nottingham
- Re: [Rfced-future] RFC Principles - long delayed Martin Thomson
- Re: [Rfced-future] RFC Principles - long delayed John Levine
- Re: [Rfced-future] RFC Principles - long delayed Brian E Carpenter
- Re: [Rfced-future] RFC Principles - long delayed Adrian Farrel
- Re: [Rfced-future] RFC Principles - long delayed Adrian Farrel
- Re: [Rfced-future] RFC Principles - long delayed Carsten Bormann
- Re: [Rfced-future] RFC Principles - long delayed Eliot Lear
- Re: [Rfced-future] RFC Principles - long delayed John C Klensin
- Re: [Rfced-future] RFC Principles - long delayed John C Klensin
- Re: [Rfced-future] RFC Principles - long delayed Tommy Pauly
- Re: [Rfced-future] RFC Principles - long delayed Christian Huitema
- Re: [Rfced-future] RFC Principles - long delayed John C Klensin
- Re: [Rfced-future] RFC Principles - long delayed Michael StJohns
- Re: [Rfced-future] RFC Principles - long delayed Stephen Farrell
- Re: [Rfced-future] RFC Principles - long delayed Brian E Carpenter
- Re: [Rfced-future] RFC Principles - long delayed Christian Huitema
- Re: [Rfced-future] RFC Principles - long delayed Stephen Farrell
- Re: [Rfced-future] RFC Principles - long delayed Stephen Farrell
- Re: [Rfced-future] RFC Principles - long delayed Brian E Carpenter
- Re: [Rfced-future] RFC Principles - long delayed Stephen Farrell
- Re: [Rfced-future] RFC Principles - long delayed Joel M. Halpern
- Re: [Rfced-future] RFC Principles - long delayed Tommy Pauly
- Re: [Rfced-future] RFC Principles - long delayed John C Klensin
- Re: [Rfced-future] RFC Principles - long delayed Martin J. Dürst
- Re: [Rfced-future] RFC Principles - long delayed Adrian Farrel
- Re: [Rfced-future] RFC Principles - long delayed Stephen Farrell
- Re: [Rfced-future] RFC Principles - long delayed Eliot Lear
- Re: [Rfced-future] RFC Principles - long delayed Adrian Farrel
- Re: [Rfced-future] RFC Principles - long delayed Jay Daley
- Re: [Rfced-future] RFC Principles - long delayed Stephen Farrell
- Re: [Rfced-future] RFC Principles - long delayed Jay Daley
- Re: [Rfced-future] RFC Principles - long delayed Brian E Carpenter
- Re: [Rfced-future] RFC Principles - long delayed Adrian Farrel
- Re: [Rfced-future] RFC Principles - long delayed Carsten Bormann
- Re: [Rfced-future] RFC Principles - long delayed Eric Rescorla
- Re: [Rfced-future] RFC Principles - long delayed Adrian Farrel
- Re: [Rfced-future] RFC Principles - long delayed Eric Rescorla
- Re: [Rfced-future] RFC Principles - long delayed John C Klensin