URNBIS P. Saint-Andre, Ed.
Internet-Draft Cisco Systems, Inc.
Obsoletes: 3406 (if approved) L. Daigle
Intended status: Best Current Practice Thinking Cat Enterprises
Expires: August 23, 2013 D.W. van Gulik
R. Iannella
Semantic Identity
P. Faltstrom
Netnod
February 19, 2013
Uniform Resource Name (URN) Namespace Definition Mechanisms
draft-ietf-urnbis-rfc3406bis-urn-ns-reg-05
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 23, 2013.
Copyright Notice
Copyright (c) 2013 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
Saint-Andre, et al. Expires August 23, 2013 [Page 1]
Internet-Draft URN Namespaces February 2013
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Discussion Venue . . . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. What is a URN Namespace? . . . . . . . . . . . . . . . . . . 4
5. URN Namespace Types . . . . . . . . . . . . . . . . . . . . . 5
5.1. Formal Namespaces . . . . . . . . . . . . . . . . . . . . 5
5.2. Informal Namespaces . . . . . . . . . . . . . . . . . . . 6
6. Defining a URN Namespace . . . . . . . . . . . . . . . . . . 7
6.1. Formal Namespaces . . . . . . . . . . . . . . . . . . . . 7
6.1.1. Syntax . . . . . . . . . . . . . . . . . . . . . . . 7
6.1.2. Specification . . . . . . . . . . . . . . . . . . . . 8
6.2. Informal Namespaces . . . . . . . . . . . . . . . . . . . 8
7. Registering a URN Namespace . . . . . . . . . . . . . . . . . 9
7.1. Formal Namespaces . . . . . . . . . . . . . . . . . . . . 9
7.2. Informal Namespaces . . . . . . . . . . . . . . . . . . . 9
8. URN Namespace Definition Template . . . . . . . . . . . . . . 10
9. Security Considerations . . . . . . . . . . . . . . . . . . . 14
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
11.1. Normative References . . . . . . . . . . . . . . . . . . 15
datatracker.ietf.org