A Proposed Model for RFC Editing and Publication
draft-thomson-rfced-model-01

Document Type Active Internet-Draft (individual)
Last updated 2020-08-09
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
rfced-future                                                  M. Thomson
Internet-Draft                                                   Mozilla
Updates: 4844, 6635 (if approved)                         10 August 2020
Intended status: Informational                                          
Expires: 11 February 2021

            A Proposed Model for RFC Editing and Publication
                      draft-thomson-rfced-model-01

Abstract

   The finishing process for a document that is approved for publication
   as an RFC currently involves a somewhat detailed and lengthy process.
   The system that executes that process involves a number of different
   actors, each bringing competency with different aspects of the
   overall process.  Ensuring that this process functions smoothly is
   critical to the mission of the organizations that publish documents
   in the RFC series.

   This document proposes a framework for that system that aims to
   provide clear delineations of accountability and responsibility for
   each of the actors in this system.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Discussion of this document takes place on the RFC Editor Futures
   program mailing list (rfced-future@iab.org), which is archived at
   https://mailarchive.ietf.org/arch/browse/rfced-future/
   (https://mailarchive.ietf.org/arch/browse/rfced-future/).

   Source for this draft and an issue tracker can be found at
   https://github.com/martinthomson/rfced-model
   (https://github.com/martinthomson/rfced-model).

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

Thomson                 Expires 11 February 2021                [Page 1]
Internet-Draft              RFC Editor Model                 August 2020

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 11 February 2021.

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.  Code Components
   extracted from this document must include Simplified BSD License text
   as described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   3
   3.  Abstract Model  . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Funding and Oversight . . . . . . . . . . . . . . . . . . . .   4
     4.1.  IETF LLC Delegation of Oversight Function . . . . . . . .   5
   5.  Evolution and Setting Policies  . . . . . . . . . . . . . . .   6
     5.1.  Individual Interactions . . . . . . . . . . . . . . . . .   8
     5.2.  The Needs of Different Streams  . . . . . . . . . . . . .   8
     5.3.  Style Guide . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  Tooling . . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   7.  Management of Individual Functions  . . . . . . . . . . . . .  11
   8.  Other Involved Entities . . . . . . . . . . . . . . . . . . .  12
   9.  Changes from Version 2  . . . . . . . . . . . . . . . . . . .  12
     9.1.  No RFC Series Editor  . . . . . . . . . . . . . . . . . .  12
     9.2.  Preserved Aspects of Current Practice . . . . . . . . . .  13
     9.3.  Motivating Principles . . . . . . . . . . . . . . . . . .  13
   10. Documentation Requirements  . . . . . . . . . . . . . . . . .  14
   11. Errors and Omissions  . . . . . . . . . . . . . . . . . . . .  14
   12. Security Considerations . . . . . . . . . . . . . . . . . . .  14
   13. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   14. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     14.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     14.2.  Informative References . . . . . . . . . . . . . . . . .  15
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  16
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  16

Thomson                 Expires 11 February 2021                [Page 2]
Show full document text