A request for formal registration of "ucode" as URN

ishikawa <chiaki.ishikawa@ubin.jp> Thu, 22 December 2011 05:37 UTC

Return-Path: <chiaki.ishikawa@ubin.jp>
X-Original-To: urn-nid@ietfa.amsl.com
Delivered-To: urn-nid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E931621F8B42 for <urn-nid@ietfa.amsl.com>; Wed, 21 Dec 2011 21:37:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.83
X-Spam-Level: *
X-Spam-Status: No, score=1.83 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DEAR_SOMETHING=1.605, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e9yOfKKb1lCW for <urn-nid@ietfa.amsl.com>; Wed, 21 Dec 2011 21:37:23 -0800 (PST)
Received: from post.ubin.jp (post.ubin.jp [202.32.0.84]) by ietfa.amsl.com (Postfix) with ESMTP id 3A55A21F8B2B for <urn-nid@apps.ietf.org>; Wed, 21 Dec 2011 21:37:21 -0800 (PST)
Received: from localhost (post [127.0.0.1]) by localhost.ubin.jp (Postfix) with SMTP id 8F5D929AC5C for <urn-nid@apps.ietf.org>; Thu, 22 Dec 2011 14:37:11 +0900 (JST)
Received: from home.intra.ubin.jp (home.intra.ubin.jp [10.129.1.1]) by post.ubin.jp (Postfix) with ESMTP id ED29029AC5C; Thu, 22 Dec 2011 14:37:01 +0900 (JST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by home.intra.ubin.jp (Postfix) with ESMTP id 459E9426501; Thu, 22 Dec 2011 14:37:10 +0900 (JST)
X-Virus-Scanned: amavisd-new at ubin.jp
Received: from home.intra.ubin.jp ([127.0.0.1]) by localhost (home.intra.ubin.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59wh6j6IFdUO; Thu, 22 Dec 2011 14:37:09 +0900 (JST)
Received: from [10.254.225.253] (debian-vbox-ci.ddns.intra.ubin.jp [10.254.225.253]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by home.intra.ubin.jp (Postfix) with ESMTP id 2436B42617D; Thu, 22 Dec 2011 14:37:09 +0900 (JST)
Message-ID: <4EF2C203.4010205@ubin.jp>
Date: Thu, 22 Dec 2011 14:37:07 +0900
From: ishikawa <chiaki.ishikawa@ubin.jp>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: urn-nid@apps.ietf.org
Subject: A request for formal registration of "ucode" as URN
Content-Type: multipart/mixed; boundary="------------080101090002070708010807"
Cc: ISHIKAWA Chiaki <chiaki.ishikawa@ubin.jp>
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 22 Dec 2011 05:58:38 -0000

Dear sirs/madams,

Allow me to introduce myself.

I am Chiaki Ishikawa of YRP Ubiquitous Networking Laboratory.
My office is an executive member of an NPO called T-Engine Forum which,
among other things, administrates uID Center which, in turn, manages
an identifier code system called "ucode".

Here with the request of the team at uID center and the chair of T-Engine
Forum, I am applying for
the formal registration of "ucode".

Attached is the copy of document with the document name which I am trying to
submit to IETF.

	draft-ietf-urnbis-yrpunl-ucode

It is at the initial approval stage:

https://datatracker.ietf.org/submit/status/37780/request/

So I think I am at the initial stage (step 2) of the following procedure.
(Instead of sending the Internet-Draft, I used the the mechanical submission
process since it seems preferred. But I am not entirely sure
when the initial approval stage passes. Hmm ...)

 Formal NID:

      1. Write an Internet-Draft describing the namespace and include
         the registration template, duly completed.  Be sure to include
         "Namespace Considerations", "Community Considerations" and
         "IANA Considerations" sections, as described in Section 4.3.

      2. Send the Internet-Draft to the I-D editor, and send a copy to
         urn-nid@apps.ietf.org for technical review.

      3. Update the Internet-Draft as necessary from comments, and
         repeat steps 2 and 3 as needed.

      4. Send a request to the IESG to publish the I-D as an RFC.  The
         IESG may request further changes (published as I-D revisions)
         and/or direct discussion to designated working groups, area
         experts, etc.

      5. If the IESG approves the document for publication as an RFC,
         send a request to IANA to register the requested NID.

Please feel free to ask me questions.

Thank you in advance for your attention.

I wish you all a pleasant holiday season and a Happy New Year.

Sincerely,
Chiaki Ishikawa