Re: Informal URN Namespace Registration Request

Ted Hardie <ted.ietf@gmail.com> Tue, 17 November 2015 17:56 UTC

Return-Path: <ted.ietf@gmail.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 6E2C71B2D49 for <urn-nid@ietfa.amsl.com>; Tue, 17 Nov 2015 09:56:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.473
X-Spam-Level: **
X-Spam-Status: No, score=2.473 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DEAR_SOMETHING=1.973, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_36=0.6, SPF_PASS=-0.001] 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 6ymWPsfYH19Z for <urn-nid@ietfa.amsl.com>; Tue, 17 Nov 2015 09:56:39 -0800 (PST)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B3CE1B2D47 for <urn-nid@apps.ietf.org>; Tue, 17 Nov 2015 09:56:39 -0800 (PST)
Received: by qkas77 with SMTP id s77so5514910qka.0 for <urn-nid@apps.ietf.org>; Tue, 17 Nov 2015 09:56:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bNriwlrdW7UIDgsRjORW6evs8cwnsWBuTOne1fSPPR4=; b=zb8uQaE3pswbv89uufF0/HRQPu+wSwMUIIgqpCL0/klCCgVpMj2Gl+8I/ZTOASYUsG FGaVeCKp1vmk/QAZ5V8POumJ64mLBHgCrr2pIYOpni7eKbPxV5tMm89jf3vN0FPUgMVW fEaiYI04/9BKYVvBrugEkrjEfGnmuF7w9I2XGZsjKmjfVV0TZzlHQDUqAgCtaOjb2gWh U2unwUdJJZuZ1KllsbPM1jqnCWRxIL+D6tRIAaTZAGUTIU/3Qwe8faB1wcSXroPMKnOv fmLu+7MZQSz7qzURhXrErP3I/Wy7sF5fFQPOXuCSFh0xvAkrg2QaOkjdAPxSY7BJhl5q 0UzQ==
MIME-Version: 1.0
X-Received: by 10.55.204.213 with SMTP id n82mr43420446qkl.36.1447782998456; Tue, 17 Nov 2015 09:56:38 -0800 (PST)
Received: by 10.55.115.132 with HTTP; Tue, 17 Nov 2015 09:56:37 -0800 (PST)
In-Reply-To: <564B6169.5030606@uchicago.edu>
References: <564A1BFA.1000309@uchicago.edu> <564B5FAB.80407@andyet.net> <564B6169.5030606@uchicago.edu>
Date: Wed, 18 Nov 2015 02:56:37 +0900
Message-ID: <CA+9kkMA-zLSqHvFBoWgQb9O71R4Y0=q1HtRnvw68UKjqGgEBQQ@mail.gmail.com>
Subject: Re: Informal URN Namespace Registration Request
From: Ted Hardie <ted.ietf@gmail.com>
To: Brendan McCollam <bmccollam@uchicago.edu>
Content-Type: multipart/alternative; boundary=001a1149a17855bee40524c03f04
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn-nid/tpAjry1PRChKoniyKYM4V2b7mYk>
Cc: "mattias@uchicago.edu Lidman" <mattias@uchicago.edu>, "urn-nid@apps.ietf.org" <urn-nid@apps.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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 17 Nov 2015 17:56:40 -0000

On Wed, Nov 18, 2015 at 2:18 AM, Brendan McCollam <bmccollam@uchicago.edu>
wrote:

> We were considering that. Unfortunately we're on a very tight schedule
> with release deadlines before 2016, and we thought that the informal
> registration process might proceed faster.
>
> Is there any process in place for "upgrading" an informal registration to
> a formal one at a later date?
>
>
​That would change the string associated with nid, unfortunately.

Ted​




> Brendan
>
>
> On 11/17/2015 11:11 AM, Peter Saint-Andre wrote:
>
>> On 11/16/15 11:10 AM, Brendan McCollam wrote:
>>
>>> Dear Sir or Madam:
>>>
>>> Please find attached our request for an Informal URN Namespace
>>> Registration, as detailed in RFC3406.
>>>
>>
>> Why not register urn:globus as a formal namespace? It seems strange for
>> all of the URNs to be of the form urn:urn-8:globus:*
>>
>> Peter
>>
>>
>>
>