datatracker.ietf.org
Sign in
Version 5.6.2.p2, 2014-07-24
Report a bug

Uniform Resource Name (URN) Syntax
draft-ietf-urnbis-rfc2141bis-urn-07

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

IETF State: WG Document
Document shepherd: No shepherd assigned

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

URNBIS                                               P. Saint-Andre, Ed.
Internet-Draft
Obsoletes: 2141 (if approved)                           January 23, 2014
Intended status: Standards Track
Expires: July 27, 2014

                   Uniform Resource Name (URN) Syntax
                  draft-ietf-urnbis-rfc2141bis-urn-07

Abstract

   A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI)
   that is intended to serve as a persistent, location-independent
   resource identifier.  This document defines the canonical syntax for
   URIs under the "urn" scheme, guidelines for URN namespaces,
   requirements for URN presentation and transmission, and methods for
   determining URN equivalence.  This document obsoletes RFC 2141.

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 July 27, 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

Saint-Andre               Expires July 27, 2014                 [Page 1]
Internet-Draft                 URN Syntax                   January 2014

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  URN Syntax  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Namespace Identifier Syntax . . . . . . . . . . . . . . .   4
     4.2.  Namespace Specific String Syntax  . . . . . . . . . . . .   4
     4.3.  Query Component and Fragment Identifier Component . . . .   4
   5.  URN Presentation and Transport  . . . . . . . . . . . . . . .   5
   6.  Equivalence of URNs . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Procedure . . . . . . . . . . . . . . . . . . . . . . . .   5
     6.2.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Handling of URNs by URI Processors  . . . . . . . . . . . . .   6
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Appendix A.  Changes from RFC 2141  . . . . . . . . . . . . . . .   8
   Appendix B.  Contributors . . . . . . . . . . . . . . . . . . . .   9
   Appendix C.  Acknowledgements . . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI)
   [RFC3986] that is intended to serve as a persistent, location-
   independent resource identifier.  This document defines the canonical

[include full document text]