The Use of Registries
draft-wilde-registries-03

Document Type Active Internet-Draft (individual)
Last updated 2019-07-30
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           E. Wilde
Internet-Draft                                             July 30, 2019
Intended status: Informational
Expires: January 31, 2020

                         The Use of Registries
                       draft-wilde-registries-03

Abstract

   Registries for Internet and Web protocols fulfill a wide range of
   tasks, ranging from low-level networking aspects such as packet type
   identifiers, all the way up to application-level protocols and
   standards.  This document summarizes some of the reasons of why,
   when, and how to use registries.  It serves as an informative
   reference for specification writers considering whether to create and
   manage a registry, allowing them to better understand some of the
   issues associated with certain design and operational decisions.

Note to Readers

   Please discuss this draft on the ART mailing list
   (<https://www.ietf.org/mailman/listinfo/art>).

   Online access to all versions and files is available on GitHub
   (<https://github.com/dret/I-D/tree/master/registries>).

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 January 31, 2020.

Wilde                   Expires January 31, 2020                [Page 1]
Internet-Draft                 Registries                      July 2019

Copyright Notice

   Copyright (c) 2019 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.  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
   2.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  TCP/UDP Port Numbers  . . . . . . . . . . . . . . . . . .   4
     2.2.  Language Tags . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Web Linking . . . . . . . . . . . . . . . . . . . . . . .   5
     2.4.  Domain Name System (DNS)  . . . . . . . . . . . . . . . .   6
     2.5.  non-IANA/DNS example  . . . . . . . . . . . . . . . . . .   6
   3.  Why use Registries  . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Openness and Extensibility  . . . . . . . . . . . . . . .   7
     3.2.  Limited Namespaces  . . . . . . . . . . . . . . . . . . .   7
     3.3.  Design/Usage Review . . . . . . . . . . . . . . . . . . .   8
     3.4.  Identifier Design . . . . . . . . . . . . . . . . . . . .   8
     3.5.  Identifier Lifecycle  . . . . . . . . . . . . . . . . . .   9
     3.6.  Documentation Requirements  . . . . . . . . . . . . . . .   9
     3.7.  Centralized Lookup  . . . . . . . . . . . . . . . . . . .  10
   4.  When to use Registries  . . . . . . . . . . . . . . . . . . .  10
   5.  Barrier to Entry Issues . . . . . . . . . . . . . . . . . . .  11
     5.1.  Non-Semantic/Reserved Entries . . . . . . . . . . . . . .  11
     5.2.  Entry Levels  . . . . . . . . . . . . . . . . . . . . . .  12
     5.3.  Separation by Value Syntax  . . . . . . . . . . . . . . .  12
   6.  How to use Registries . . . . . . . . . . . . . . . . . . . .  13
     6.1.  Registry Operations . . . . . . . . . . . . . . . . . . .  14
     6.2.  Registry Creation . . . . . . . . . . . . . . . . . . . .  15
     6.3.  Registry Interaction  . . . . . . . . . . . . . . . . . .  15
     6.4.  Implementation Support  . . . . . . . . . . . . . . . . .  16
     6.5.  Registry Stability  . . . . . . . . . . . . . . . . . . .  16
     6.6.  Registry History  . . . . . . . . . . . . . . . . . . . .  16
     6.7.  Registry Access . . . . . . . . . . . . . . . . . . . . .  17
     6.8.  Runtime vs. Design-Time . . . . . . . . . . . . . . . . .  17
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  18

Wilde                   Expires January 31, 2020                [Page 2]
Show full document text