Independent Submission Editor ModelThe University of Aucklandn.brownlee@auckland.ac.nzCheck Point Software959 Skyway RoadSan CarlosCA94070USAbob.hinden@gmail.comISEIASARSELLCIAB
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 (RSE).
The ISE is appointed by the IAB, and also interacts
with the
IETF Administration Limited Liability Company (LLC).This version obsoletes RFC 6548 to replace all references to the
Internet Administrative Support Activity (IASA) and related structures with those defined by the IASA 2.0
structure.Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Architecture Board
(IAB) and represents information that the IAB has deemed valuable
to provide for permanent record. It represents the consensus of the Internet
Architecture Board (IAB). Documents approved for publication
by the IAB are not candidates for any level of Internet Standard; see
Section 2 of RFC 7841.
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
.
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
() 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.
Table of Contents
. Introduction
. Independent Submission Editor
. Qualifications
. Responsibilities
. Independent Submission Editorial Board
. Security Considerations
. References
. Normative References
. Informative References
IAB Members at the Time of Approval
Acknowledgements
Authors' Addresses
Introduction
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 (ISE).
The previous version of this
document is a derivative of
,
and was separated out from .
This document updates the Independent Submission Editor Model to
align it with the IASA 2.0 structure
that creates the IETF Administration Limited Liability Company
("LLC") managed by a board of directors ("LLC Board").
This document obsoletes .
Independent Submission Editor
The ISE is
an individual who is responsible for the
Independent Submission stream of RFCs, as defined by
.
The Independent Submission stream and the
ISE are not under the authority or
direction of the RSE or the RFC Series Oversight Committee (RSOC)
(see ).
As noted below, the ISE is appointed by and is responsible
directly to the IAB.
Qualifications
The ISE 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
.
Responsibilities
The ISE 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 RFC errata for Independent Submissions.
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 LLC.
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.
While the ISE itself is considered a volunteer function, the
IAB considers maintaining the Independent Submission stream
part of the IAB's supported activities. Therefore, the LLC
should include these costs in the IASA budget.
Independent Submission Editorial Board
The ISE is supported by an Editorial
Board for the review of Independent Submission stream documents.
This board is known as the Independent Submission 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.
Security Considerations
This document has no specific security implications, however the
same security considerations as those in
and apply.
ReferencesNormative ReferencesIndependent Submissions to the RFC EditorThere is a long-standing tradition in the Internet community, predating the Internet Engineering Task Force (IETF) by many years, of use of the RFC Series to publish materials that are not rooted in the IETF standards process and its review and approval mechanisms. These documents, known as "Independent Submissions", serve a number of important functions for the Internet community, both inside and outside of the community of active IETF participants. This document discusses the Independent Submission model and some reasons why it is important. It then describes editorial and processing norms that can be used for Independent Submissions as the community goes forward into new relationships between the IETF community and its primary technical publisher. This memo provides information for the Internet community.Independent Submission Editor ModelIABThis 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 (RSE). The ISE is appointed by the IAB, and also interacts with the IETF Administrative Oversight Committee (IAOC). This document is not an Internet Standards Track specification; it is published for informational purposes.Structure of the IETF Administrative Support Activity, Version 2.0RFC Editor Model (Version 2)The RFC Series and RFC EditorInformative ReferencesRFC Editor Model (Version 1)IABThe 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. This memo provides information for the Internet community.RFC Editor Model (Version 2)IABThe 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. Internet Architecture Board (IAB) oversight via 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 RFC 5620, and obsoletes that document. This document is not an Internet Standards Track specification; it is published for informational purposes.IAB Members at the Time of Approval The IAB members at the time of approval of
were: , , ,
, ,
, ,
, , , , , and .
The IAB members at the time of approval of this document (RFC 8730) were:
, , , , ,
, ,
, ,
, ,
, and .
Acknowledgements
Generous thanks to 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.
served as document editor for this RFC to
align it with the IASA 2.0 structure.Authors' AddressesThe University of Aucklandn.brownlee@auckland.ac.nzCheck Point Software959 Skyway RoadSan CarlosCA94070USAbob.hinden@gmail.com