[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 RFC 6924

Network Working Group                                           B. Leiba
Internet-Draft                                       Huawei Technologies
Updates: 2648,3553 (if approved)                       February 14, 2013
Intended status: Informational
Expires: August 16, 2013

        Registration of Second-Level URN Namespaces Under "ietf"
                  draft-leiba-urnbis-ietf-namespace-02

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, and
   updates RFC 2648 and RFC 3553 to refer readers of those documents to
   this 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 August 16, 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


Leiba                   Expires August 16, 2013                 [Page 1]

Internet-Draft        IETF URN namespace registry          February 2013


   "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.

   Action 3: Populate the new registry as follows:

   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]
   --------------+-----------+-----------------------------------------

   [[IANA and RFC Editor: Please replace "XXXX", above, with this RFC
   number, and remove this note.]]

3.  Security Considerations

Leiba                   Expires August 16, 2013                 [Page 2]

Internet-Draft        IETF URN namespace registry          February 2013


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

4.  Acknowledgments

   Alfred Hoenes noticed the absence of this 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. 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 0648
   Email: barryleiba@computer.org
   URI:   http://internetmessagingtechnology.org/





















Leiba                   Expires August 16, 2013                 [Page 3]


Html markup produced by rfcmarkup 1.108, available from http://tools.ietf.org/tools/rfcmarkup/