datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Uniform Resource Name (URN) Namespace Definition Mechanisms
draft-ietf-urnbis-rfc3406bis-urn-ns-reg-09

Document type: Active Internet-Draft (urnbis WG)
Document stream: IETF
Last updated: 2014-02-12
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

IETF State: WG Document
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

URNBIS                                                    P. Saint-Andre
Internet-Draft                                                      &yet
Obsoletes: 3406 (if approved)                          February 12, 2014
Intended status: Best Current Practice
Expires: August 16, 2014

      Uniform Resource Name (URN) Namespace Definition Mechanisms
               draft-ietf-urnbis-rfc3406bis-urn-ns-reg-09

Abstract

   This document supplements the Uniform Resource Name (URN) syntax
   specification by defining the concept of a URN namespace, as well as
   mechanisms for defining and registering such namespaces.  This
   document obsoletes RFC 3406.

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 16, 2014.

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

Saint-Andre              Expires August 16, 2014                [Page 1]
Internet-Draft               URN Namespaces                February 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  What is a URN Namespace?  . . . . . . . . . . . . . . . . . .   3
   4.  URN Namespace Types . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Formal Namespaces . . . . . . . . . . . . . . . . . . . .   5
     4.2.  Informal Namespaces . . . . . . . . . . . . . . . . . . .   6
   5.  Defining a URN Namespace  . . . . . . . . . . . . . . . . . .   7
     5.1.  Purpose . . . . . . . . . . . . . . . . . . . . . . . . .   7
     5.2.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.3.  Assignment  . . . . . . . . . . . . . . . . . . . . . . .   8
     5.4.  Security and Privacy  . . . . . . . . . . . . . . . . . .   9
     5.5.  Resolution  . . . . . . . . . . . . . . . . . . . . . . .   9
   6.  Registration Template . . . . . . . . . . . . . . . . . . . .  10
     6.1.  Namespace ID  . . . . . . . . . . . . . . . . . . . . . .  10
     6.2.  Version . . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.3.  Date  . . . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.4.  Registrant  . . . . . . . . . . . . . . . . . . . . . . .  10
     6.5.  Purpose . . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.6.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.7.  Assignment  . . . . . . . . . . . . . . . . . . . . . . .  10
     6.8.  Resolution  . . . . . . . . . . . . . . . . . . . . . . .  10
     6.9.  Documentation . . . . . . . . . . . . . . . . . . . . . .  11
   7.  Registering a URN Namespace . . . . . . . . . . . . . . . . .  11
     7.1.  Formal Namespaces . . . . . . . . . . . . . . . . . . . .  11
     7.2.  Informal Namespaces . . . . . . . . . . . . . . . . . . .  11
   8.  Guidelines for Designated Experts . . . . . . . . . . . . . .  12
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   10. Security and Privacy Considerations . . . . . . . . . . . . .  12
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  12
     11.2.  Informative References . . . . . . . . . . . . . . . . .  13
   Appendix A.  Changes from RFC 3406  . . . . . . . . . . . . . . .  14
   Appendix B.  Contributors . . . . . . . . . . . . . . . . . . . .  14
   Appendix C.  Acknowledgements . . . . . . . . . . . . . . . . . .  14
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

[include full document text]