Network Working GroupInternet Engineering Task Force (IETF) B. LeibaInternet-DraftRequest for Comments: 6924 Huawei Technologies Updates:2648,3553 (if approved) February 14,2648 April 2013Intended status:Category: InformationalExpires: August 16, 2013ISSN: 2070-1721 Registration of Second-Level URN NamespacesUnderunder "ietf"draft-leiba-urnbis-ietf-namespace-02Abstract RFC 2648 defines the "ietf" URNnamespace,namespace anddefinesa number ofsub-namespaces.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,and updatesthereby changing the mechanism defined in RFC 2648and RFC 3553 to refer readersfor adding new sub- namespaces ofthose documents to this registry."ietf". Status ofthisThis Memo ThisInternet-Draftdocument issubmitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documentsnot an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF).Note that other groups may also distribute working documents as Internet-Drafts. The listIt represents the consensus ofcurrent Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents validthe IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are amaximumcandidate for any level of Internet Standard; see Section 2 ofsix monthsRFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may beupdated, replaced, or obsoleted by other documentsobtained atany 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, 2013.http://www.rfc-editor.org/info/rfc6924. 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)(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" URNnamespace,namespace anddefinesa number of sub-namespaces. "An IETF URNSub- namespaceSub-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 updatesthereby changing the mechanism defined in RFC 2648and RFC 3553 to refer readersfor adding new sub-namespaces ofthose documents to this registry."ietf". 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". IANAis asked to takehas taken the following three actions: Action 1:RenameRenamed the group "IETF Protocol Parameter Identifiers", giving it the new name "Uniform Resource Name (URN) Namespace for IETF Use". The existing registry in that groupwill remain,remains, and its namewill beis unchanged. Its registration procedure has been updated to "IETF Review" (formerly called "IETF Consensus"). Action 2:AddAdded a new registry to the renamed group. The new registrywill beis 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 registrywill appearappears first in the group, to provide a human-friendly, top-down resolution of the namespace hierarchy. Action 3:PopulatePopulated the new registry as follows: IETF URN Sub-namespaces Registration Procedures: IETF Review Reference:[RFCXXXX][RFC6924] 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] --------------+-----------+-----------------------------------------[[IANA and RFC Editor: Please replace "XXXX", above, with this RFC number, and remove this note.]]3. Security Considerations This is a proceduraldocument,document and is entirely unrelated to security. 4. Acknowledgments Alfred Hoenes noticed the absence of thisregistry,registry and suggested its creation. 5. References 5.1. Normative References [RFC2648] Moats, R., "A URN Namespace for IETF Documents", RFC 2648, August 1999. [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. 5.2. Informative References [RFC3553] Mealling, M., Masinter, L., Hardie,T.T., and G. Klyne, "An IETF URN Sub-namespace for Registered Protocol Parameters", BCP 73, RFC 3553, June 2003. Author's Address Barry Leiba Huawei Technologies Phone: +1 646 827 0648Email:EMail: barryleiba@computer.org URI: http://internetmessagingtechnology.org/