The Use of Registries
draft-wilde-registries-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-02-01
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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                                          February 1, 2016
Intended status: Informational
Expires: August 4, 2016

                         The Use of Registries
                       draft-wilde-registries-00

Abstract

   Registries on the Internet and the Web fulfill a wide range of tasks,
   ranging from low-level networking aspects such as packet type
   identifiers, all the way to application-level protocols and
   standards.  This document summarizes some of the reasons of why and
   how to use registries, and how some of them are operated.  It serves
   as a 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
   discussions.

Note to Readers

   Please discuss this draft on the apps-discuss mailing list [1].

   Online access to all versions and files is available on GitHub [2].

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 4, 2016.

Wilde                    Expires August 4, 2016                 [Page 1]
Internet-Draft                 Registries                  February 2016

Copyright Notice

   Copyright (c) 2016 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
   (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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  TCP/UDP Port Numbers  . . . . . . . . . . . . . . . . . .   4
     2.2.  Language Tags . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Web Linking . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Why to use Registries . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Openness and Extensibility  . . . . . . . . . . . . . . .   6
     3.2.  Limited Namespaces  . . . . . . . . . . . . . . . . . . .   6
     3.3.  Design/Usage Review . . . . . . . . . . . . . . . . . . .   7
     3.4.  Identifier Design . . . . . . . . . . . . . . . . . . . .   7
     3.5.  Identifier Lifecycle  . . . . . . . . . . . . . . . . . .   7
     3.6.  Documentation Requirements  . . . . . . . . . . . . . . .   8
     3.7.  Centralized Lookup  . . . . . . . . . . . . . . . . . . .   9
   4.  When to use Registries  . . . . . . . . . . . . . . . . . . .   9
   5.  How to use Registries . . . . . . . . . . . . . . . . . . . .  10
     5.1.  Implementation Support  . . . . . . . . . . . . . . . . .  10
     5.2.  Registry Application  . . . . . . . . . . . . . . . . . .  10
     5.3.  Registry Stability  . . . . . . . . . . . . . . . . . . .  10
     5.4.  Registry History  . . . . . . . . . . . . . . . . . . . .  10
     5.5.  Runtime vs. Design-Time . . . . . . . . . . . . . . . . .  10
     5.6.  Registry Access . . . . . . . . . . . . . . . . . . . . .  10
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Technologies and standards in computer networking have long used the
   concept of a "Registry" as a place where well-known information is
   available and managed.  In most case, the main reason to use a
   registry is to create a technology or standard that has stable parts

Wilde                    Expires August 4, 2016                 [Page 2]
Internet-Draft                 Registries                  February 2016

   (the technology/standard itself), as well as some parts that are
   supposed to evolve while the technology/standard itself remains
   stable and unchanged.

   A registry essentially is a pattern of how to separate those two
Show full document text