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

[Ballot comment]

Seems a little OTT to prescribe the page layout for the
new registry, maybe s/will appear/should appear/ or
something might be better and save a later pedantic
update to this.

[Ballot discuss]
As far as I can tell, this document doesn't Update the two RFCs it points to. These look like the "See Also" use of Updates we've agreed not to use. Am I missing something it changes in the earlier RFCs? If so, could that be written more clearly?

IANA has reviewed draft-leiba-urnbis-ietf-namespace-01 and has the following comments:

We understand that, upon approval of this document, there are two
actions which IANA must complete.

First, on the IANA Matrix located at:

http://www.iana.org/protocols

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 will rename the group "IETF Protocol Parameter Identifiers", giving it the new name "Uniform Resource Name (URN) Namespace for IETF Use".
We understand that the existing registry in that group will remain, and its name will be unchanged.

Second, a new registry will be added to the group now named "Uniform Resource Name (URN) Namespace for IETF Use". The new registry will be called "IETF URN Sub-namespaces", and new registrations will use the "IETF Review" policy as defined in RFC 5226 [RFC5226]. The new registry will appear first in the group, to provide a human-friendly, top-down resolution of the namespace hierarchy.

There are initial registrations in the new registry. The new registry will appear as follows:

IETF URN Sub-namespaces
Registration Procedure(s): IETF Review
Reference: [ RFC-to-be ]

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

We understand that these two actions are the only ones required to be
completed upon approval of this document.

Note: The actions requested in this document will not be completed
until the document has been approved for publication as an RFC.

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
Reply-To: ietf@ietf.org
Subject: Last Call:  (Registration of Second-Level URI Namespaces Under "ietf") to Informational RFC


The IESG has received a request from an individual submitter to consider
the following document:
- 'Registration of Second-Level URI Namespaces Under "ietf"'
  as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-02-11. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-leiba-urnbis-ietf-namespace/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-leiba-urnbis-ietf-namespace/ballot/


No IPR declarations have been submitted directly on this I-D.

1. Summary

Barry Leiba is serving as the document shepherd as well as author
of this simple document.  Pete Resnick is the responsible Area
Director.

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 Informational document creates
and populates such a registry.

2. Review and Consensus

This document originates from a note to IANA by Alfred H�nes, in
which Alfred noted the absence of the subject registry.  IANA
asked Barry, as the AD responsible for the urnbis working group,
and Barry agreed that such a registry is needed.  Because this is
outside the urnbis charter, Barry is pursuing this as an
individual submission.

There has so far been no other discussion of this within the
community; little discussion is expected, and any that happens
will be during last call.  This is a simple document that's
addressing a procedural oversight, and no special reviews are
necessary.

3. Intellectual Property

The author confirms that to his personal knowledge, in
conformance with BCPs 78 and 79, there is no IPR related to this
document.

4. Other Points

This document creates a new IANA registry to hold URN
sub-namespaces under the "ietf" namespace.  Existing such
namespaces include "urn:ietf:rfc:", "urn:ietf:std:", and
"urn:ietf:params:".  All of the existing namespaces are entered
into the new registry by this document, and future registrations
are defined as requiring IETF Review.  This policy seems
appropriate for top-level sub-namespaces controlled by the IETF,
and is in the spirit of RFC 2648.  This document updates RFCs
2648 and 3553, for two reasons: (1) It registers the
sub-namespaces created in those documents and the establishment
of the registry needs to be noted by readers of those documents,
and (2) RFC 2648 itself implies that if new sub-namespaces are
created, RFC 2648 will need to be updated.