Independent Submission Editor Model
The University of Auckland
n.brownlee@auckland.ac.nz
iab@iab.org
RFC
This document describes the function and responsibilities
of the RFC Independent Submission Editor (ISE).
The Independent Submission Stream is one of the Stream Producers
that create draft RFCs,
with the ISE as its Stream Approver.
The ISE is overall responsible for activities within
the Independent Submission Stream, working with draft editors and
reviewers, and interacts with the RFC Production Center
and Publisher, and the RFC Series Editor.
The ISE is appointed by the IAB, and also interacts
with the IETF Administrative Oversight Committee (IAOC).
The RFC Editor Model
defines a set of Streams that produce draft RFCs, which are
submitted for publication. This document defines the management
function for the Independent Submission stream, specifically the
role of Independent Submission Editor. This document is a derivative
of section 3.2, and was separated out
from .
This document obsoletes .
The Independent Submission Editor (ISE) is
an individual who is responsible for the
Independent Submission stream of RFCs, as defined by
.
The Independent Submission stream and the
Independent Submission Editor are not under the authority or
direction of the RSE or the RFC Series Oversight Committee (RSOC).
As noted below, the ISE is appointed by and is responsible
directly to the IAB.
The Independent Submission Editor is a senior position for
which the following qualifications are desired:
Technical competence, i.e., broad technical experience
and perspective across a wide range of Internet
technologies and applications, and also the
ability to work effectively with portions of that spectrum
in which they have no personal expertise.
Thorough familiarity with the RFC series.
An ability to define and constitute advisory and
document review arrangements. If those arrangements
include an Editorial Board similar to the current one or
some equivalent arrangement, the ability to assess the
technical competence of potential Editorial Board members
(see ).
Good standing in the technical community, in and beyond
the IETF.
Demonstrated editorial skills, good command of the
English language, and demonstrated history of being able
to work effectively with technical documents and materials
created by others.
The ability to work effectively in a multi-actor
environment with divided authority and responsibility
similar to that described in
.
The Independent Submission Editor is an individual who may
have assistants and who is responsible for:
Maintaining technical quality of the Independent Submission
stream.
Reviewing, approving, and processing Independent Submissions.
Forwarding draft RFCs in the Independent Submission stream
to the RFC Production Center.
Defining and developing the scope of the Independent Submission
stream as a part of the overall RFC editor function
.
Reviewing and approving Independent Submissions RFC errata.
Coordinating work and conforming to general RFC Series
policies as specified by the IAB and RSE.
Providing statistics and documentation as requested by the
RSE and/or IAOC.
The ISE may choose to select individuals to participate in
an Advisory Board for assistance in special topics as the
ISE deems appropriate. Such an Advisory Board exists
at the pleasure of the ISE, and its members serve at the
pleasure of the ISE.
The individual with the listed qualifications is
selected by the IAB after input has been collected from the
community. An approach similar to the one used by the IAB
to select an IAOC member every other year as described in
should be used.
While the ISE itself is considered a volunteer function, the
IAB considers maintaining the Independent Submission stream
part of the IAB's supported activities, and that the IAOC
should include these costs in the IASA budget.
The Independent Submission Editor is supported by an Editorial
Board for the review of Independent Submission stream documents.
This board is known as the Independent Submission Stream Editorial
Board. This volunteer Editorial Board exists at the pleasure of
the ISE, and its members
serve at the pleasure of the ISE. The existence of this board is
simply noted within this model, and additional discussion of
such is considered out of scope of this document.
This document does not create a new registry nor does it register any
values in existing registries; no IANA action is required.
Bernard Aboba, Ross Callon, Alissa Cooper, Joel Halpern,
Spencer Dawkins, Russ Housley, David Kessens, Olaf Kolkman,
Danny McPherson, Jon Peterson, Andrei Robachevsky, Dave Thaler,
Hannes Tschofenig.
Generous thanks to Joel Hapern for all his help with this document,
and for all his work on ).
Thanks also to the IAB members, whose comments and suggestions
were both welcome and useful.
Made changes suggested by SM and Olaf Kolkman.
Added 'defining/developing scope of Independent
Submission Stream,'
suggested by Brian Carpenter.
Made changes suggested in IAB tickets #87, #92, #94
and #103.
Changed/simplified description of ISE's Advisory Board.
Made changes suggested by IAB ticket #105.
Made changes from discussion on rfc-interest list:
Expanded RSOC on first use, deleted comment on
responsibility of other streams.
Following Bob Braden's suggestion, deleted
"or team"
from section 2.2.
Made changes suggested by Trac tickets 115 and 116.
Made one further change suggested by Trac ticket 115.
Added 'IAB Members at approval' and 'Acknowledgements'
sections, as requested by Trac ticket 114.