RFC Editor Model (Version 2)
draft-iab-rfc-editor-model-v2-04

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-03-12
Stream IAB
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
Stream IAB state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
Network Working Group                                   O. Kolkman (Ed.)
Internet-Draft
Obsoletes: 5620 (if approved)                           J. Halpern (Ed.)
Intended status: Informational                                  Ericsson
Expires: September 13, 2012                                          IAB
                                                          March 12, 2012

                      RFC Editor Model (Version 2)
                    draft-iab-rfc-editor-model-v2-04

Abstract

   The RFC Editor performs a number of functions that may be carried out
   by various people or entities.  The RFC Editor model described in
   this document divides the responsibilities for the RFC Series into
   three functions: The RFC Series Editor, the RFC Production Center,
   and the RFC Publisher.  The Internet Architecture Board (IAB)
   oversight by way of delegation to the RFC Series Oversight Committee
   (RSOC) is described, as is the relationship between the IETF
   Administrative Oversight Committee (IAOC) and the RSOC.  This
   document reflects the experience gained with RFC Editor Model version
   1, documented in [RFC5620] and obsoletes that document.

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 http://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 September 13, 2012.

Copyright Notice

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

Kolkman (Ed.), et al.  Expires September 13, 2012               [Page 1]
Internet-Draft        RFC Editor Model (Version 2)            March 2012

   (http://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.  RFC Editor Model . . . . . . . . . . . . . . . . . . . . . . .  4
     2.1.  RFC Series Editor  . . . . . . . . . . . . . . . . . . . .  7
       2.1.1.  Strategic Leadership and Management of the
               Publication and Production Functions . . . . . . . . .  8
       2.1.2.  Representation of the RFC Series . . . . . . . . . . .  8
         2.1.2.1.  Representation to the IETF . . . . . . . . . . . .  8
         2.1.2.2.  External Representation  . . . . . . . . . . . . .  9
       2.1.3.  Development of RFC Production and Publication  . . . . 10
       2.1.4.  Development of the RFC Series  . . . . . . . . . . . . 10
       2.1.5.  Workload . . . . . . . . . . . . . . . . . . . . . . . 11
       2.1.6.  Qualifications . . . . . . . . . . . . . . . . . . . . 11
       2.1.7.  Conflict of Interest . . . . . . . . . . . . . . . . . 12
     2.2.  RFC Production Center  . . . . . . . . . . . . . . . . . . 12
     2.3.  RFC Publisher  . . . . . . . . . . . . . . . . . . . . . . 13
   3.  Committees . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     3.1.  RFC Series Oversight Committee (RSOC)  . . . . . . . . . . 13
       3.1.1.  RSOC Composition . . . . . . . . . . . . . . . . . . . 15
   4.  Administrative Implementation  . . . . . . . . . . . . . . . . 15
     4.1.  Vendor Selection for the Production and Publisher
           Functions  . . . . . . . . . . . . . . . . . . . . . . . . 16
     4.2.  Budget . . . . . . . . . . . . . . . . . . . . . . . . . . 17
     4.3.  Disagreements Among RFC Editor Related Entities  . . . . . 18
     4.4.  Issues with Contractual Impact . . . . . . . . . . . . . . 19
   5.  IANA considerations  . . . . . . . . . . . . . . . . . . . . . 19
   6.  Security considerations  . . . . . . . . . . . . . . . . . . . 19
   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 20
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 20
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 21

Kolkman (Ed.), et al.  Expires September 13, 2012               [Page 2]
Show full document text