Network Working Group O. Kolkman, Ed.
Request for Comments: 5620 IAB
Category: Informational August 2009
RFC Editor Model (Version 1)
Abstract
The RFC Editor performs a number of functions that may be carried out
by various persons or entities. The RFC Editor model presented in
this document divides the responsibilities for the RFC Series into
four functions: The RFC Series Editor, the Independent Submission
Editor, the RFC Production Center, and the RFC Publisher. It also
introduces the RFC Series Advisory Group and an (optional)
Independent Submission Stream Editorial Board. The model outlined
here is intended to increase flexibility and operational support
options, provide for the orderly succession of the RFC Editor, and
ensure the continuity of the RFC series, while maintaining RFC
quality and timely processing, ensuring document accessibility,
reducing costs, and increasing cost transparency.
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (c) 2009 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 in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Kolkman & IAB Informational [Page 1]
RFC 5620 RFC Editor Model (Version 1) August 2009
Table of Contents
1. Introduction ....................................................3
2. IAOC Implementation .............................................4
2.1. Expenses for the RFC Editor ................................4
3. RFC Editor Model ................................................5
3.1. RFC Series Editor ..........................................6
3.2. Independent Submission Editor ..............................8
3.3. RFC Production Center ......................................9
3.4. RFC Publisher .............................................11
4. Committees .....................................................11
4.1. RFC Series Advisory Group (RSAG) ..........................11
4.1.1. Charter ............................................11
4.1.2. Membership .........................................12
4.1.3. Disagreements among RFC Editor Entities ............13
4.2. Independent Submission Stream Editorial Board .............14
5. IANA Considerations ............................................14
6. Security Considerations ........................................14
7. Acknowledgments ................................................15
8. References .....................................................16
8.1. Normative References ......................................16
8.2. Informative References.....................................16
Appendix A. 2009 Selection Process ................................17
A.1. Ad Hoc Advisory Committee(s) ..............................17
A.2. The IAB Selection Process of an RFC Series Editor
and/or an Independent Submission Editor ...................17
A.2.1. Nominations and Eligibility ........................17
A.2.2. Committees in 2009 .................................18
A.2.3. Selection ..........................................18
A.2.4. Care of Personal Information........................18
A.2.5. Term of Office and Selection Time Frame ............19
Kolkman & IAB Informational [Page 2]
RFC 5620 RFC Editor Model (Version 1) August 2009
1. Introduction
The IAB, on behalf of the Internet technical community, is concerned
with ensuring the continuity of the RFC Series, orderly RFC Editor
succession, maintaining RFC quality, and RFC document accessibility.
The IAB is also sensitive to the concerns of the IETF Administrative
Oversight Committee (IAOC) about providing the necessary services in
a cost-effective and efficient manner.
The definition of the RFC series is described in RFC 4844 [1].
Section 3.1 of RFC 4844 defines "RFC Editor":
| 3.1. RFC Editor
|
| Originally, there was a single person acting as editor of the RFC
| Series (the RFC Editor). The task has grown, and the work now
| requires the organized activity of several experts, so there are RFC
| Editors, or an RFC Editor organization. In time, there may be
| multiple organizations working together to undertake the work
| required by the RFC Series. For simplicity's sake, and without
| attempting to predict how the role might be subdivided among them,
| this document refers to this collection of experts and organizations
| as the "RFC Editor".
|
| The RFC Editor is an expert technical editor and series editor,
| acting to support the mission of the RFC Series. As such, the RFC
| Editor is the implementer handling the editorial management of the
| RFC Series, in accordance with the defined processes. In addition,
| the RFC Editor is expected to be the expert and prime mover in
| discussions about policies for editing, publishing, and archiving
| RFCs.
RFC 4844 makes no attempt to explore the internal organization of the
RFC Editor. However, RFC 4844 envisions changes in the RFC Editor
organizational structure. In discussion with the Internet community,
the IAB considered changes that increase flexibility and operational
support options, provide for the orderly succession of the RFC
Editor, and ensure the continuity of the RFC series, while
maintaining RFC quality and timely processing, ensuring document
accessibility, reducing costs, and increasing cost transparency. The
model set forth below is the result of those discussions, and
examines the internal organization of the RFC Editor, while remaining
consistent with RFC 4844.
Kolkman & IAB Informational [Page 3]
RFC 5620 RFC Editor Model (Version 1) August 2009
Note that RFC 4844 uses the term "RFC Editor function" or "RFC
Editor" as the collective set of responsibilities for which this memo
provides a model for internal organization. This memo introduces the
term "RFC Series Editor" or "Series Editor" for one of the
organizational components.
While the IAB approved the initial version of this RFC Editor model
on October 1, 2008, the model has received clarifications since. It
should be noted that the publication of the document as an RFC does
not cast the model in stone, as the primary purpose of this document,
throughout the publication process, is to encourage normal community
review in order to ascertain consensus to work to this model as a
first step. The document, and the resulting structures, will be
modified as needed through normal procedures. The IAB will continue
to monitor discussions within the community about potential
adjustments to the RFC Editor model and recognizes that the process
described in this document may need to be adjusted to align with any
changes that result from such discussions, hence the version number
in the title.
In particular, the document will be reviewed after the various
transition periods and mechanisms specified in this version are
completed.
2. IAOC Implementation
The model is constructed in such a way that it allows for all these
functions to be implemented jointly or under separate contractual
arrangements. In fact, a bidder could put together a proposal that
includes one or more subcontractors. The reporting structure will
depend on the manner that the contracts are awarded, and they are
subject to change over time. As a result, the model describes only
responsibilities, procedures, and process. The exact implementation
is a responsibility of the IAOC.
2.1. Expenses for the RFC Editor
The expenses discussed in this document are not new expenses. They
are part of the IASA budget. Today, these expenses are part of the
RFC Editor contract with the University of Southern California's
Information Sciences Institute.
Kolkman & IAB Informational [Page 4]
RFC 5620 RFC Editor Model (Version 1) August 2009
3. RFC Editor Model
The RFC Editor model divides the responsibilities for the RFC Series
into the following components:
o RFC Series Editor ("RSE").
o Independent Submission Editor ("ISE").
o RFC Production Center.
o RFC Publisher.
The RFC Series production and process under this structure is
schematically represented by the figure below. (The figure does not
depict oversight and escalation relations.)
------ ----- ------ ---------
Stream | | | | | | |Community|
Pro- | IETF | | IAB | | IRTF | | at |
ducers | | | | | | | Large |
--^--- --^-- ---^-- ----^----
| | | |
| | | | -------
| | | | | Indep.|
--v--- ---v--- ---v-- ----v------ | Stream|
Stream | | | | | | |Independent| | Edi- |
Appro- | IESG | | IAB | | IRSG | |Submission |.....| torial|
vers | | | | | | | Editor | | Board |
----^- ---^--- ----^--- ----^------ -------
| | | |
| | | | -------
| | | | | RFC |
------ --v--------v----------v-----------v----- | Series|
| | | | | Adv. |
| IANA | <->| RFC Production Center <---. | Group |
| | | | | -------
------ -----------------^---------------------- | |
| | |
| ------v-------
------v--------- | |
| | | RFC Series |
| RFC Publisher |<------->| Editor |
| | | |
---------------- --------------
Figure 1: Ordinary RFC Series production and process
Kolkman & IAB Informational [Page 5]
RFC 5620 RFC Editor Model (Version 1) August 2009
In this model, documents are produced and approved through multiple
document streams. The four that now exist are described in [