Independent Submission Editor Model
RFC 8730
Document | Type |
RFC - Informational
(February 2020; No errata)
Obsoletes RFC 6548
Was draft-ietf-iasa2-rfc6548bis (individual)
|
|
---|---|---|---|
Authors | Nevil Brownlee , Bob Hinden | ||
Last updated | 2020-03-09 | ||
Stream | IAB | ||
Formats | plain text html xml pdf htmlized bibtex | ||
Stream | IAB state | Published RFC | |
Consensus Boilerplate | Yes | ||
RFC Editor Note | (None) |
Internet Architecture Board (IAB) N. Brownlee, Ed. Request for Comments: 8730 The University of Auckland Obsoletes: 6548 R. Hinden, Ed. Category: Informational Check Point Software ISSN: 2070-1721 February 2020 Independent Submission Editor Model Abstract 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 Internet Administrative Support Activity (IASA) and related structures with those defined by the IASA 2.0 structure. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Architecture Board (IAB) and represents information that the IAB has deemed valuable to provide for permanent record. It represents the consensus of the Internet Architecture Board (IAB). Documents approved for publication by the IAB are not candidates for any level of Internet Standard; see Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8730. Copyright Notice Copyright (c) 2020 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 (https://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. 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 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 [RFC6548] is a derivative of [RFC5620], Section 3.2, and was separated out from [RFC6635]. This document updates the Independent Submission Editor Model to align it with the IASA 2.0 structure [RFC8711] that creates the 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 [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 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 withShow full document text