Re: [dispatch] Submission of "URN Namespace for Metaverse Standards Forum Resources"

Rick van Rein <rick@openfortress.nl> Tue, 19 December 2023 23:17 UTC

Return-Path: <vanrein@vanrein.org>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79954C23960A for <dispatch@ietfa.amsl.com>; Tue, 19 Dec 2023 15:17:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.678
X-Spam-Level:
X-Spam-Status: No, score=-0.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
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 0giyBgFR1aes for <dispatch@ietfa.amsl.com>; Tue, 19 Dec 2023 15:17:28 -0800 (PST)
Received: from fame.vanrein.org (2a02-58-157-9b00--7.ip6.tweak.nl [IPv6:2a02:58:157:9b00::7]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 575B6C239605 for <dispatch@ietf.org>; Tue, 19 Dec 2023 15:17:23 -0800 (PST)
Received: by fame.vanrein.org (Postfix, from userid 1000) id 2043E2F571; Tue, 19 Dec 2023 23:17:20 +0000 (UTC)
Date: Tue, 19 Dec 2023 23:17:20 +0000
From: Rick van Rein <rick@openfortress.nl>
To: Thomas Stockhammer <tsto@qti.qualcomm.com>
Cc: "dispatch@ietf.org" <dispatch@ietf.org>, "Stephan Wenger (stewe@stewe.org)" <stewe@stewe.org>
Message-ID: <20231219231720.GA9831@openfortress.nl>
Mail-Followup-To: Thomas Stockhammer <tsto@qti.qualcomm.com>, "dispatch@ietf.org" <dispatch@ietf.org>, "Stephan Wenger (stewe@stewe.org)" <stewe@stewe.org>
References: <CYYPR02MB9904A92E67293956B41665D1EE97A@CYYPR02MB9904.namprd02.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Disposition: inline
In-Reply-To: <CYYPR02MB9904A92E67293956B41665D1EE97A@CYYPR02MB9904.namprd02.prod.outlook.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/cyUMFI01WkGNCwbw9P62p7boNDY>
Subject: Re: [dispatch] Submission of "URN Namespace for Metaverse Standards Forum Resources"
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2023 23:17:31 -0000

Hello,

In my humble of the URN namespace, it is intended to pin down specifications under names, with the intent of interoperability of independent implementations.  It is not primarily intended as a system of delegation for URI namespace allocation.

Ref: RFC 8141, Section 6.2, "registrants SHOULD provide a stable specification documenting the URN namespace definition".

Based on this, it seems unfit for the URN space to assign sub-names for something as broad and unspecific as "resources published by" any party.  Exceptions may exist for parties that can forward definitions to an existing naming/numbering system, such as the ISBN or the DOI numbering system, if the target organisation happens to be a standards organisation.

Constructive alternatives to a name scope delegation could be a mixture of
(1) to separately register URN forms for specific formats
(2) since this appears to be specific to one or a few domain names, to use the tag: URI defined in RFC 4151 or perhaps a URL format
(3) use the OID branch for Private Enteriprise Numbers, and possibly use urn:oid: as per RFC 3061.


I hope this is helpful.


Best wishes,
  -Rick