RFC 6548

RFC 6548: Independent Submission Editor Model 💖

okay bestie, let's get into it 🎀. This is RFC 6548, titled Independent Submission Editor Model, published in June 2012 as Informational (ISSN 2070-1721). It's from the Internet Architecture Board (IAB), edited by N. Brownlee, Ed. from The University of Auckland. It obsoletes RFC 5620 (only together with RFC 6635) 🦋. The header doesn't list anything it updates.

Abstract ✨

okay so this doc explains the job of the RFC Independent Submission Editor (ISE) 💅. The Independent Submission stream is one of the streams that make draft RFCs, and the ISE is its stream approver 👑. The ISE is basically in charge of everything happening in that stream. They work with draft editors and reviewers, and they deal with the RFC Production Center, the Publisher, and the RFC Series Editor (RSE) 🧚. The IAB appoints the ISE, and they also talk to the IETF Administrative Oversight Committee (IAOC) 🌸.

Status of This Memo 🌈

this one is not an Internet Standards Track spec. It's published just for information 💜.

This document is a product of the Internet Architecture Board (IAB). It holds info the IAB thought was worth keeping on the permanent record. Docs the IAB approves for publication can't become any level of Internet Standard. See Section 2 of RFC 5741 for that 🔥.

Info about the current status of this document, any errata, and how to give feedback can be found at http://www.rfc-editor.org/info/rfc6548 🦋.

Copyright Notice 🎀

Copyright (c) 2012 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) as they stand on the publication date. Please read these carefully, bestie, because they explain your rights and restrictions for this doc 🫶.

Table of Contents 🧚

1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2
  2.  Independent Submission Editor . . . . . . . . . . . . . . . . . 2
    2.1.  Qualifications  . . . . . . . . . . . . . . . . . . . . . . 2
    2.2.  Responsibilities  . . . . . . . . . . . . . . . . . . . . . 3
  3.  Independent Submission Editorial Board  . . . . . . . . . . . . 4
  4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
  5.  IAB Members at the Time of Approval . . . . . . . . . . . . . . 4
  6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 4
  7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 4
    7.1.  Normative References  . . . . . . . . . . . . . . . . . . . 4
    7.2.  Informative References  . . . . . . . . . . . . . . . . . . 5

1. Introduction 🌸

so the RFC Editor Model [RFC6635] sets out a bunch of streams that make draft RFCs for publication 📚. This doc is all about managing the Independent Submission stream, specifically the Independent Submission Editor (ISE) role 👑. It's a derivative of [RFC5620], Section 3.2, and got split out from [RFC6635] 🍓.

This document obsoletes [RFC5620] in combination with [RFC6635] 💅.

2. Independent Submission Editor 🦋

the ISE is an individual 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 [RFC6635] 🙈. As noted below, the ISE is appointed by and answers directly to the IAB 👑.

2.1. Qualifications 💖

the ISE is a senior position, and these are the qualifications that are desired 🔥:

1. Technical competence, meaning broad technical experience and perspective across a wide range of Internet technologies and applications, plus the ability to work effectively with parts of that spectrum where 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 a demonstrated history of working 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 they're 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 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 IAOC 📊.

The ISE may choose to pick individuals to take part in an Advisory Board for help with special topics, whenever the ISE thinks that's appropriate 💜. That Advisory Board exists at the pleasure of the ISE, and its members serve at the pleasure of the ISE too 👑.

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 the IAB uses to select an IAOC member every other year, as described in [RFC4333], should be used 🎀.

Even though the ISE itself is a volunteer function, the IAB considers keeping the Independent Submission stream part of the IAB's supported activities. So the IAOC should include these costs in the IASA budget 💰.

3. Independent Submission Editorial Board 🌸

the ISE gets support from an Editorial Board that reviews Independent Submission stream documents 📚. This board is called the Independent Submission Editorial Board 🦋. It's a volunteer board that exists at the pleasure of the ISE, and its members serve at the pleasure of the ISE 💖. This model just notes that the board exists. Any further discussion of it is out of scope for this document 🙈.

4. Security Considerations 🔥

⚠️ Security note, bestie: This document has no specific security implications. However, the same security considerations as those in [RFC4846] and [RFC4844] apply. Please take them seriously 💀.

5. IAB Members at the Time of Approval 👑

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

6. Acknowledgements 🫶

huge 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 ✨.

7. References 📚

7.1. Normative References 🔥

• [RFC4846] Klensin, J. and D. Thaler, "Independent Submissions to the RFC Editor", RFC 4846, July 2007.
• [RFC4844] Daigle, L., Ed. and IAB, "The RFC Series and RFC Editor", RFC 4844, July 2007.

7.2. Informative References 🧚

• [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. and IAB, "RFC Editor Model (Version 1)", RFC 5620, August 2009.
• [RFC6635] Kolkman, O., Ed., Halpern, J., Ed., and IAB, "RFC Editor Model (Version 2)", RFC 6635, June 2012.

Authors' Addresses 💌

Nevil Brownlee (editor), The University of Auckland 🎓 EMail: n.brownlee@auckland.ac.nz

Internet Architecture Board 🏛️ EMail: iab@iab.org