RFC Series Model Process
draft-flanagan-rseme-03

Document Type Active Internet-Draft (individual)
Last updated 2019-11-19
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf 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                                        H. Flanagan
Internet-Draft                                                RFC Editor
Intended status: Informational                          20 November 2019
Expires: 23 May 2020

                        RFC Series Model Process
                        draft-flanagan-rseme-03

Abstract

   The RFC Series has come to a crossroads where questions must be
   answered regarding how the Series should be managed, the role of the
   RFC Series Editor, and the oversight of the RFC Editor function.
   This draft offers a proposal to form a new IAB program called the RFC
   Editor Future Development Program.  This proposal is based on the
   discussions held during three virtual meetings in September and
   October 2019, as well as the RSEME session at IETF 106, and requests
   a new, open IAB program that will drive consensus around any changes
   to the RFC Editor model.  The program will require extensive
   community engagement and outreach to a broad set of stakeholder
   communities.

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 23 May 2020.

Copyright Notice

   Copyright (c) 2019 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.

Flanagan                   Expires 23 May 2020                  [Page 1]
Internet-Draft          RFC Series Model Process           November 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Summaries from Virtual Meetings and IETF 106  . . . . . . . .   2
     2.1.  First Virtual Meeting Summary . . . . . . . . . . . . . .   3
     2.2.  Second Virtual Meeting Summary  . . . . . . . . . . . . .   3
     2.3.  Third Virtual Meeting Summary . . . . . . . . . . . . . .   4
     2.4.  RSEME session at IETF 106 . . . . . . . . . . . . . . . .   4
   3.  Proposal - RFC Editor Future Development Program  . . . . . .   4
   4.  Timeline  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Informative References  . . . . . . . . . . . . . . . . . . .   6
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The RFC Series has come to a crossroads where questions must be
   answered regarding how the Series should be managed, the role of the
   RFC Series Editor, and the oversight of the RFC Editor function.  The
   RFC Editor, editor and publisher of the Series, publishes RFCs for
   the IETF, the IRTF, the IAB, and the Independent Submissions streams.
   Those RFCs are referred to by other Standards Development
   Organizations (SDOs) and the users of their documents, by
   organizations and governments in their procurement processes, by
   academics, by network operators, and more.  Decisions on the future
   of the RFC Editor and the RFC Series must include input from, and
   reflect considerations of the needs and uses of, both the producers
   and the consumers of RFCs.

2.  Summaries from Virtual Meetings and IETF 106

   Three virtual meetings were organized, scheduled to be sensitive to a
   wide range of time zones, to discuss the process by which the
   communities of interest can determine consensus on the RFC Series
   model.  These meetings were coordinated by Heather Flanagan, RFC
   Series Editor, and explicit invitations were sent to:

   *  IETF, IRTF, IAB, and Independent Submission authors and
      participants via various mailing lists, including the rfc-
      interest, ietf-announce, and wgchairs mailing lists

   *  IETF liaison contacts [IETF-LIAISONS]

Flanagan                   Expires 23 May 2020                  [Page 2]
Internet-Draft          RFC Series Model Process           November 2019
Show full document text