How Requests for IANA Action Will Be Handled on the Independent Stream
RFC 8726

Document Type RFC - Informational (November 2020; No errata)
Was draft-ise-iana-policy (individual)
Author Adrian Farrel 
Last updated 2020-11-19
Stream ISE
Formats plain text html xml pdf htmlized bibtex
IETF conflict review conflict-review-ise-iana-policy
Stream ISE state Published RFC
Consensus Boilerplate Unknown
Document shepherd Adrian Farrel
Shepherd write-up Show (last changed 2019-08-20)
IESG IESG state RFC 8726 (Informational)
Telechat date
Responsible AD (None)
Send notices to Adrian Farrel <rfc-ise@rfc-editor.org>
IANA IANA review state Version Changed - Review Needed
IANA action state No IANA Actions


Independent Submission                                         A. Farrel
Request for Comments: 8726                Independent Submissions Editor
Category: Informational                                    November 2020
ISSN: 2070-1721

 How Requests for IANA Action Will Be Handled on the Independent Stream

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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This is a contribution to the RFC Series, independently of any other
   RFC stream.  The RFC Editor has chosen to publish this document at
   its discretion and makes no statement about its value for
   implementation or deployment.  Documents approved for publication by
   the RFC Editor 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/rfc8726.

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.  Allocations from Existing Registries
   3.  Changing Policies of Existing Registries
   4.  Creating New IANA Registries
   5.  Assigning Designated Experts
   6.  Transfer of Control
   7.  IANA Considerations
   8.  Security Considerations
   9.  References
     9.1.  Normative References
     9.2.  Informative References
   Acknowledgements
   Author's Address

1.  Introduction

   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.  A full
   list of registries and code points can be found at
   https://www.iana.org/protocols.

   Requests may be made to IANA for actions to create registries or to
   allocate code points from existing registries.  Procedures for these
   operations are described in [RFC8126].

   Many requests for IANA action are included in documents that are
   progressed for publication as RFCs.  RFCs may be sourced from within
   the IETF (on the IETF Stream) but may also be sourced from other
   streams, including the Independent Submission Stream (the Independent
   Stream), as described in [RFC4846].  The Independent Stream is under
   the care of the Independent Submissions Editor (ISE).

   This document complements [RFC4846] by providing a description of how
   the ISE currently handles documents in the Independent 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.

   If a case arises that is not precisely covered by this document, the
   ISE may discuss a solution with the interested parties, including
   IANA, the IESG, the stream managers for other streams, and the
   authors of an Independent Submission that requests IANA action.

2.  Allocations from Existing Registries

   Each IANA registry is governed by an allocation policy -- the rules
   that IANA applies to determine which code points can be allocated and
   under what circumstances.  These policies are described in [RFC8126].

   Documents proceeding from the Independent Stream will always follow
   the assignment policies defined for the registries from which they
   request allocations.  Similarly, all code point assignments are
   subject to the oversight of any designated expert (DE) appointed for
   the registry.

   It should be noted that documents on the Independent Stream can never
   result in Standards Track RFCs and Independent Stream documents are
   never subject to IETF review.  Thus, a registry whose policy is "IETF
   Review" or "Standards Action" [RFC8126] is not available to
   Independent Stream documents.

3.  Changing Policies of Existing Registries
Show full document text