RFC 6548: Independent Submission Editor Model
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8730.
Current document in this lineage: RFC 8730 — Independent Submission Editor Model; RFC 9920 — RFC Editor Model (Version 3)
In plain English — editorial summary, not part of the RFC
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 Administrative Oversight Committee (IAOC). This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6548
- Published
- June 2012
- Authors
- N. Brownlee; IAB
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 5
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 7 RFCs, each formally replacing the one before it.
Referenced by
One later RFC formally updates or obsoletes part of this document.
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?