Changes to the RFC Series and RSE
draft-brownlee-rfc-series-and-rse-changes-01

Document Type Active Internet-Draft (individual)
Last updated 2020-06-25
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)
Network Working Group                                     J. N. Brownlee
Internet-Draft                                                U Auckland
Intended status: Informational                              26 June 2020
Expires: 28 December 2020

                   Changes to the RFC Series and RSE
              draft-brownlee-rfc-series-and-rse-changes-01

Abstract

   This document discusses the impact of changes to the RFC Series on
   the RFC Production Centre, the need for the RFC Series Editor to be
   independent of the Series Input Streams (the I* groups), and a
   suggested Editorial Board for the Series Editor.

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/.

   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 28 December 2020.

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.

Brownlee                Expires 28 December 2020                [Page 1]
Internet-Draft             RFC Series Changes                  June 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  RSE Responsibilities  . . . . . . . . . . . . . . . . . . . .   2
   3.  Changes to the RFC Series . . . . . . . . . . . . . . . . . .   3
   4.  Support for the RSE . . . . . . . . . . . . . . . . . . . . .   3
   5.  Independence of the RSE . . . . . . . . . . . . . . . . . . .   5
   6.  Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   Appendix A.  Change log [RFC Editor: Please remove.]  . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Over the last few weeks the rfced-future mailing list has discussed
   topics such as:

   *  What are the responsibilities of the RFC Series Editor?

   *  How should changes to the RFC Series be handled?

   *  Where does the RFC Series Editor (RSE) fit, relative to the RFC
      input Streams, i.e. the IAB, IESG, IRTF and Independent
      Submissions Editor (ISE)?

   *  What does _independent_ mean for the RSE?

   *  How could the RSE be effectively supported?

   This draft addresses those topics in a little more detail.

   The history of our "new formats" in Section 3 of this draft comes
   from my own experiences on their Design Team.  I present them here
   because I feel that many IETF participants have not considered just
   how much work is required to make changes to the RFC Series.
   Otherwise, opinions expressed in this draft are purely my own.

2.  RSE Responsibilities

   RFC Series Editor Responsibilities are clearly set out in [RFC8729],
   "The RFC Series and RFC Editor", February 2020.

   These responsibilities have been discussed extensively on the *rfced-
   future@iab.org* mailing list.  I believe that they do not need to be
   further discussed at this time.

Brownlee                Expires 28 December 2020                [Page 2]
Internet-Draft             RFC Series Changes                  June 2020

3.  Changes to the RFC Series

   Our last RSE was appointed (and contracted directly by ISOC) in 2011.
   Her first few years were busy:

   *  About one year to get up to speed with the RFC Production Centre
      (RPC).

   *  Two years and three BOFs to come up with [RFC6949], "RFC Series
      Format Requirements," May _2013_.

   *  Another three years for a large design team (at least 8 members)
      to produce [RFC7990], "RFC Format Framework", December _2016_,
      [RFC7991], "The _'xml2rfc'_ Version 3 Vocabulary", and RFCs 7992
Show full document text