Principles for Operation of Internet Assigned Numbers Authority (IANA) Registries
draft-iab-iana-principles-01

The information below is for an old version of the document
Document Type Active Internet-Draft
Last updated 2014-12-05
Stream IAB
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
Stream IAB state Active IAB Document
Consensus Boilerplate Unknown
RFC Editor Note (None)
Internet Architecture Board (IAB)                    R. Housley (editor)
Internet-Draft                                            Vigil Security
Intended status: Informational                       O. Kolkman (editor)
                                                        Internet Society
Expires: 8 June 2015                                     5 December 2014

                      Principles for Operation of
         Internet Assigned Numbers Authority (IANA) Registries

                      draft-iab-iana-principles-01

Abstract

   This document provides principles for the operation of Internet
   Assigned Numbers Authority (IANA) registries.

   {{{ RFC Editor: Please delete the note prior to publication. }}}

   Note: This Internet-Draft was developed by the IAB IANA Evolution
   Program, and it should be discussed on the InternetGovtech@iab.org
   mail list.  See http://www.iab.org/mailman/listinfo/internetgovtech
   for subscription details.

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 8 June 2015.

Copyright Notice

   Copyright (c) 2014 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

Housley & Kolkman          Expires 8 June 2015                  [Page 1]
Internet-Draft          IANA Registry Principles           December 2014

   (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.

0.  Document Background

   {{{ RFC Editor: Please delete this section prior to publication. }}}

   This document is a split off from draft-iab-iana-framework-02.  This
   document contains principles that were scattered in various places in
   the IANA Framework, pulling them into one place.

   The IANA Framework has been under discussion since February 2011.

1.  Introduction

   The Internet Engineering Task Force (IETF) and its predecessors have
   traditionally separated the publication of protocol specifications in
   immutable Request for Comments (RFCs) and the registries containing
   protocol parameters.  The latter is maintained by a set of functions
   traditionally known collectively as the Internet Assigned Numbers
   Authority (IANA).  Dating back to the earliest days of the Internet,
   specification publication and the registry operations were tightly
   coupled: Jon Postel of the Information Sciences Institute (ISI) of
   the University of Southern California (USC) was responsible for both
   RFC publication and IANA registry operation.  This tight coupling had
   advantages, but it was never a requirement.  Indeed, today the RFC
   Editor and IANA registry operation are provided by different
   entities.

   Internet registries are critical to the operation of the Internet,
   since they provide a definitive record of the value and meaning of
   identifiers that protocols use when communicating with each other.
   Almost every Internet protocol makes use of registries in some form.
   At the time of writing, the IANA maintains more than two thousand
   protocol parameter registries.

   Internet registries hold protocol identifiers consisting of constants
   and other well-known values used by Internet protocols.  These values
   can be numbers, strings, addresses, and so on.  They are uniquely
   assigned for one particular purpose or use.  Identifiers can be
   maintained in a central list (such as a list of cryptographic
   algorithms) or they can be hierarchically allocated and assigned by
   separate entities at different points in the hierarchy (such as IP

Housley & Kolkman          Expires 8 June 2015                  [Page 2]
Internet-Draft          IANA Registry Principles           December 2014

   addresses and domain names).

   The registry system is built on trust and mutual cooperation.  The
   use of the registries is voluntary and is not enforced by mandates or
   certification policies.  While the use of registries is voluntary, it
Show full document text