How Requests for IANA Action Will Be Handled on the Independent Stream
RFC 8726, “How Requests for IANA Action Will Be Handled on the Independent Stream”, is an Informational document published in November 2020 by A. Farrel. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 8726 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8725 JSON Web Token Best Current Practices
- RFC 8727 JSON Binding of the Incident Object Description Exchange Format
- RFC 8724 SCHC: Generic Framework for Static Context Header Compression and Fragmentation
- RFC 8728 RFC Editor Model
- RFC 8723 Double Encryption Procedures for the Secure Real-Time Transport Protocol
- RFC 8729 The RFC Series and RFC Editor
- RFC 8722 Defining the Role and Function of IETF Protocol Parameter Registry Operators
- RFC 8730 Independent Submission Editor Model