datatracker.ietf.org
Sign in
Version 5.7.1.p2, 2014-10-29
Report a bug

Uniform Resource Names (URNs)
draft-ietf-urnbis-rfc2141bis-urn-08

URNBIS                                                    P. Saint-Andre
Internet-Draft                                                      &yet
Obsoletes: 2141, 3406 (if approved)                           J. Klensin
Intended status: Standards Track
Expires: April 24, 2015                                 October 21, 2014

                     Uniform Resource Names (URNs)
                  draft-ietf-urnbis-rfc2141bis-urn-08

Abstract

   A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI)
   that is assigned under the "urn" scheme and a particular URN
   namespace, typically with the intent that the URN will be a
   persistent, location-independent resource identifier or abstract
   designator.  With regard to URN syntax, this document defines the
   canonical syntax for URNs (in a way that is consistent with URI
   syntax), specifies methods for determining URN equivalence, and
   discusses URI conformance.  With regard to URN namespaces, this
   specifies a method for defining a URN namespace and associating it
   with a namespace identifier, and describes procedures for registering
   namespace identifiers with the Internet Assigned Numbers Authority
   (IANA).  This document obsoletes both RFC 2141 and 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 April 24, 2015.

Copyright Notice

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

Saint-Andre & Klensin    Expires April 24, 2015                 [Page 1]
Internet-Draft                    URNs                      October 2014

   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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  URN Syntax  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Namespace Identifier Syntax . . . . . . . . . . . . . . .   5
     3.2.  Namespace Specific String Syntax  . . . . . . . . . . . .   5
     3.3.  p-component, q-component, and f-component . . . . . . . .   6
   4.  Equivalence of URNs . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Procedure . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  URI Conformance . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  URN Namespaces  . . . . . . . . . . . . . . . . . . . . . . .   9
     6.1.  Formal Namespaces . . . . . . . . . . . . . . . . . . . .  11
     6.2.  Informal Namespaces . . . . . . . . . . . . . . . . . . .  12
   7.  Defining a URN Namespace  . . . . . . . . . . . . . . . . . .  12
     7.1.  Purpose . . . . . . . . . . . . . . . . . . . . . . . . .  13
     7.2.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     7.3.  Assignment  . . . . . . . . . . . . . . . . . . . . . . .  14
     7.4.  Security and Privacy  . . . . . . . . . . . . . . . . . .  15

[include full document text]