RFC 8726: How Requests for IANA Action Will Be Handled on the Independent Stream
In plain English — editorial summary, not part of the RFC
The Internet Assigned Numbers Authority (IANA) maintains registries to track code points used by protocols such as those defined by the IETF and documented in RFCs developed on the IETF Stream. The Independent Submission Stream is another source of documents that can be published as RFCs. This stream is under the care of the Independent Submissions Editor (ISE). This document complements RFC 4846 by providing a description of how the ISE currently handles documents in the Independent Submission Stream that request actions from IANA. Nothing in this document changes existing IANA registries or their allocation policies, nor does it change any previously documented processes.
Document record
- Document ID
- RFC8726
- Published
- November 2020
- Authors
- A. Farrel
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7958DNSSEC Trust Anchor Publication for the Root ZoneObsoleted
August 2016
- RFC 9957The DOCSIS Queue Protection Algorithm to Preserve Low LatencyCurrent
May 2026
- RFC 3589Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5Current
September 2003
- RFC 8722Defining the Role and Function of IETF Protocol Parameter Registry OperatorsCurrent
February 2020
- RFC 8730Independent Submission Editor ModelUpdated
February 2020
- RFC 8688A Session Initiation Protocol (SIP) Response Code for Rejected CallsCurrent
December 2019
- RFC 9029Updates to the Allocation Policy for the Border Gateway Protocol - Link State (BGP-LS) Parameters RegistriesObsoleted
June 2021
- RFC 8356Experimental Codepoint Allocation for the Path Computation Element Communication Protocol (PCEP)Current
March 2018
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?