Re: [urn] Request for oneM2M URN Namespace registration

worley@ariadne.com Mon, 21 November 2022 23:27 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 23ECBC157B35 for <urn@ietfa.amsl.com>; Mon, 21 Nov 2022 15:27:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.682
X-Spam-Level:
X-Spam-Status: No, score=-1.682 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_SOFTFAIL=0.665, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HqCuDayCjH4m for <urn@ietfa.amsl.com>; Mon, 21 Nov 2022 15:27:26 -0800 (PST)
Received: from resdmta-c1p-023854.sys.comcast.net (resdmta-c1p-023854.sys.comcast.net [96.102.19.45]) (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 CB648C157B32 for <urn@ietf.org>; Mon, 21 Nov 2022 15:27:26 -0800 (PST)
Received: from resomta-c1p-023413.sys.comcast.net ([96.102.18.230]) by resdmta-c1p-023854.sys.comcast.net with ESMTP id x7xloCghbLUpMxGAFocfqj; Mon, 21 Nov 2022 23:25:23 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1669073123; bh=PBrBD3FDaB0QQU+ycF+fuHPx6kUXwKJD3lJEfpKmA1o=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:Xfinity-Spam-Result; b=ShM5ah7ZYbwNqHJ5OQ/Sv4ahNUEqoRwnj3YycGEUAcGtgR1K1hnuXOpRGlsImqbee 221+tLSY86dPLmdxq9k48D7QPFBcIR1nUsEWJ7TH4X73y0q2Dw+hpOde3J5t+etKTF eEeyTOTqFFbtzChWR0xZnqbakgRHiAxBdcENXxXmRaMkHryvTJz6uQyGLgw1Gub4Hv P3Pi32e5jiOcEDF/qND8uMBD1LRofvQ7ZtaRI9mRk5+UrNzJZkOsJvob81MriC5xn0 1/kwMRJN9GX3uU64GRIfW5Dcq1zOV24a2PMWGctJIaVe4Udlw2iqoCQozyk4/DXJV9 UtzrI8zwvH0tw==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430::c1f3]) by resomta-c1p-023413.sys.comcast.net with ESMTPA id xG9ro3tMhW1DNxG9soU1dr; Mon, 21 Nov 2022 23:25:01 +0000
X-Xfinity-VMeta: sc=0.00;st=legit
Received: from hobgoblin.ariadne.com (localhost [127.0.0.1]) by hobgoblin.ariadne.com (8.16.1/8.16.1) with ESMTPS id 2ALNOuE2334633 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Mon, 21 Nov 2022 18:24:56 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 2ALNOtZ0334630; Mon, 21 Nov 2022 18:24:55 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Miguel Angel Reina Ortega <MiguelAngel.ReinaOrtega=40etsi.org@dmarc.ietf.org>
Cc: urn@ietf.org
In-Reply-To: <PR0P264MB180411AA5B583274D1B2E9528E099@PR0P264MB1804.FRAP264.PROD.OUTLOOK.COM> (MiguelAngel.ReinaOrtega=40etsi.org@dmarc.ietf.org)
Sender: worley@ariadne.com
Date: Mon, 21 Nov 2022 18:24:55 -0500
Message-ID: <87tu2rq4ag.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/OseLIGRKuP6t9x9z4jhun8OslTY>
Subject: Re: [urn] Request for oneM2M URN Namespace registration
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 21 Nov 2022 23:27:31 -0000

> The namespace is now registered:
> 
> https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml

Thanks, Peter, for pushing this through.  I was going to say that I
apologize for not engaging with this proposal, but I see that very early
I recommended fast-tracking it with no objections.

However, there is one place I think the wording could be improved.  I
doubt the registration template can be changed easily at this date, but
the web page
https://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace could be
updated to clarify the intention.  Specifically, it says

    As general rule, the NSS-restoftree is limited to printable ASCII
    character set, unless otherwise specified by the sub-node namespace.

The NSS is part of the URN, and a URN is required to be a sequence of
printable ASCII characters.  So this sentence, read literally, imposes
no new constraint.

Of course, what you mean is that NSS-restoftree is (usually) limited to
not *represent* non-ASCII characters, that is, it does not contain what
are commonly called %-escapes, '"%" <hex> <hex>'.

The question is what is a more accurate, but still clear, statement of
the intention.  Looking at RFC 8141, I see that it refers to RFC 2141 to
specify the syntax, and in RFC 2141 section 2.2 are the rules:

   <NSS>         ::= 1*<URN chars>

   <URN chars>   ::= <trans> | "%" <hex> <hex>

   <trans>       ::= <upper> | <lower> | <number> | <other> | <reserved>

   <hex>         ::= <number> | "A" | "B" | "C" | "D" | "E" | "F" |
                     "a" | "b" | "c" | "d" | "e" | "f"

   [definitions of upper, lower, number, other, and reserved omitted]

So you could accurately say that NSS-restoftree is (usually) limited to
<trans> characters.  But nobody would understand that without a direct
reference to RFC 2141!

Perhaps a better wording is

    As a general rule, unless otherwise specified by the sub-node
    namespace, the NSS-restoftree does not contain %-escapes, and thus
    represents only the printable ASCII character set.
    
Here, I've moved the qualifying "unless ..." earlier in the sentence to
connect it more with "As a general rule".

Dale