[urn] Re: FW: Request to IANA for formal URN assignment (Bank VTB)

Peter Saint-Andre <stpeter@stpeter.im> Wed, 13 November 2024 21:16 UTC

Return-Path: <stpeter@stpeter.im>
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 3421BC169439 for <urn@ietfa.amsl.com>; Wed, 13 Nov 2024 13:16:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=stpeter.im header.b="TSCCvndI"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="PUlTDUPe"
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 PCXiY_6C6opB for <urn@ietfa.amsl.com>; Wed, 13 Nov 2024 13:16:37 -0800 (PST)
Received: from fout-b1-smtp.messagingengine.com (fout-b1-smtp.messagingengine.com [202.12.124.144]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAAE8C15107F for <urn@ietf.org>; Wed, 13 Nov 2024 13:16:37 -0800 (PST)
Received: from phl-compute-11.internal (phl-compute-11.phl.internal [10.202.2.51]) by mailfout.stl.internal (Postfix) with ESMTP id D9045114019F; Wed, 13 Nov 2024 16:16:36 -0500 (EST)
Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-11.internal (MEProxy); Wed, 13 Nov 2024 16:16:37 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1731532596; x=1731618996; bh=a1quDKTViH2WgR6E0njz+e/zBqEOVnc39ylkXpYxdDQ=; b= TSCCvndIu0dC2d2eRWfym8bbmYamD+Lo1uwFcLFhTEBrIcV4QYvO5wuKRKHVBr4d 4X/O0enNX/MgJfZ82exZpylOjYHoXpKKyt2ZEjaznBGMMVmj8bfhSkSmh/y5vg1m HhS1KRX5h0X3UXevgb3QIHolzb9VgO81NOoSeldq95DJzbCMuekdiDWQoX5ZDX1j TIIvyJtd+lVZzzdy45D8IGkxriB1ivJb06lu536llrnE1w7e+vBQZZnHYW3LGi24 AJWqzQ1dXHohyMSpTrtHHfy2UePpfcZQgTSlre9Y3qX9f0q/Q7Lp9smvKbEtKlOz HKMdrtg2k33nCq6ybJTkkw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1731532596; x= 1731618996; bh=a1quDKTViH2WgR6E0njz+e/zBqEOVnc39ylkXpYxdDQ=; b=P UlTDUPeycXV9J3b8csVRrZURw67OVxuZHTCMTnkDByyoP9Br8c135iFpMRY10Zi9 eSN+CuaMWcjIQiRgVGe5XqOWaFTOCSPqLjhOHVFGVJ9aAjKYQaPZnlsUDN6T97vU Eh7pu9HzG++RwKrv108HClGHVdaeOwXldNDhB0LQH6c/JGzgniZJ4dGC5FeeaIYD VCqOcWFCQ3Pd1t6HG+fDxb/CJbN6pAm8iiXCsIH9avv7uXH5znXdrNU9X/CmXRxY xNsRhZEit+SZnIiVuHegnnSSxmDrHweffzRAxgW6mbve6AzEEwrDtGOnqKjQe2nO n3sl45RiOadKSrJ+tCnvg==
X-ME-Sender: <xms:Mxc1Z6Uh9vBIf3zsi6qzxkFQ4h8V8bR2Whlzs1hjAwzVHCfwk3k7OQ> <xme:Mxc1Z2mtGB0ArUAjc1dhOwXx8QKTXQSxfanch2556RY8xn35M1s4fGk1ByKkP1EIM _21JOToCgYw7LcIhg>
X-ME-Received: <xmr:Mxc1Z-aDenF09y3hSfwsAS18LJoXZWjBNmzuHZUsNH1IrgX1lMAE7CJUostnR6Rv>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrvddtgddugeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnh htshculddquddttddmnecujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtvdej necuhfhrohhmpefrvghtvghrucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhessh htphgvthgvrhdrihhmqeenucggtffrrghtthgvrhhnpeehieeuvdeikefgtdejvedutdeg kefhkeeihfeuteetfedvjeeifeehhefgffefleenucffohhmrghinhepihgvthhfrdhorh hgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepshht phgvthgvrhesshhtphgvthgvrhdrihhmpdhnsggprhgtphhtthhopeegpdhmohguvgepsh hmthhpohhuthdprhgtphhtthhopeifohhrlhgvhiesrghrihgrughnvgdrtghomhdprhgt phhtthhopegrhigrrhihghhinhesihhnnhhordhtvggthhdprhgtphhtthhopehurhhnse hivghtfhdrohhrghdprhgtphhtthhopehsthhpvghtvghrsehsthhpvghtvghrrdhimh
X-ME-Proxy: <xmx:Mxc1ZxU5lrTBaVVSU7BfW0AOAp6vej3ks6KHvJsNUzT1dzO8ayhRrg> <xmx:Mxc1Z0nw3uxOgducw7ztTFZ4vIa-NmoWJKlH5He1nmeA5_QY5HTDjw> <xmx:Mxc1Z2eBAHmyUbSMj-gQeiRWbppMmi9qJdE0a-pvGW2j-sW_SuWLyQ> <xmx:Mxc1Z2E0CwlU6hPtKw0IgTENzjy0BYQ2SN-Ej8rb9qZk2XEwKPHXwQ> <xmx:NBc1Z1CO8EV9dMJlwLgAAZLzFexH_-R8lQggInGFjESE5FFVlTorDjMR>
Feedback-ID: i24394279:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 13 Nov 2024 16:16:34 -0500 (EST)
Message-ID: <1294fde5-23d2-4370-a2b0-aa942366b85e@stpeter.im>
Date: Wed, 13 Nov 2024 14:16:33 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: "Dale R. Worley" <worley@ariadne.com>, Ярыгин Анатолий Александр ович <AYArygin@inno.tech>
References: <87h68a6fqh.fsf@hobgoblin.ariadne.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <87h68a6fqh.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: SH45MDIKDGDAHQ3YNI7LDU573COLEUHA
X-Message-ID-Hash: SH45MDIKDGDAHQ3YNI7LDU573COLEUHA
X-MailFrom: stpeter@stpeter.im
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-urn.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: urn@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [urn] Re: FW: Request to IANA for formal URN assignment (Bank VTB)
List-Id: "Discussion about Uniform Resource Names (URNs)." <urn.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/lKS-JHiDuJaiIjny92Y_ZtQYf2w>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Owner: <mailto:urn-owner@ietf.org>
List-Post: <mailto:urn@ietf.org>
List-Subscribe: <mailto:urn-join@ietf.org>
List-Unsubscribe: <mailto:urn-leave@ietf.org>

On 11/13/24 1:28 PM, Dale R. Worley wrote:

Dale, I agree with your first two points. On the third point, see below.

> 3. Of the 90 or so formal URN namespace registrations, it does not
> appear that any others are registered by a private business.  Almost all
> are registered by standards or trade organizations.  RFC 8141 section
> 5.1 suggests that this is intentional:
> 
>     The intent
>     is that, while the community of those who might actively use the URNs
>     assigned within that URN namespace might be small, the potential use
>     of names within that URN namespace is open to any user on the
>     Internet.  Formal URN namespaces might be appropriate even when some
>     aspects are not fully open.  For example, a URN namespace might make
>     use of a fee-based, privately managed, or proprietary registry for
>     assignment of URNs in the URN namespace.  However, it might still
>     benefit some Internet users if the associated services have openly
>     published names.
> 
> On the other hand, there does not appear to be any specific rule against
> a registration that is initially intended to be used almost solely
> within a private business.  And given that there are fewer than 90
> registrations to date, there seems to be no shortage of namespace
> identifiers.  So I recommend that we do not stop this registration due
> to its narrow (initial) intended usage.

You might recall that we had a discussion on this very topic about 10 
years ago, starting here:

https://mailarchive.ietf.org/arch/msg/urn/oU0Q5MLm0qMQjWb2Zh0IaOYoAOo/

One suggestion that emerged from that discussion was to use the tag: URI 
scheme (RFC 4151) where possible. This kind of internal usage within a 
private organization doesn't quite seem appropriate for URNs.

Peter