[urn] Review period Re: I-D Action: draft-ietf-urnbis-rfc3406bis-urn-ns-reg-02.txt

Leslie Daigle <leslie@thinkingcat.com> Sun, 25 March 2012 12:59 UTC

Return-Path: <leslie@thinkingcat.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 8C86821F84AF for <urn@ietfa.amsl.com>; Sun, 25 Mar 2012 05:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id hYcMKYcVINZQ for <urn@ietfa.amsl.com>; Sun, 25 Mar 2012 05:59:04 -0700 (PDT)
Received: from zeke.ecotroph.net (zeke.ecotroph.net []) by ietfa.amsl.com (Postfix) with ESMTP id 892E321F84A0 for <urn@ietf.org>; Sun, 25 Mar 2012 05:59:04 -0700 (PDT)
Received: from dhcp-4553.meeting.ietf.org ([::ffff:]) (AUTH: PLAIN leslie, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by zeke.ecotroph.net with esmtp; Sun, 25 Mar 2012 08:58:51 -0400 id 015B4080.4F6F168E.00006B2D
Message-ID: <4F6F1689.1070704@thinkingcat.com>
Date: Sun, 25 Mar 2012 08:58:49 -0400
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: urn@ietf.org
References: <20120312202035.21803.90004.idtracker@ietfa.amsl.com>
In-Reply-To: <20120312202035.21803.90004.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [urn] Review period Re: I-D Action: draft-ietf-urnbis-rfc3406bis-urn-ns-reg-02.txt
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Mar 2012 12:59:05 -0000


This document questions the 2-week mailing list review period for formal 
namespace registrations, suggestion 4 weeks (or possibly 8).

First, that process came from what was standard/accepted practice at the 
time of writing the first document (RFC2611).  That was over a decade 
ago -- and maybe we all read mail a little more regularly then ;-)

I sort of wonder if there isn't generally a better mechanism, overall. 
What gets experts' attention these days?  Do we need an RSS feed? 
Tweets? (!).

All in all, I agree that reviews don't generally happen within 2 weeks. 
  Some of that is because the current designated expert hasn't been 
paying adequate attention, and should be replaced.  But then, authors 
don't come back quickly with updates, either, so there wind up being 
iterations before things are actually signed off.  I don't actually know 
that 4 or 8 weeks would capture that whole phase.

What I've seen (as the designated expert that needs to be replaced):

+ namespace proposals that don't  get published as I-D's
  -- Step 0:  please publish this as an I-D

+ namespace proposals that don't follow the correct version of the RFC
  -- authors need guidance about current version

+ namespace proposals that need to be cleaned up in terms of having 
reasonable explanations in the Considerations sections
  -- offer guidance and repeat

+ namespace proposals that come in through *other* IETF wgs, and never 
get put on the urn-nid mailing list
  -- need AD help to get them to the URN reviewers

What I have *not* seen, surprisingly (but pleasantly):

+ a lot of discussion about whether something really should be a URN 
namespace.  Hurrah.


On 3/12/12 4:20 PM, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Uniform Resource Names, Revised Working Group of the IETF.
> 	Title           : Uniform Resource Name (URN) Namespace Definition Mechanisms
> 	Author(s)       : Alfred Hoenes
> 	Filename        : draft-ietf-urnbis-rfc3406bis-urn-ns-reg-02.txt
> 	Pages           : 30
> 	Date            : 2012-03-12
>     Uniform Resource Names (URNs) are intended to serve as persistent,
>     location-independent, resource identifiers.  To structure and
>     organize their usage, the URN syntax (RFC 2141bis) specifies a
>     hierarchy that divides the set of possible URNs into "URN Namespaces"
>     that can be individually defined and managed.  URN Namespaces in
>     particular serve to map existing identifier systems into the URN
>     system and thereby make available generic, network-based resolution
>     services for the identified documents, artifacts, and other objects
>     (and metadata related to them).
>     To achive these goals, URN Namespaces need to be specified in a
>     comparable manner, and their Namespace Identifiers (NIDs) need to be
>     registered with IANA, so that naming conflicts are avoided and
>     implementers of services can follow a structured approach in support
>     of various namespaces, guided by the registry to the related
>     documents and the particularities of specific namespaces, as
>     described in these Namespace registration documents.
>     This RFC serves as a guideline for authors of URN Namespace
>     definition and registration documents and the process to be followed
>     to register a URN Namespace with IANA.  It describes the essential
>     content of such documents and how they shall be structured to allow
>     readers familar with the scheme to quickly assess the properties of a
>     specific URN Namespace.
>     This document is a companion document to the revised URN Syntax
>     specification, RFC 2141bis; it supersedes and replaces RFC 3406.
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-urnbis-rfc3406bis-urn-ns-reg-02.txt
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-urnbis-rfc3406bis-urn-ns-reg-02.txt
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn


      Yours to discover."
                                 -- ThinkingCat
Leslie Daigle