The University of Auckland

n.brownlee@auckland.ac.nz

iab@iab.org

Check Point Software

959 Skyway Road San Carlos CA 94070 USA bob.hinden@gmail.com

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 (RSE). 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 (ISE). This document is a derivative of , Section 3.2, and was separated out from . This document obsoletes in combination with .

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.

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 .

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 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. Therefore, the IAOC should include these costs in the IASA budget.

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.

This document has no specific security implications, however the same security considerations as those in and apply.

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.

This document describes the framework for an RFC Series and an RFC Editor function that incorporate the principles of organized community involvement and accountability that has become necessary as the Internet technical community has grown, thereby enabling the RFC Series to continue to fulfill its mandate. This memo provides information for the Internet community. 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.