Registration of Second-Level URI Namespaces Under "ietf"
draft-leiba-urnbis-ietf-namespace-01

Abstract

RFC 2648 defines the "ietf" URN namespace, and defines a number of sub-namespaces. RFC 3553 defines an additional sub-namespace, "params", and creates a registry to document allocations under that. But there is no registry that lists, in one place, all sub-namespaces of "ietf". This document creates and populates such a registry.

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 12, 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 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.

1. Introduction

"A URN Namespace for IETF Documents" [RFC2648] defines the "ietf" URN namespace, and defines a number of sub-namespaces. "An IETF URN Sub-namespace for Registered Protocol Parameters" [RFC3553] defines an additional sub-namespace, "params", and creates a registry to document allocations under that. But there is no registry that lists, in one place, all sub-namespaces of "ietf". This document creates and populates such a registry, and updates RFC 2648 and RFC 3553 to refer readers of those documents to this registry.

2. IANA Considerations

There is currently a top-level registry group called "IETF Protocol Parameter Identifiers", which contains one registry, "IETF URN Sub-namespace for Registered Protocol Parameters". IANA is asked to take the following three actions:

Action 1: Rename the group "IETF Protocol Parameter Identifiers", giving it the new name "Uniform Resource Name (URN) Namespace for IETF Use". The existing registry in that group will remain, and its name will be unchanged.

Action 2: Add a new registry to the renamed group. The new registry will be called "IETF URN Sub-namespaces", and new registrations will use the IETF Review policy [RFC5226], which provides for IETF consensus in order to add a new URN namespace under "ietf". The new registry will appear first in the group, to provide a human-friendly, top-down resolution of the namespace hierarchy.

IETF URN Sub-namespaces

Registration Procedures: IETF Review
Reference: [RFCXXXX]

Note: This is the Official Registry for sub-namespaces of the 'IETF'
URN Namespace.

Sub-namespace | Reference | IANA Registry Reference
--------------+-----------+-----------------------------------------
rfc           | [RFC2648] | none
fyi           | [RFC2648] | none
std           | [RFC2648] | none
bcp           | [RFC2648] | none
id            | [RFC2648] | none
mtg           | [RFC2648] | none
params        | [RFC3553] | [http://www.iana.org/assignments/params]
--------------+-----------+-----------------------------------------
          

Action 3: Populate the new registry as follows:

3. Security Considerations

This is a procedural document, and is entirely unrelated to security.

4. References

4.1. Normative References

4.2. Informative References

Author's Address

Table of Contents

• 1. Introduction
• 2. IANA Considerations
• 3. Security Considerations
• 4. References
• 4.1. Normative References
• 4.2. Informative References
• Author's Address