The RFC Series and RFC Editor
RFC 8729

Document Type RFC - Informational (February 2020; No errata)
Obsoletes RFC 4844
Last updated 2020-03-09
Stream IAB
Formats plain text html xml pdf htmlized bibtex
Stream IAB state Published RFC
Consensus Boilerplate Yes
RFC Editor Note (None)


Internet Architecture Board (IAB)                        R. Housley, Ed.
Request for Comments: 8729                                              
Obsoletes: 4844                                           L. Daigle, Ed.
Category: Informational                                    February 2020
ISSN: 2070-1721

                     The RFC Series and RFC Editor

Abstract

   This document describes the framework for an RFC Series and an RFC
   Editor function that incorporate the principles of organized
   community involvement and accountability that has become necessary as
   the Internet technical community has grown, thereby enabling the RFC
   Series to continue to fulfill its mandate.  This document obsoletes
   RFC 4844.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Architecture Board (IAB)
   and represents information that the IAB has deemed valuable to
   provide for permanent record.  It represents the consensus of the
   Internet Architecture Board (IAB).  Documents approved for
   publication by the IAB are not candidates for any level of Internet
   Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8729.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.

Table of Contents

   1.  Introduction
   2.  RFC Series Mission
   3.  Roles and Responsibilities
     3.1.  RFC Editor
     3.2.  IAB
     3.3.  Operational Oversight
     3.4.  Policy Oversight
   4.  Framework
     4.1.  Document Approval
       4.1.1.  Definition
       4.1.2.  Operational Implementation
       4.1.3.  Process Change
       4.1.4.  Existing Approval Process Documents
     4.2.  Editing, Processing, and Publication of Documents
       4.2.1.  Definition
       4.2.2.  Operational Implementation
       4.2.3.  Process Change
       4.2.4.  Existing Process Documents
     4.3.  Archiving, Indexing, and Accessibility
       4.3.1.  Definition
       4.3.2.  Operational Implementation
       4.3.3.  Process Change
       4.3.4.  Existing Process Documents
     4.4.  Series-Wide Guidelines and Rules
       4.4.1.  Definition
       4.4.2.  Operational Implementation
       4.4.3.  Process Change
       4.4.4.  Existing Process Documents
   5.  RFC Streams
     5.1.  RFC Approval Processes
       5.1.1.  IETF Document Stream
       5.1.2.  IAB Document Stream
       5.1.3.  IRTF Document Stream
       5.1.4.  Independent Submission Stream
     5.2.  RFC Technical Publication Requirements
       5.2.1.  IETF Documents
       5.2.2.  IAB Documents
       5.2.3.  IRTF Documents
       5.2.4.  Independent Submissions
   6.  Security Considerations
   7.  Changes Since RFC 4844
   8.  Informative References
   Appendix A.  A Retrospective of IAB Charters and RFC Editor
     A.1.  1992
     A.2.  1994
     A.3.  2000
   IAB Members at the Time of Approval
   Authors' Addresses

1.  Introduction

   The first Request for Comments (RFC) document was published in April
   of 1969 as part of the effort to design and build what we now know of
   as the Internet.  Since then, the RFC Series has been the archival
   series dedicated to documenting Internet technical specifications,
   including both general contributions from the Internet research and
   engineering community as well as standards documents.

   As described in the history of the first 30 years of RFCs
   ([RFC2555]), the RFC Series was created for the purpose of capturing
   the research and engineering thought that underlie the design of
   (what we now know of as) the Internet.  As the Internet Engineering
   Task Force (IETF) was formalized to carry out the discussion and
   documentation of Internet standards, IETF documents have become a
   large part (but not the entirety) of the RFC Series.

   As the IETF has grown up and celebrated its own 30 years of history,
   its requirements for archival publication of its output have changed
   and become more rigorous.  Perhaps most significantly, the IETF must
   be able to define (based on its own open consensus discussion
   processes and leadership directions) and implement adjustments to its
   publication processes.

   At the same time, the Internet engineering and research community as
   a whole has grown and come to require more openness and
   accountability in all organizations supporting it.  More than ever,
   this community needs an RFC Series that is supported (operationally
Show full document text