RFC 8730

Independent Submission Editor Model

📅 published February 2020, from ietf

💖 Independent Submission Editor Model ✨

okay bestie, the title block first!! 🎀 This is RFC 8730, written by the Internet Architecture Board (IAB) with editor N. Brownlee from The University of Auckland, plus R. Hinden from Check Point Software 🧚. It's Informational (so not a standards track thing, just for the permanent record 📚), dated February 2020, and it obsoletes RFC 6548 🦋. Nothing here updates anything else, fr 💅.

Abstract ✨

so this doc is all about the job description of the RFC Independent Submission Editor (ISE) 💜 The Independent Submission stream is one of the stream producers that make draft RFCs, and the ISE is its stream approver 🌸. The ISE is basically the boss of everything going on in that stream 👑. They work with draft editors and reviewers, they talk to the RFC Production Center and Publisher, and they talk to the RFC Series Editor (RSE) too 💅. The IAB appoints the ISE, and the ISE also deals with the IETF Administration Limited Liability Company (LLC) 🫶.

this version obsoletes RFC 6548 so that every mention of the Internet Administrative Support Activity (IASA) and its related structures gets swapped for the ones from the IASA 2.0 structure 🔥 it's giving clean upgrade energy ✨

Status of This Memo 📜

this one is not on the Internet Standards Track, it's just published for info 🦋

This doc is a product of the Internet Architecture Board (IAB) and it's basically the IAB's way of saying "this is valuable, keep it forever" 📚 It represents the consensus of the IAB 🫶. Documents the IAB approves for publication are not candidates for any level of Internet Standard, so check Section 2 of RFC 7841 for that 💀.

Want the latest on this doc's status, any errata, or how to give feedback? Go here: https://www.rfc-editor.org/info/rfc8730 🌈

Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. 💖

this doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) as they stand on the publication date, so read those carefully because they spell out your rights and restrictions 🙈

Table of Contents 🍓

1.  Introduction
2.  Independent Submission Editor
  2.1.  Qualifications
  2.2.  Responsibilities
3.  Independent Submission Editorial Board
4.  Security Considerations
5.  References
  5.1.  Normative References
  5.2.  Informative References
IAB Members at the Time of Approval
Acknowledgements
Authors' Addresses

1. Introduction 🌸

The RFC Editor Model [RFC8728] defines a bunch of streams that make draft RFCs, which then get submitted for publication 📝 this doc is the management function for the Independent Submission stream, specifically the role of Independent Submission Editor (ISE) 💜

The previous version, [RFC6548], is a derivative of [RFC5620], Section 3.2, and it got split out from [RFC6635] 🦋

this doc updates the Independent Submission Editor Model so it lines up with the IASA 2.0 structure [RFC8711], which creates the IETF Administration Limited Liability Company ("LLC") run by a board of directors ("LLC Board") ✨ And yes, it obsoletes [RFC6548] 💀

2. Independent Submission Editor 👑

The ISE is an individual who is responsible for the Independent Submission stream of RFCs, as defined by [RFC8729] 💅 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 [RFC8728]) 🙅 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 they're hoping for: ✨

  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 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 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 pick individuals to join an Advisory Board for help with special topics, whenever the ISE thinks it'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 🌈

the ISE itself is a volunteer function, but the IAB considers keeping the Independent Submission stream going to be one of its supported activities 💅 So the LLC 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 known as 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, and any more discussion of it is out of scope for this doc 🙈

4. Security Considerations 🚨

🚨💀 this doc has no specific security implications, however the same security considerations as those in [RFC4846] and [RFC8729] apply 💀🚨

5. References 📚

5.1. Normative References 💜

[RFC4846]  Klensin, J., Ed. and D. Thaler, Ed., "Independent
           Submissions to the RFC Editor", RFC 4846,
           DOI 10.17487/RFC4846, July 2007,
           <https://www.rfc-editor.org/info/rfc4846>.

[RFC6548]  Brownlee, N., Ed. and IAB, "Independent Submission Editor
           Model", RFC 6548, DOI 10.17487/RFC6548, June 2012,
           <https://www.rfc-editor.org/info/rfc6548>.

[RFC8711]  Haberman, B., Hall, J., and J. Livingood, "Structure of
           the IETF Administrative Support Activity, Version 2.0",
           BCP 101, RFC 8711, DOI 10.17487/RFC8711, February 2020,
           <https://www.rfc-editor.org/info/rfc8711>.

[RFC8728]  Kolkman, O., Ed., Halpern, J., Ed., and R. Hinden, Ed.,
           "RFC Editor Model (Version 2)", RFC 8728,
           DOI 10.17487/RFC8728, February 2020,
           <https://www.rfc-editor.org/info/rfc8728>.

[RFC8729]  Housley, R., Ed. and L. Daigle, Ed., "The RFC Series and
           RFC Editor", RFC 8729, DOI 10.17487/RFC8729, February
           2020, <https://www.rfc-editor.org/info/rfc8729>.

5.2. Informative References 🌈

[RFC5620]  Kolkman, O., Ed. and IAB, "RFC Editor Model (Version 1)",
           RFC 5620, DOI 10.17487/RFC5620, August 2009,
           <https://www.rfc-editor.org/info/rfc5620>.

[RFC6635]  Kolkman, O., Ed., Halpern, J., Ed., and IAB, "RFC Editor
           Model (Version 2)", RFC 6635, DOI 10.17487/RFC6635, June
           2012, <https://www.rfc-editor.org/info/rfc6635>.

IAB Members at the Time of Approval 🎀

the IAB members when [RFC6548] was approved 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 when this doc (RFC 8730) was approved were: Jari Arkko, Alissa Cooper, Stephen Farrell, Wes Hardaker, Ted Hardie, Christian Huitema, Zhenbin Li, Erik Nordmark, Mark Nottingham, Melinda Shore, Jeff Tantsura, Martin Thomson, and Brian Trammell 🫶

Acknowledgements 🌸

Generous thanks to Joel Halpern for all his help with this doc, 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 document editor for this RFC to align it with the IASA 2.0 structure ✨

Authors' Addresses 📮

Nevil Brownlee (editor) The University of Auckland

Email: n.brownlee@auckland.ac.nz

Robert M. Hinden (editor) Check Point Software 959 Skyway Road San Carlos, CA 94070 United States of America

Email: bob.hinden@gmail.com

that's a wrap, bestie!! 🌈🦋💖✨ go read the original for the exact wording, it's the one that counts 🫶🧚

📦 where this page comes from