Guidelines for Writing an IANA Considerations Section in RFCs
draft-leiba-cotton-iana-5226bis-20

Document Type Active Internet-Draft (individual)
Last updated 2017-02-27 (latest revision 2017-02-09)
Stream IETF
Intended RFC status Best Current Practice
Formats plain text xml pdf html bibtex
Reviews
Stream WG state (None)
Document shepherd Tony Hansen
Shepherd write-up Show (last changed 2014-09-24)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Terry Manderson
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state Waiting on Authors
RFC Editor RFC Editor state EDIT
Network Working Group                                          M. Cotton
Internet-Draft                                                     ICANN
BCP: 26                                                         B. Leiba
Obsoletes: 5226 (if approved)                        Huawei Technologies
Intended status: Best Current Practice                         T. Narten
Expires: August 10, 2017                                 IBM Corporation
                                                       February 08, 2017

     Guidelines for Writing an IANA Considerations Section in RFCs
                   draft-leiba-cotton-iana-5226bis-20

Abstract

   Many protocols make use of points of extensibility that use constants
   to identify various protocol parameters.  To ensure that the values
   used in these fields do not have conflicting uses, and to promote
   interoperability, their allocation is often coordinated by a central
   record keeper.  For IETF protocols, that role is filled by the
   Internet Assigned Numbers Authority (IANA).

   To make assignments in a given registry prudently, guidance is needed
   for describing the conditions under which new values should be
   assigned, as well as when and how modifications to existing values
   can be made.  This document defines a framework for the documentation
   of these guidelines by specification authors, in order to assure that
   the provided guidance for the IANA Considerations is clear and
   addresses the various issues that are likely in the operation of a
   registry.

   This is the third edition of this document; it obsoletes RFC 5226.

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 http://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 August 10, 2017.

Copyright Notice

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

Cotton, Leiba & Narten  Expires August 10, 2017                 [Page 1]
Internet-Draft    IANA Considerations Section in RFCs      February 2017

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (http://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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Keep IANA Considerations for IANA  . . . . . . . . . . . .  3
     1.2.  For Updated Information  . . . . . . . . . . . . . . . . .  4
     1.3.  A Quick Checklist Up Front . . . . . . . . . . . . . . . .  4
   2.  Creating and Revising Registries . . . . . . . . . . . . . . .  6
     2.1.  Organization of Registries . . . . . . . . . . . . . . . .  6
     2.2.  Documentation Requirements for Registries  . . . . . . . .  7
     2.3.  Specifying Change Control for a Registry . . . . . . . . .  9
     2.4.  Revising Existing Registries . . . . . . . . . . . . . . . 10
   3.  Registering New Values in an Existing Registry . . . . . . . . 10
     3.1.  Documentation Requirements for Registrations . . . . . . . 10
     3.2.  Updating Existing Registrations  . . . . . . . . . . . . . 12
     3.3.  Overriding Registration Procedures . . . . . . . . . . . . 13
     3.4.  Early Allocations  . . . . . . . . . . . . . . . . . . . . 13
   4.  Choosing a Registration Policy, and Well-Known Policies  . . . 14
     4.1.  Private Use  . . . . . . . . . . . . . . . . . . . . . . . 16
     4.2.  Experimental Use . . . . . . . . . . . . . . . . . . . . . 16
     4.3.  Hierarchical Allocation  . . . . . . . . . . . . . . . . . 17
     4.4.  First Come First Served  . . . . . . . . . . . . . . . . . 17
     4.5.  Expert Review  . . . . . . . . . . . . . . . . . . . . . . 18
     4.6.  Specification Required . . . . . . . . . . . . . . . . . . 19
     4.7.  RFC Required . . . . . . . . . . . . . . . . . . . . . . . 20
     4.8.  IETF Review  . . . . . . . . . . . . . . . . . . . . . . . 21
Show full document text