CARVIEW |
Select Language
HTTP/2 200
date: Mon, 14 Jul 2025 20:31:26 GMT
content-type: application/xml
cache-control: public, max-age=3600
cross-origin-opener-policy: same-origin
expires: Mon, 14 Jul 2025 21:31:26 GMT
referrer-policy: same-origin
vary: Cookie, origin, Accept-Encoding
x-content-type-options: nosniff
x-frame-options: DENY
x-resolution-methods: manual;auto;fallback
x-resolution-outcomes: ;RfcAdapter: using docid IETF RFC 8726 -> using query @.type == "IETF" && @.primary == true && @.id == "RFC 8726" -> 1 found,;
last-modified: Mon, 14 Jul 2025 20:31:26 GMT
cf-cache-status: EXPIRED
server: cloudflare
cf-ray: 95f3c89cc99320c5-BLR
content-encoding: gzip
alt-svc: h3=":443"; ma=86400
How Requests for IANA Action Will Be Handled on the Independent Stream
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.