Network Working Group | N. Brownlee (Ed.) |
Internet-Draft | The University of Auckland |
Intended status: Informational | IAB |
Expires: March 29, 2012 | September 26, 2011 |
Independent Submission Editor Model
draft-iab-ise-model-00
This document describes the function and responsibilities of the Independent Stream Editor (ISE). The Independent Stream is one of the Stream Producers, with the ISE as its Stream Approver. The ISE is overall responsible for activities within the Independent Stream, working with draft editors and reviewers, and interacts with the RFC Production Centre and Publisher, and the RFC Series Editor. The ISE is appointed by the IAB, and also interacts with the IETF Administrative Oversight Committee (IAOC).
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 March 29, 2012.
Copyright (c) 2011 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 (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.
The Independent Submissions Editor roles and responsibilities were documented in "RFC Editor Model (version 1)" [RFC5620]. In the light of experience, we see that having it there gave rise to some confusion as to where and how the ISE fits into the RFC Editor model. To reduce that confusion, the ISE material has been moved into this document.
The Independent Submission Editor (ISE) is the head of the Independent Submission Stream of RFCs, as defined by [RFC4844]. The Independent Stream and the Independent Submission Editor are not under the authority or direction of the RSE. 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:
The Independent Submission Editor is an individual who may have assistants and who is responsible for:
The Independent Submission Editor may seek support from an advisory board (see [RFC4846]) and may form a team to perform the activities needed to fulfill their responsibilities. The individual with the listed qualifications will be selected by the IAB after input is 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 [RFC4333] 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 will include the expenses made for the support of the ISE in its IASA-supported 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 the 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, and no IANA action is required.
This document has no specific security implications.
[RFC4846] | Klensin, J. and D. Thaler, "Independent Submissions to the RFC Editor", RFC 4846, July 2007. |
[I-D.iab-rfc-editor-model-v2] | Kolkman, O, Halpern, J and T IAB, "RFC Editor Model (Version 2)", Internet-Draft draft-iab-rfc-editor-model-v2-02, June 2011. |
[RFC4844] | Daigle, L., Internet Architecture Board, "The RFC Series and RFC Editor", RFC 4844, July 2007. |
[RFC4333] | Huston, G. and B. Wijnen, "The IETF Administrative Oversight Committee (IAOC) Member Selection Guidelines and Process", BCP 113, RFC 4333, December 2005. |
[RFC5620] | Kolkman, O., IAB, "RFC Editor Model (Version 1)", RFC 5620, August 2009. |