Re: ZigBee Alliance "xcl" URN Formal Application

worley@ariadne.com (Dale R. Worley) Thu, 04 August 2016 18:26 UTC

Return-Path: <worley@alum.mit.edu>
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 6E79812D162 for <urn-nid@ietfa.amsl.com>; Thu, 4 Aug 2016 11:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level:
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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 cdN2BfJ574rj for <urn-nid@ietfa.amsl.com>; Thu, 4 Aug 2016 11:26:14 -0700 (PDT)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (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 42C3D12B019 for <urn-nid@apps.ietf.org>; Thu, 4 Aug 2016 11:26:14 -0700 (PDT)
Received: from resomta-ch2-01v.sys.comcast.net ([69.252.207.97]) by resqmta-ch2-08v.sys.comcast.net with SMTP id VNLNb642h84vjVNLRblqkL; Thu, 04 Aug 2016 18:26:13 +0000
Received: from hobgoblin.ariadne.com ([73.100.16.189]) by comcast with SMTP id VNLQbJZZPXOkgVNLRb4ACa; Thu, 04 Aug 2016 18:26:13 +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 u74IQBsd010531; Thu, 4 Aug 2016 14:26:12 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id u74IQBSg010528; Thu, 4 Aug 2016 14:26:11 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Victor Berrios <vberrios@zigbee.org>
Subject: Re: ZigBee Alliance "xcl" URN Formal Application
In-Reply-To: <D025AB24-7A0E-49A1-8722-6BBC428BE31E@zigbee.org> (vberrios@zigbee.org)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Thu, 04 Aug 2016 14:26:11 -0400
Message-ID: <87eg64crwc.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfKKXPxzUUHP8mzpbLTjSTlayWKxJVBnAgyECQi3E6HpLhYoaOkB2pJrjeaGog9MoxlsHrqXTXtC3ncrdY4fRaUwkl1Ohy+gWneBFK1oJpGJSldoD1+VN uILlymQPPXeKy691JpXgQW4OK5duTElPC4n2OLcdsuxAOjwAUOJ7wzvEynxBY49e81gFODM2pw/PtIjCHMUmj0pbqOtYSK9/tbw=
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn-nid/YXMOYKWgr8YzMPH8E1h3SXNXM7Y>
Cc: urn-nid@apps.ietf.org
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 04 Aug 2016 18:26:15 -0000

>From ZigBe_Alliance-zcl-urn-application-FINAL-03Aug16.txt:

I see that "Declaration of syntactic structure" says:

      URNs assigned by the ZigBee Alliance will have the following
      structure based on the organizational structure of the resources
      specified in the ZigBee Alliance specifications:

        urn:zcl:<NSS>

      where the syntax of "<NSS>" is specified in Section 2.2 of the URN
      Syntax requirements [RFC2141].

whereas "Rules for Lexical Equivalence" says:

      The "<NSS>" is case-sensitive. Only lower case letters are
      considered valid.

These are not consistent, since <NSS> allows upper-case letters (both as
part of %-escapes and in their own right).

If you really mean to forbid upper-case letters, you need to state that
in "syntactic structure".  E.g.,

        urn:zcl:<NSS>

      where the syntax of "<NSS>" is specified in Section 2.2 of the URN
      Syntax requirements [RFC2141], except that it may not contain
      upper-case letters.

Also, the "urn" and namespace parts are case-insensitive (RFC 2141,
sections 2 and 2.1), so "equivalence" should be updated to, perhaps

       The "<NSS>" portion of URNs is compared as a character string.

Dale