
From k.ohara@applic.or.jp  Thu Jan 13 02:26:04 2011
Return-Path: <k.ohara@applic.or.jp>
X-Original-To: urn-nid@core3.amsl.com
Delivered-To: urn-nid@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78A243A6B62 for <urn-nid@core3.amsl.com>; Thu, 13 Jan 2011 02:26:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.526
X-Spam-Level: ***
X-Spam-Status: No, score=3.526 tagged_above=-999 required=5 tests=[AWL=-1.410,  BAYES_40=-0.185, FAKE_REPLY_C=2.012, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_110=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RXyOm9BIG6FQ for <urn-nid@core3.amsl.com>; Thu, 13 Jan 2011 02:26:02 -0800 (PST)
Received: from uni2.genesis.co.jp (uni2.genesis.co.jp [202.238.194.131]) by core3.amsl.com (Postfix) with SMTP id 0163B3A6B60 for <urn-nid@apps.ietf.org>; Thu, 13 Jan 2011 02:26:01 -0800 (PST)
Received: (qmail 31103 invoked by alias); 13 Jan 2011 19:28:21 +0900
Received: from ip138.flip1.remote.ne.jp (HELO c406) (206.3.23.138) by smtp.applic.or.jp with SMTP; 13 Jan 2011 19:28:21 +0900
Message-ID: <7A9BC444E4714E11A65199051BC79BFF@c406>
From: "Kazuaki Ohara" <k.ohara@applic.or.jp>
To: "Dirk-Willem van Gulik" <dirkx@webweaving.org>
Subject: Re: A formal NID registration request
Date: Thu, 13 Jan 2011 19:28:17 +0900
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_00F2_01CBB358.07959A90"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Cc: urn-nid@apps.ietf.org
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 13 Jan 2011 10:26:04 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_00F2_01CBB358.07959A90
Content-Type: text/plain;
	format=flowed;
	charset="iso-2022-jp";
	reply-type=original
Content-Transfer-Encoding: 7bit

Dear Mr. Gulik,

Our apologies for this delayed response and thanks for your review of our Internet-Draft.

On January 12, 2011 We submitted the I-D 'A Uniform Resource Name (URN) Formal Namespace
for the Local Government ICT Platform Project in Japan' to IETF, which is the attached text file.


> I do note though that some of the URLs are (already) broken - and it may be an idea
> to either stabilise these URLs or to publish the information as a standard
> (e.g. at JSA/JIS or as an IETF draft).

We checked all the URLs and made them stabilised for reference at anytime.


> As an aside - I am a bit surprised by the 'file' concept below - looking at some of
> the documentation this 'file' is almost a document identifier -
> i.e. slightly more abstract than an actual file. But that is probably me misunderstanding.

I'm sorry lack of my English expression skill might have confused you a little.
We want to indicate just what kind of type the (document) file is and we make it more clear as follows.

<the classification of the file> is "schema" | "wsdl" | "bpel"
                               ->
<the classification of the document type> is "schema" | "wsdl" | "bpel"


Best regards,
Kazuaki Ohara


----- Original Message ----- 
From: "Dirk-Willem van Gulik" <dirkx@webweaving.org>
To: "Patrik Faltstrom" <patrik@frobbit.se>
Cc: <urn-nid@apps.ietf.org>; "Kazuaki Ohara" <k.ohara@applic.or.jp>
Sent: Thursday, December 16, 2010 7:23 PM
Subject: Re: A formal NID registration request



On 16 Dec 2010, at 08:04, Patrik F.ANdltstrNvm wrote:

> I have not seen anyone voluntarily review this request for a URN namespace. Maybe I have missed some email.

This application meets most of the requirements from RFC3406 with ease. Missing are some of the less objective qualifications from 
section 3.3. However these are adequately addressed in the supplement/PDF - and are a core capability of these types of governmental 
institutions.

I do note though that some of the URLs are (already) broken - and it may be an idea to either stabilise these URLs or to publish the 
information as a standard (e.g. at JSA/JIS or as an IETF draft).

So I see no reason for this RQ not to go forward.

As an aside - I am a bit surprised by the 'file' concept below - looking at some of the documentation this 'file' is almost a 
document identifier - i.e. slightly more abstract than an actual file. But that is probably me misunderstanding.

Thanks,

Dw. 

------=_NextPart_000_00F2_01CBB358.07959A90
Content-Type: text/plain;
	format=flowed;
	name="draft-applic-urn-00.txt";
	reply-type=original
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="draft-applic-urn-00.txt"


                                                                         =
           Kazuaki Ohara
             The Association for Promotion of Public Local Information =
and Communication (APPLIC)
                                                                         =
        January 12, 2011


A Uniform Resource Name (URN) Formal Namespace for the Local Government =
ICT Platform Project in Japan


Abstract

 This document describes the Namespace Idendifier (NID) 'applic' for =
Uniform Resource Name (URN)
 that is produced by the Association for Promotion of Public Local =
Information and Communication (APPLIC)
 which consists of local governments, private companies and academic =
experts in Japan.

Status of this Memo

 This Internet-Draft is submitted in full conformance with the =
provisions of RFC 3406
 published on October 2002 at http://tools.ietf.org/html/rfc3406.

Copyright Notice

 Copyright (c) 2011 IETF Trust and the persons identified as the =
document authors.
 All rights reserved.



1. Introduction

In order to realize the improvement of public services for citizens and =
the reduction of ICT costs
for local governments in japan, APPLIC has started the Local Government =
ICT Platform project(*1)
according to one of the Japanese government policies(*2).

In this project APPLIC has set the standard specifications for various =
services
and exchanged data items between local governments, between local =
government and
private enterprise, which are based on the concept of SOA, and has =
published them(*3).
(and will upgrade them when necessary.)

The XML schemas and WSDL files on the services also are included in the =
specifications,
and NamespaceID on them has to be registered formaly and to be unique.

(*1)Reference to the document "Local Government ICT Platform", on the =
following URL.
    http://www.applic.or.jp/tech/urn/Local_Government_ICT_Platform.pdf
(*2)Reference to page 12 of the document "Outline of Japan's =
Info-Communications Policies", published as follows.
    http://www.soumu.go.jp/menu_news/kouhoushi/pdf/060530-e_1.pdf
(*3)The latest version at 2010/10 is published on the following page.
    http://www.applic.or.jp/URN/APPLIC-0009-2010/



2. Specification Template

   NamespaceID:  "applic"


Registration Information:

   Version 1
   Date:  2011-01-12


Declared registrant of the namespace:

   Name(Organization): The Association for Promotion of Public Local =
Information and Communication (APPLIC)
   Address: 2-9-4,Torano-mon,Minato-ward,Tokyo 105-0001,Japan
   E-mail: tech-ans@applic.or.jp
   URL: http://www.applic.or.jp/


Declaration of syntactic structure:

  The identifier structure is as follows:

  urn: <namespace ID>:xmlns:pf:<the classification of the =
specification>:<the classification of the document type>:<the =
information of the=20
specification release>

 <namespace ID> is "applic"

 <the classification of the specification> is "dis" | "gis" | "lgxml" | =
"interop" | "common"

 <the classification of the document type> is "schema" | "wsdl" | "bpel"

 <the information of the specification release time> is YYYY-**

      YYYY : the year of the specification release
       **  : the time of the specification release in the year ,which is =
from "01" to "99"


Relevant ancillary documentation :

   The specification documents and XML schemas are published on the =
following site:

   http://www.applic.or.jp/

   (e.g. The latest version at 2010/10 is published on the following =
page.)

   ( http://www.applic.or.jp/URN/APPLIC-0009-2010/ )


Identifier uniqueness considerations:

=81@=81@URN identifiers are assigned uniquely.
      -- APPLIC assigns them to at most one resource according to above =
syntactic structure, and do not reassign.

=81@=81@=81@
Identifier persistence considerations:

=81@=81@All identifier assignments are permanent by APPLIC.


Process of identifier assignment:

=81@=81@The assignment process is completely closed one under APPLIC =
control.


Process for identifier resolution:

=81@=81@APPLIC will maintain lists of assigned identifiers on its web =
pages or documents. (http://www.applic.or.jp/)


Rules for Lexical Equivalence:

=81@=81@The entire URN is case-insensitive.

Conformance with URN Syntax:

=81@=81@No special considerations.


Validation mechanism:

=81@=81@No special considerations.


Scope:

=81@=81@Global.



3. Example

  (The following examples are not to be real.)

  urn:applic:xmlns:pf:lgxml:wsdl:2016-01
  urn:applic:xmlns:pf:common:schema:2020-03



4. Namespace Considerations

 In order to guarantee the uniqueness of URNs, the assignment process of =
them is completely closed one under APPLIC control
 and in fact APPLIC assigns them according to the above "Declaration of =
syntactic structure" in "2. Specification Template"
 and publishes them.



5. Community Considerations

 In Japan software development companies implement the functions of the =
Local Government ICT Platform
 specifications (including XML schemas and WSDL files) into their =
software products for local governments
 and release them. Local governments need to design their services by =
using them in order to communicate
 with each other on the Local Government ICT Platform.
 The software products in accordance with the specifications can be =
passed by APPLIC and published
 on the following APPLIC web page.
 http://www.applic.or.jp/pf/entry/unit.html.

 Any organization such as local governments and private enterprises will =
be entitled to access the namespace and its
 associated application, registration and resolution services.
 The primary "applic" namespace usage is to identify information =
resources, such as XML messages, according to
 the Local Government ICT Platform specifications.



6. IANA Considerations

 This document includes a URN NID registration for APPLIC for entry in =
the IANA registry of URN NIDs
 (see [RFC2434] for more information).

 (APPLIC indicates in the document "Standard Specification regarding =
Platform Communication",
  one of the Local Government ICT Platform documents,
  that The NamespaceID "applic" is entered into the IANA registry of URN =
NIDs.)



7. Security Considerations

 There are no additional security considerations except those of the use =
and resolution of URNs in general.



8. References

8.1. Normative References

[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, =
"Uniform Resource Names (URN) Namespace Definition Mechanisms",=20
BCP 66, RFC 3406, October 2002.


8.2. Informative References

[RFC4350] F.Hendrikx, C.Wallis, (New Zealand Government), "A Uniform =
Resource Names (URN) Namespace for the New Zealand Government",=20
RFC4350, February 2006.

[RFC4617] J.KorniJenko, "A Uniform Resource Name (URN) Formal Namespace =
for the Latvian National Government Integration Project",=20
RFC4617, August 2006.



Author's Address

  Kazuaki Ohara
  The Association for Promotion of Public Local Information and =
Communication (APPLIC)
  2-9-4,Torano-mon,Minato-ward,Tokyo 105-0001,Japan
  E-mail: tech-ans@applic.or.jp
  URL: http://www.applic.or.jp/

------=_NextPart_000_00F2_01CBB358.07959A90--


From sumanth@cablelabs.com  Sun Jan 16 13:42:19 2011
Return-Path: <sumanth@cablelabs.com>
X-Original-To: urn-nid@core3.amsl.com
Delivered-To: urn-nid@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AADC83A6E38 for <urn-nid@core3.amsl.com>; Sun, 16 Jan 2011 13:42:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.329
X-Spam-Level: 
X-Spam-Status: No, score=-0.329 tagged_above=-999 required=5 tests=[AWL=0.134,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oSmKk1rVvBip for <urn-nid@core3.amsl.com>; Sun, 16 Jan 2011 13:42:18 -0800 (PST)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id C8B833A6D87 for <urn-nid@ietf.org>; Sun, 16 Jan 2011 13:42:18 -0800 (PST)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id p0GLioNY014566 for <urn-nid@ietf.org>; Sun, 16 Jan 2011 14:44:50 -0700
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Sun, 16 Jan 2011 14:44:49 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Sun, 16 Jan 2011 14:44:50 -0700
From: Sumanth Channabasappa <sumanth@cablelabs.com>
To: "urn-nid@ietf.org" <urn-nid@ietf.org>
Date: Sun, 16 Jan 2011 14:45:40 -0700
Subject: Submission of URN registration request template (cablelabs)
Thread-Topic: Submission of URN registration request template (cablelabs)
Thread-Index: Acu1xre0M8DB9Ke9RJqUxGr7lR45kA==
Message-ID: <76AC5FEF83F1E64491446437EA81A61F7D20816FBA@srvxchg>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Approved: ondar
X-Mailman-Approved-At: Thu, 20 Jan 2011 08:30:55 -0800
Cc: Eduardo Cardona <e.cardona@cablelabs.com>, Jean-Francois Mule <jf.mule@cablelabs.com>
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 16 Jan 2011 21:42:19 -0000

Folks,

This email is regarding the URN request documented in draft-cardona-cablela=
bs-urn-05, which describes a Namespace Identifier (NID) -- 'cablelabs' -- f=
or URNs used to identify resources published by Cable Television Laboratori=
es, Inc. (CableLabs).

See: http://tools.ietf.org/html/draft-cardona-cablelabs-urn-05

While we received some early review comments (see: http://www.ietf.org/mail=
-archive/web/urn-nid/current/msg01056.html) and incorporated them, we faile=
d to send this formal request as pointed out by Leslie (see: http://www.iet=
f.org/mail-archive/web/urn-nid/current/msg01064.html) and more recently by =
Peter. We apologize for this oversight. Please consider this request and pr=
ovide any further comments or suggestions.

Thanks!
- S (on behalf of the authors)


Here's the completed template, as documented in the I-D:


   Namespace ID:
        cablelabs
=20
   Registration Information:
        registration version number: 1
        registration date: YYYY-MM-DD [RFC Editor: Please replace YYYY-
        MM-DD with the date of approval of this document for publication
        as an RFC.]
=20
   Declared registrant of the namespace:
        Registering organization
           Name: Cable Television Laboratories, Inc.
           Address: 858 Coal Creek Circle, Louisville, CO 80027, USA
        Designated contact
           Role: Manager, Standards
           Email: ietf_standards@cablelabs.com
=20
   Declaration of syntactic structure:
        The Namespace Specific String (NSS) of all URNs that use the
        "cablelabs" NID will have the following structure:
=20
        {CLclass}:{CLClassSpecificString}
=20
        The "CLclass" is a US-ASCII string that conforms to the URN
        syntax requirements specified in [RFC2141] and defines a
        specific class of resource type.  Each class will have a
        specific labeling scheme that is covered by
        "CLClassSpecificString", which also conforms to the naming
        requirements of [RFC2141].
        CableLabs maintains the CableLabs Assigned Names and Numbers
        [CANN] specification that will contain the assignment of
        CableLabs resource classes, and the specific registration values
        assigned for each resource class.
=20
   Relevant ancillary documentation:
        CableLabs publishes information regarding the registered
        resources in the CableLabs' Assigned Names and Numbers
        specification ([CANN]).
=20
   Identifier uniqueness considerations:
        CableLabs will manage resource classes using the "cablelabs" NID
        and will be the authority for managing resources and subsequent
        strings associated.  CableLabs is expected to guarantee the
        uniqueness of the strings themselves or it may permit secondary
        responsibility for certain defined resources.
        CableLabs could allow the use of experimental type values for
        testing purposes only.  Note that using experimental types may
        create collisions as multiple users may use the same values for
        resources and specific strings.
=20
   Identifier persistence considerations:
        CableLabs will update the CableLabs' Assigned Names and Numbers
        specification (ref: [CANN]) to document the registered resources
        that use the "cablelabs" NID.
=20
   Process of identifier assignment:
        CableLabs will provide procedures for registration of each type
        of resource that it maintains.  Each such resource may have
        three types of registration activities:
           1.  Registered values associated with CableLabs documents or
           services
           2.  Registration of values or sub-trees to other entities
           3.  Name models for use in experimental purposes
=20
   Process for identifier resolution:
        The namespace is not listed with a resolution discovery system;
        this is not applicable for this URN registration.
=20
   Rules for Lexical Equivalence:
        No special considerations; the rules for lexical equivalence of
        [RFC2141] apply.
=20
   Conformance with URN Syntax:
        No special considerations.
=20
   Validation mechanism:
        None specified.  URN assignment will be handled by procedures
        implemented in support of CableLabs activities.
=20
   Scope:
        Global

From ted.ietf@gmail.com  Thu Jan 20 08:52:25 2011
Return-Path: <ted.ietf@gmail.com>
X-Original-To: urn-nid@core3.amsl.com
Delivered-To: urn-nid@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A7C73A713A for <urn-nid@core3.amsl.com>; Thu, 20 Jan 2011 08:52:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.244
X-Spam-Level: 
X-Spam-Status: No, score=-3.244 tagged_above=-999 required=5 tests=[AWL=0.355,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PGPYPNZc3KAQ for <urn-nid@core3.amsl.com>; Thu, 20 Jan 2011 08:52:23 -0800 (PST)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id 3025D3A7132 for <urn-nid@ietf.org>; Thu, 20 Jan 2011 08:52:23 -0800 (PST)
Received: by qyj19 with SMTP id 19so842394qyj.10 for <urn-nid@ietf.org>; Thu, 20 Jan 2011 08:55:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=KfNtweeZasBAoIH7fiszAHBvJYAB/9gLLDjmy2YIf0s=; b=aTzmOUnKMxpZOj7+dwPC2/uXzS7i8uamHz7u/VL5HsJar0UOhE59DA5dMSBbuklEpI iS+v0RC94+7BhWf8a5MfzSyKOU8ttMbSqxSbg38bqQAQ2vwyyk5Np84iR+JjSr+02Cw4 EP8c1VuJtUxXqJWySJQ4mdcyIaCjii32x8hI4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=flEg4ljzjvVKKYkauPWPUKsThcjr0dOGpvap3oZq/FFesLtXP9guLU7zJQ9YzcUmKe /mFMWLpI3I7OyTRXoMZ7YZope4Yfxo5xQOVpfdQV8rEb1F+5FyUZoBWii5W8cFVKZBDL pFuxTu2zRQLh2x3HHu5Lbhb5eAaKYnMV4yQGs=
MIME-Version: 1.0
Received: by 10.229.109.213 with SMTP id k21mr1968223qcp.3.1295542506010; Thu, 20 Jan 2011 08:55:06 -0800 (PST)
Received: by 10.229.230.138 with HTTP; Thu, 20 Jan 2011 08:55:05 -0800 (PST)
In-Reply-To: <76AC5FEF83F1E64491446437EA81A61F7D20816FBA@srvxchg>
References: <76AC5FEF83F1E64491446437EA81A61F7D20816FBA@srvxchg>
Date: Thu, 20 Jan 2011 08:55:05 -0800
Message-ID: <AANLkTi=sn2QtMLcbtPqyA5OP8OC3qDNnBu0_qpmZzLBA@mail.gmail.com>
Subject: Re: Submission of URN registration request template (cablelabs)
From: Ted Hardie <ted.ietf@gmail.com>
To: Sumanth Channabasappa <sumanth@cablelabs.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Eduardo Cardona <e.cardona@cablelabs.com>, "urn-nid@ietf.org" <urn-nid@ietf.org>, Jean-Francois Mule <jf.mule@cablelabs.com>
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 20 Jan 2011 16:52:25 -0000

Howdy,

The extracted registration below doesn't reflect a community
considerations sections.  It is in the draft, with the following text:

5. Community Considerations


   The CableLabs specifications are publicly available or licensed to
   manufacturers on a nondiscriminatory basis.  CableLabs will maintain
   the allocation of resources for the "cablelabs" NID and maintain
   updated the corresponding specifications where those resources are
   referenced or used.

It might be useful to document whether the CANN specification itself will b=
e
publicly available or whether it will under license, if that data is known.

regards,

Ted Hardie

On Sun, Jan 16, 2011 at 1:45 PM, Sumanth Channabasappa
<sumanth@cablelabs.com> wrote:
> Folks,
>
> This email is regarding the URN request documented in draft-cardona-cable=
labs-urn-05, which describes a Namespace Identifier (NID) -- 'cablelabs' --=
 for URNs used to identify resources published by Cable Television Laborato=
ries, Inc. (CableLabs).
>
> See: http://tools.ietf.org/html/draft-cardona-cablelabs-urn-05
>
> While we received some early review comments (see: http://www.ietf.org/ma=
il-archive/web/urn-nid/current/msg01056.html) and incorporated them, we fai=
led to send this formal request as pointed out by Leslie (see: http://www.i=
etf.org/mail-archive/web/urn-nid/current/msg01064.html) and more recently b=
y Peter. We apologize for this oversight. Please consider this request and =
provide any further comments or suggestions.
>
> Thanks!
> - S (on behalf of the authors)
>
>
> Here's the completed template, as documented in the I-D:
>
>
> =A0 Namespace ID:
> =A0 =A0 =A0 =A0cablelabs
>
> =A0 Registration Information:
> =A0 =A0 =A0 =A0registration version number: 1
> =A0 =A0 =A0 =A0registration date: YYYY-MM-DD [RFC Editor: Please replace =
YYYY-
> =A0 =A0 =A0 =A0MM-DD with the date of approval of this document for publi=
cation
> =A0 =A0 =A0 =A0as an RFC.]
>
> =A0 Declared registrant of the namespace:
> =A0 =A0 =A0 =A0Registering organization
> =A0 =A0 =A0 =A0 =A0 Name: Cable Television Laboratories, Inc.
> =A0 =A0 =A0 =A0 =A0 Address: 858 Coal Creek Circle, Louisville, CO 80027,=
 USA
> =A0 =A0 =A0 =A0Designated contact
> =A0 =A0 =A0 =A0 =A0 Role: Manager, Standards
> =A0 =A0 =A0 =A0 =A0 Email: ietf_standards@cablelabs.com
>
> =A0 Declaration of syntactic structure:
> =A0 =A0 =A0 =A0The Namespace Specific String (NSS) of all URNs that use t=
he
> =A0 =A0 =A0 =A0"cablelabs" NID will have the following structure:
>
> =A0 =A0 =A0 =A0{CLclass}:{CLClassSpecificString}
>
> =A0 =A0 =A0 =A0The "CLclass" is a US-ASCII string that conforms to the UR=
N
> =A0 =A0 =A0 =A0syntax requirements specified in [RFC2141] and defines a
> =A0 =A0 =A0 =A0specific class of resource type. =A0Each class will have a
> =A0 =A0 =A0 =A0specific labeling scheme that is covered by
> =A0 =A0 =A0 =A0"CLClassSpecificString", which also conforms to the naming
> =A0 =A0 =A0 =A0requirements of [RFC2141].
> =A0 =A0 =A0 =A0CableLabs maintains the CableLabs Assigned Names and Numbe=
rs
> =A0 =A0 =A0 =A0[CANN] specification that will contain the assignment of
> =A0 =A0 =A0 =A0CableLabs resource classes, and the specific registration =
values
> =A0 =A0 =A0 =A0assigned for each resource class.
>
> =A0 Relevant ancillary documentation:
> =A0 =A0 =A0 =A0CableLabs publishes information regarding the registered
> =A0 =A0 =A0 =A0resources in the CableLabs' Assigned Names and Numbers
> =A0 =A0 =A0 =A0specification ([CANN]).
>
> =A0 Identifier uniqueness considerations:
> =A0 =A0 =A0 =A0CableLabs will manage resource classes using the "cablelab=
s" NID
> =A0 =A0 =A0 =A0and will be the authority for managing resources and subse=
quent
> =A0 =A0 =A0 =A0strings associated. =A0CableLabs is expected to guarantee =
the
> =A0 =A0 =A0 =A0uniqueness of the strings themselves or it may permit seco=
ndary
> =A0 =A0 =A0 =A0responsibility for certain defined resources.
> =A0 =A0 =A0 =A0CableLabs could allow the use of experimental type values =
for
> =A0 =A0 =A0 =A0testing purposes only. =A0Note that using experimental typ=
es may
> =A0 =A0 =A0 =A0create collisions as multiple users may use the same value=
s for
> =A0 =A0 =A0 =A0resources and specific strings.
>
> =A0 Identifier persistence considerations:
> =A0 =A0 =A0 =A0CableLabs will update the CableLabs' Assigned Names and Nu=
mbers
> =A0 =A0 =A0 =A0specification (ref: [CANN]) to document the registered res=
ources
> =A0 =A0 =A0 =A0that use the "cablelabs" NID.
>
> =A0 Process of identifier assignment:
> =A0 =A0 =A0 =A0CableLabs will provide procedures for registration of each=
 type
> =A0 =A0 =A0 =A0of resource that it maintains. =A0Each such resource may h=
ave
> =A0 =A0 =A0 =A0three types of registration activities:
> =A0 =A0 =A0 =A0 =A0 1. =A0Registered values associated with CableLabs doc=
uments or
> =A0 =A0 =A0 =A0 =A0 services
> =A0 =A0 =A0 =A0 =A0 2. =A0Registration of values or sub-trees to other en=
tities
> =A0 =A0 =A0 =A0 =A0 3. =A0Name models for use in experimental purposes
>
> =A0 Process for identifier resolution:
> =A0 =A0 =A0 =A0The namespace is not listed with a resolution discovery sy=
stem;
> =A0 =A0 =A0 =A0this is not applicable for this URN registration.
>
> =A0 Rules for Lexical Equivalence:
> =A0 =A0 =A0 =A0No special considerations; the rules for lexical equivalen=
ce of
> =A0 =A0 =A0 =A0[RFC2141] apply.
>
> =A0 Conformance with URN Syntax:
> =A0 =A0 =A0 =A0No special considerations.
>
> =A0 Validation mechanism:
> =A0 =A0 =A0 =A0None specified. =A0URN assignment will be handled by proce=
dures
> =A0 =A0 =A0 =A0implemented in support of CableLabs activities.
>
> =A0 Scope:
> =A0 =A0 =A0 =A0Global
>
