[urn] Registration requirement for separation of namespaces

[John C Klensin <[e-mail]>]

Hi.

This note is prompted by a recent Last Call discussion on the
IETF List about a new namespace proposal,
draft-martin-urn-globus.   Those who are interested in details
should have a look at that draft and archives of the IETF
discussion list for messages with subject lines containing that
string and posted within the last week or so.  I don't believe
those details are needed to understand what follows.

Section 4.3 of RFC 3406 requires that a registration request for
a new namespace have a "Namespace Considerations" section that

	"outlines the perceived need for a new namespace (i.e.,
	where existing namespaces fall short of the proposer's
	requirements)."

That requirement was dropped when we folded the registration
procedures and requirements into 2141bis and, indeed, was
dropped before the posting of the now-obsolete
draft-ietf-urnbis-rfc3406bis-urn-ns-reg-09 in February 2014 (and
probably earlier).

That was some time ago.  Just to prevent any last-minute
surprises, does anyone see a need for a requirement that
proposals for new namespaces include consideration of existing
ones and why they are not applicable?  I note that such a
requirement may require significant research, especially as more
NIDs are registered, and may not actually be helpful.  I assume
that is the reason why the requirement was dropped.   If anyone
does feel that the requirement (or something like it) should be
reinstated, I'd appreciate it if they would speak up soon... and
that their comment justify the additional costs and explain how
whatever claims are made will be evaluated (or not).  Sending
proposed text would be ideal, but the most important thing, IMO,
is to know whether that is an issue that anyone plans to bring
up during WG or IETF Last Call.

thanks,
   john