Re: [urn] draft-ietf-urnbis-ns-reg-transition

Sean Leonard <dev+ietf@seantek.com> Sun, 21 February 2016 05:24 UTC

Return-Path: <dev+ietf@seantek.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 928F91B30EF for <urn@ietfa.amsl.com>; Sat, 20 Feb 2016 21:24:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Ste2hXwZVFj for <urn@ietfa.amsl.com>; Sat, 20 Feb 2016 21:24:12 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FC561B30F1 for <urn@ietf.org>; Sat, 20 Feb 2016 21:24:12 -0800 (PST)
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 390ED509BD for <urn@ietf.org>; Sun, 21 Feb 2016 00:24:11 -0500 (EST)
To: urn@ietf.org
References: <655C976223FCCC2DE6251563@JcK-HP8200.jck.com>
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <56C949BF.1030107@seantek.com>
Date: Sat, 20 Feb 2016 21:23:11 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <655C976223FCCC2DE6251563@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/gPOh7ZAdGc4xfpOH49cHUbaP3Qw>
Subject: Re: [urn] draft-ietf-urnbis-ns-reg-transition
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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, 21 Feb 2016 05:24:13 -0000

 From my perspective, this one is okay. I did not find any nits to pick, 
other than that the document seems mostly to be a matter of housekeeping 
for existing registrations (and I cannot think of any additional 
registrations to update).

However, this document raises a novel issue in my mind, which I will 
spin up under a separate thread.

Sean

On 2/7/2016 2:34 PM, John C Klensin wrote:
> Hi.
>
> draft-ietf-urnbis-ns-reg-transition-06 is now in the posting
> queue.  As compared to the previous version, it has updated
> references, an explicit reference to the IANA URN namespace
> registry, and some minor editorial tuning.
>
> We will eventually need to come back to this document after the
> 2141bis registration template is complete (see prior note about
> reviewing that template in 2141bis-15) and we are ready to move
> forward, but probably time can be better spent now than on
> review this document.  The one important exception is that, if
> anyone has (or knows of) existing registrations that could
> usefully be changed to reflect the new model, this would be the
> right time to start thinking about them, if only because minor
> patches could be made as part of this I-D without requiring new
> documents.
>
>       john
>
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn