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

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Wed, 24 December 2014 06:11 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 9AC951ACD07; Tue, 23 Dec 2014 22:11:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.199
X-Spam-Level:
X-Spam-Status: No, score=0.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 0j3C0-6mFaxC; Tue, 23 Dec 2014 22:11:31 -0800 (PST)
Received: from scintmta01-14.scbb.aoyama.ac.jp (scintmta01-14.scbb.aoyama.ac.jp [133.2.253.64]) by ietfa.amsl.com (Postfix) with ESMTP id 94E4D1ACD15; Tue, 23 Dec 2014 22:11:30 -0800 (PST)
Received: from scmeg01-14.scbb.aoyama.ac.jp (scmeg01-14.scbb.aoyama.ac.jp [133.2.253.15]) by scintmta01-14.scbb.aoyama.ac.jp (Postfix) with ESMTP id 4DF1432E53F; Wed, 24 Dec 2014 15:10:44 +0900 (JST)
Received: from itmail2.it.aoyama.ac.jp (unknown [133.2.206.134]) by scmeg01-14.scbb.aoyama.ac.jp with smtp id 15b9_5ed0_515d8f66_92a2_4211_8887_889c493da596; Wed, 24 Dec 2014 15:10:43 +0900
Received: from [133.2.210.64] (unknown [133.2.210.64]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id 9A635BF4DF; Wed, 24 Dec 2014 15:10:43 +0900 (JST)
Message-ID: <549A58E4.30206@it.aoyama.ac.jp>
Date: Wed, 24 Dec 2014 15:10:44 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Peter Saint-Andre - &yet <peter@andyet.net>, Sean Leonard <dev+ietf@seantek.com>, urn@ietf.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>
In-Reply-To: <5499C04C.6040605@andyet.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/RoIj71huhxI3bbwQ7H3v1QH5mWc
Cc: urn-nid@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: Wed, 24 Dec 2014 06:11:34 -0000

On 2014/12/24 04:19, Peter Saint-Andre - &yet wrote:
> On 12/23/14, 12:13 PM, Sean Leonard wrote:
>> Maybe.
>>
>> But there are two distinct controversies: 1) whether a proposed NID
>> follows the URN rules sufficiently to permit registration, and 2) what
>> the URN rules should be. It is very difficult for people who are trying
>> to get work done under 1), to get sucked into debates about 2).
>
> Ah, I am thinking of the post-URNBIS context. Once we finish 2141bis,
> the debates will be done. Or so I hope. :-)

I agree. Even now, the traffic isn't terribly high when averaged over a 
month or so, and while Sean definitely has a point, it's good that 
people who discuss the overall framework get exposed to actual examples 
and vice versa.

So I think we should put "urn@ietf.org" into the draft as the address 
for review/discussions of namespace proposals, with the understanding 
that this will attain force when the draft is published as an RFC.

Regards,   Martin.