How Requests for IANA Action Will be Handled on the Independent Stream
draft-ise-iana-policy-03

Document Type Active Internet-Draft (individual)
Last updated 2019-12-03 (latest revision 2019-09-23)
Stream ISE
Intended RFC status Informational
Formats plain text xml pdf htmlized bibtex
IETF conflict review conflict-review-ise-iana-policy
Stream ISE state Sent to the RFC Editor
Consensus Boilerplate Unknown
Document shepherd Adrian Farrel
Shepherd write-up Show (last changed 2019-08-20)
IESG IESG state I-D Exists
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
RFC Editor RFC Editor state RFC-EDITOR
Network Working Group                                          A. Farrel
Internet-Draft                            Independent Submissions Editor
Intended status: Informational                        September 23, 2019
Expires: March 26, 2020

 How Requests for IANA Action Will be Handled on the Independent Stream
                        draft-ise-iana-policy-03

Abstract

   The Internet Assigned Numbers Authority (IANA) maintains registries
   to track codepoints used by protocols such as those defined by the
   IETF and documented in RFCs developed on the IETF Stream.

   The Independent Submissions 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 Submissions
   Stream that request actions from the 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 Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on March 26, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Farrel                   Expires March 26, 2020                 [Page 1]
Internet-Draft       IANA and the Independent Stream      September 2019

   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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Allocations from Existing Registries  . . . . . . . . . . . .   3
   3.  Changing Policies of Existing Registries  . . . . . . . . . .   3
   4.  Creating New IANA Registries  . . . . . . . . . . . . . . . .   3
   5.  Assigning Designated Experts  . . . . . . . . . . . . . . . .   4
   6.  Transfer of Control . . . . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   10. Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The Internet Assigned Numbers Authority (IANA) maintains registries
   to track codepoints 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 Submissions 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 the IANA.  Nothing in this document changes
   existing IANA registries or their allocation policies, nor does it
   change any previously documented processes.

Farrel                   Expires March 26, 2020                 [Page 2]
Internet-Draft       IANA and the Independent Stream      September 2019
Show full document text