Re: [urn] Formal request for URN for ITU

worley@ariadne.com (Dale R. Worley) Tue, 03 July 2018 03:08 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1144130ED6 for <urn@ietfa.amsl.com>; Mon, 2 Jul 2018 20:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.685
X-Spam-Level:
X-Spam-Status: No, score=-1.685 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 uuySnK-zamsY for <urn@ietfa.amsl.com>; Mon, 2 Jul 2018 20:08:50 -0700 (PDT)
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C546130DF1 for <urn@ietf.org>; Mon, 2 Jul 2018 20:08:50 -0700 (PDT)
Received: from resomta-ch2-03v.sys.comcast.net ([69.252.207.99]) by resqmta-ch2-12v.sys.comcast.net with ESMTP id aBbmfsMzdwfygaBgPf7cgj; Tue, 03 Jul 2018 03:08:49 +0000
Received: from hobgoblin.ariadne.com ([24.91.37.100]) by resomta-ch2-03v.sys.comcast.net with ESMTPA id aBgOfP2S9iX04aBgPf7vq3; Tue, 03 Jul 2018 03:08:49 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w6338mON009899; Mon, 2 Jul 2018 23:08:48 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w6338lCQ009896; Mon, 2 Jul 2018 23:08:47 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Scott Mansfield <scott.mansfield@ericsson.com>
Cc: urn@ietf.org
In-Reply-To: <CY1PR15MB0235486A2436E18C8F5C92CB8B430@CY1PR15MB0235.namprd15.prod.outlook.com> (scott.mansfield@ericsson.com)
Sender: worley@ariadne.com
Date: Mon, 02 Jul 2018 23:08:47 -0400
Message-ID: <87601x6mo0.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfKv8sP3XbDisZT9qD/YCi4bk+U2VJGOADcX1UCO51qIxk8A14jizCU4gBY9gD/YjB0+kATIglpyffpJrktxvQGWWA5GupW9/jiGBQga4zRsOyDO+wCUq bSm0DsAlIVGxLJmoWqj3vJ2nkPBCA/JT6Y1HK5XobVEEFTvycpm81igl4407ADevU4LmJ+VH5J60HdhGsMWUkxrJEyKhVwC+bKE=
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/vIv-bR7szWjV8VcZUaqp0sSRdQU>
Subject: Re: [urn] Formal request for URN for ITU
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jul 2018 03:08:52 -0000

Scott Mansfield <scott.mansfield@ericsson.com> writes:
> This is a request from International Telecommunication Union (ITU) for
> a namespace.
>
> Please review and provide comments/revisions to ensure clarity and
> focus of the request.  The format of the request is in ID format
> capturing the information requested from Appendix A of RFC 8141.

The registration looks generally good to me.  Some questions are:

   Abstract

   This document describes the Namespace Identifier (NID) 'itu' for
   Uniform Resource Names (URNs) used to identify resources published by
   the ITU (International Telecommunication Union).

The word "published" is used in the Abstract but nowhere else.  All of
the example URNs seem to name either publications or abstract resources
described in publications.  But some thought should be given to whether
"published" is more restrictive that you want to commit to, and if you
want to keep the word, it would probably be better to incorporate it
into section 2.5 ("Purpose").

Section 2.5 describes the purpose of this namespace entirely in terms of
Yang module names.  But it seems likely to me that other purposes will
be found for ITU URNs, and it would be wise to allow the ITU to define
URNs for other types of resources.

This document is referenced four times:

   [4]        ITU, "ITU URN Management", 2017, <http://www.itu.int/en/
              ITU-T/Documents/ITU-URN-Management.pdf>.

This document is an Informative Reference, so the namespace registration
supersedes it, but it would be wise to edit "ITU URN Management" and the
registration to be compatible.  In particular:

(1) The registration states:

       The ITU process is found in the ITU URN Management [4] document.

Although [4] describes the syntax and semantics of URNs, it doesn't seem
to describe any organizational processes.

(2) The document contains two syntax specifications that omit colons
between components that seem to be intended:

    urn:itu:t:rec:{ITU-T-RecommendationNumber}{ITU-T-RecommendationSpecificString}

    {ITU-T-RecommendationType}{ITU-T-RecommendationTypeIdentifier}

Dale