Re: [urn] continued use of urn-nid@ietf.org list

Sean Leonard <dev+ietf@seantek.com> Mon, 12 January 2015 08:06 UTC

Return-Path: <dev+ietf@seantek.com>
X-Original-To: urn-nid@ietfa.amsl.com
Delivered-To: urn-nid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE32A1A8A67; Mon, 12 Jan 2015 00:06:08 -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 ujBNFVBdfYFB; Mon, 12 Jan 2015 00:06:07 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (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 E753C1A8A66; Mon, 12 Jan 2015 00:06:06 -0800 (PST)
Received: from [192.168.123.7] (unknown [23.241.1.22]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 6932322E26A; Mon, 12 Jan 2015 03:06:05 -0500 (EST)
Message-ID: <54B38029.9060804@seantek.com>
Date: Mon, 12 Jan 2015 00:04:57 -0800
From: Sean Leonard <dev+ietf@seantek.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: [urn] continued use of urn-nid@ietf.org list
References: <5499BA48.5060807@andyet.net> <5499BED1.104@seantek.com> <5499C04C.6040605@andyet.net> <549A58E4.30206@it.aoyama.ac.jp> <844A0581B9447C7703322432@JcK-HP8200.jck.com> <CALaySJJU1XdwrOyTdJ4nobrW8=piQ40Z0=Ay-5KvJY9-iGTEYQ@mail.gmail.com> <54B2279C.2020203@seantek.com> <CALaySJJObM8v+rN=LMvy1gdvRCPQqND7QLw74p4WVB9DxFn+zQ@mail.gmail.com>
In-Reply-To: <CALaySJJObM8v+rN=LMvy1gdvRCPQqND7QLw74p4WVB9DxFn+zQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn-nid/PUmAkY7BKsQJS-Vs67zufEAdOOU>
Cc: John C Klensin <john-ietf@jck.com>, "urn-nid@ietf.org" <urn-nid@ietf.org>, "urn@ietf.org" <urn@ietf.org>
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn-nid/>
List-Post: <mailto:urn-nid@ietf.org>
List-Help: <mailto:urn-nid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jan 2015 08:06:09 -0000

On 1/11/2015 5:50 AM, Barry Leiba wrote:
>> I completely disagree with, and would like to point out the contradiction in
>> terms, about: "I think we should celebrate...rapid progress...*by blocking
>> all pending and future [work]...*"
> ...
>> Thus, the proposal "not [to] start not start processing on any other URN
>> namespace requests until [the URNBIS] WG has finished the update" is both
>> unfair to participants and technically unsound.
> Sean, I understand what you're saying, and I share some of your
> concern here, which is why, in my "closing the loop" message, I said
> that I'm watching the time and will re-evaluate if we remain stalled.
> But I also understand the concern about (1) registering more and more
> URN namespaces without taking into account the changes that are in the
> works and (2) registering more and more URN namespaces without getting
> input from the registrants about whether the changes that are in the
> works suit their needs.
>
> I'm therefore willing to delay those requests for a reasonable time in
> order to try to get that input and have the changes taken into
> account.  Let's see how things go over the next couple of months, and
> then figure out where we are.

I can't speak for the other draft authors, but...I can live with a 
couple of months. Plenty of other I-Ds to write. <g>

Cheers,

Sean