Network Working Group N. Brownlee, Ed.
Internet-Draft The University of Auckland
Obsoletes: 6548 (if approved) R. Hinden, Ed.
Intended status: Informational Check Point Software
Expires: July 11, 2019 January 7, 2019

Independent Submission Editor Model


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 IASA and related structures with those defined by the IASA 2.0 Model.

[RFC Editor: Please remove the following paragraph prior to publication.]

The IASA2 WG requests that the IAB publish this replacement for RFC 6548.

Status of This Memo

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

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 July 11, 2019.

Copyright Notice

Copyright (c) 2019 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. 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.

Table of Contents

1. Introduction

The RFC Editor Model [I-D.ietf-iasa2-rfc6635bis] 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 [RFC5620], Section 3.2, and was separated out from [RFC6635].

This document updates the Independent Submission Editor Model to be aligned with IASA 2.0 Model [I-D.ietf-iasa2-rfc4071bis] that creates a IETF Administration Limited Liability Company ("LLC") managed by a board of directors ("LLC Board"). This document obsoletes [RFC6548].

2. Independent Submission Editor

The ISE is an individual who is responsible for the Independent Submission stream of RFCs, as defined by [RFC4844]. 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 [I-D.ietf-iasa2-rfc6635bis]). As noted below, the ISE is appointed by and is responsible directly to the IAB.

2.1. Qualifications

The ISE is a senior position for which the following qualifications are desired:

  1. 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.
  2. Thorough familiarity with the RFC series.
  3. 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 Section 3).
  4. Good standing in the technical community, in and beyond the IETF.
  5. 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.
  6. The ability to work effectively in a multi-actor environment with divided authority and responsibility similar to that described in [RFC6635].

2.2. Responsibilities

The ISE is an individual who may have assistants and who is responsible for:

  1. Maintaining technical quality of the Independent Submission stream.
  2. Reviewing, approving, and processing Independent Submissions.
  3. Forwarding draft RFCs in the Independent Submission stream to the RFC Production Center.
  4. Defining and developing the scope of the Independent Submission stream as a part of the overall RFC Editor function [RFC6635].
  5. Reviewing and approving RFC errata for Independent Submissions.
  6. Coordinating work and conforming to general RFC Series policies as specified by the IAB and RSE.
  7. 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.

3. 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.

4. Security Considerations

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

5. IAB Members at the Time of Approval

The IAB members at the time of approval of [RFC6548] were: Bernard Aboba, Ross Callon, Alissa Cooper, Joel Halpern, Spencer Dawkins, Russ Housley, David Kessens, Olaf Kolkman, Danny McPherson, Jon Peterson, Andrei Robachevsky, Dave Thaler, and Hannes Tschofenig.

The IAB members at the time of approval of this document were: Jari Arrko, Alissa Cooper, Ted Hardie, Christian Heuitema, Gabriel Montenegro, Erik Nordmark, Mark Nottingham, Melina Shore, Robert Sparks, Jeff Tantsura, Martin Thomson, Brian Trammell, and Suzanne Woolf.

6. Acknowledgements

Generous thanks to Joel Hapern for all his help with this document, and for all his work on [RFC6635]). Thanks also to the IAB members, whose comments and suggestions were both welcome and useful.

Bob Hinden served as documented editor for this version of this document that aligned it with the IASA 2.0 model.

7. References

7.1. Normative References

[I-D.ietf-iasa2-rfc4071bis] Haberman, B., Hall, J. and J. Livingood, "Structure of the IETF Administrative Support Activity, Version 2.0", Internet-Draft draft-ietf-iasa2-rfc4071bis-03, December 2018.
[I-D.ietf-iasa2-rfc6635bis] Kolkman, O., Halpern, J. and R. Hinden, "RFC Editor Model (Version 2)", Internet-Draft draft-ietf-iasa2-rfc6635bis-02, January 2019.
[RFC4844] Daigle, L. and Internet Architecture Board, "The RFC Series and RFC Editor", RFC 4844, DOI 10.17487/RFC4844, July 2007.
[RFC4846] Klensin, J. and D. Thaler, "Independent Submissions to the RFC Editor", RFC 4846, DOI 10.17487/RFC4846, July 2007.
[RFC6548] Brownlee, N. and IAB, "Independent Submission Editor Model", RFC 6548, DOI 10.17487/RFC6548, June 2012.

7.2. Informative References

[RFC5620] Kolkman, O. and IAB, "RFC Editor Model (Version 1)", RFC 5620, DOI 10.17487/RFC5620, August 2009.
[RFC6635] Kolkman, O., Halpern, J. and IAB, "RFC Editor Model (Version 2)", RFC 6635, DOI 10.17487/RFC6635, June 2012.

Appendix A. Change log [RFC Editor: Please remove]

Authors' Addresses

Nevil Brownlee (editor) The University of Auckland EMail:
Robert M. Hinden (editor) Check Point Software 959 Skyway Road San Carlos, CA 94070 USA EMail: