IETF Logo Mail Archive

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

Ярыгин Анатолий Алексан дрович <AYArygin@inno.tech> Tue, 19 November 2024 07:48 UTC

Return-Path: <AYArygin@inno.tech>
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 E6322C1840F1 for <urn@ietfa.amsl.com>; Mon, 18 Nov 2024 23:48:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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_HELO_NONE=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=inno.tech
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 70j_2NKhUxJi for <urn@ietfa.amsl.com>; Mon, 18 Nov 2024 23:47:56 -0800 (PST)
Received: from mx.inno.tech (mx.inno.tech [185.228.49.205]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9F4EC1840E8 for <urn@ietf.org>; Mon, 18 Nov 2024 23:47:53 -0800 (PST)
Received: from ksmg3 (localhost [127.0.0.1]) by mx.inno.tech (Postfix) with ESMTP id 85C1280009; Tue, 19 Nov 2024 10:47:50 +0300 (MSK)
DKIM-Filter: OpenDKIM Filter v2.11.0 mx.inno.tech 85C1280009
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inno.tech; s=s1; t=1732002470; bh=1W0ZI+RsAfGapuWgtjH/zOtjXypKrGC+z24a1aKHsTE=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version:From; b=rsP7AzuJRe0EQhvarhDOLqWXtP3cQV+NSAZsYbQmnuBl4GEPpPrOCTl0rQjfWlIoR sSUYRozfZpY3EZMPAUYIvmdqcHMYoBYWXZz7zaKKP3tRj9PEUOE/t7lzgjPdkEhhEm MQ+VdlVZTFYcoWodGZENtTSZIQDZLlqw7kBUSTEja1aHKyCcI7U4EcgYGm5rr79hq6 QrGP8ELJIQdJhjmREIrP3zn7zHy/EfsRNtja4Z9+tuPa9KoDKpkBqx00JfBUVsjd47 2nFDmG/F0jTtwypA+URmdm9bV4mp6FsbkFZ9a3G9oaVdbOf4bd5F68QlyBP4xRWy1o 5jQ9K+64aQGFQ==
Received: from SEC-DLP-QRNT (unknown [10.0.0.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx.inno.tech (Postfix) with ESMTPS; Tue, 19 Nov 2024 10:47:50 +0300 (MSK)
X-CHECKED: 1
X-CHECKED-RELAY-ID: 3c279d7389fa9528e53a55e18b8e1fb6328980c7
X-Cache: 20241119_104749217_00023782
X-MS-Exchange-Organization-AuthAs: Partner
Received: from MAIL-DC1.inno.local (10.0.115.2) by MAIL-DC1.inno.local (10.0.115.2) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.40; Tue, 19 Nov 2024 10:47:48 +0300
Received: from MAIL-DC1.inno.local ([10.0.115.10]) by MAIL-DC1.inno.local ([10.0.115.10]) with mapi id 15.02.1118.040; Tue, 19 Nov 2024 10:47:48 +0300
From: Ярыгин Анатолий Алексан дрович <AYArygin@inno.tech>
To: "worley@ariadne.com" <worley@ariadne.com>
Thread-Topic: [urn] FW: Request to IANA for formal URN assignment (Bank VTB)
Thread-Index: AQHbOiiF+i0b0yDpoUugPY4af6c69bK+OEPw
Date: Tue, 19 Nov 2024 07:47:48 +0000
Message-ID: <50b301e87447419fb3a149cd893b04a8@inno.tech>
References: <65505344f00e40a2b7b567910226c73b@inno.tech> <871pz8t1ia.fsf@hobgoblin.ariadne.com>
In-Reply-To: <871pz8t1ia.fsf@hobgoblin.ariadne.com>
Accept-Language: ru-RU, en-US
Content-Language: ru-RU
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-si-sent-message-id: C3143D5DD5AA474387687162FE1ACE71
x-siagent-storeuniqueid: 13E3D2CE31F248BC8CB52979FFB96B78
x-originating-ip: [10.0.0.114]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-KSMG-Rule-ID: 5
X-KSMG-Message-Action: skipped
X-KSMG-AntiSpam-Status: not scanned, allowlist
X-KSMG-AntiPhishing: not scanned, allowlist
X-KSMG-LinksScanning: not scanned, allowlist
X-KSMG-AntiVirus: Kaspersky Secure Mail Gateway, version 2.0.1.6960, not scanned, allowlist
X-MailFrom: AYArygin@inno.tech
X-Mailman-Rule-Hits: nonmember-moderation
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-urn.ietf.org-0
Message-ID-Hash: T4FFCM46MLC3JMQJQ4VC4IPMPJFK4A6D
X-Message-ID-Hash: T4FFCM46MLC3JMQJQ4VC4IPMPJFK4A6D
X-Mailman-Approved-At: Tue, 19 Nov 2024 05:04:45 -0800
CC: "urn@ietf.org" <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/mNalq-dnq5SfzljjRqi0hlrzAKg>
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>

Hi.

Thank you, Dale.

It seems to me that with this approach to UID registration for URN, 
the procedure has degenerated and become useless for the wider community, organizations and institutions. 
Enormous opportunities are designed, but are doomed to remain useless like a cursed fig tree... 
We have no problem with this decision, but this triumph of uselessness is regrettable. 
Alas.

Regards,
Anatoliy.
-----Original Message-----
From: worley@ariadne.com <worley@ariadne.com> 
Sent: Tuesday, November 19, 2024 5:13 AM
To: Ярыгин Анатолий Александрович <AYArygin@inno.tech>
Cc: urn@ietf.org
Subject: Re: [urn] FW: Request to IANA for formal URN assignment (Bank VTB)



                                                         <AYArygin@inno.tech> writes:
> Please,
> review the request in attachments.

> Regards,
> Anatoliy Yarygin,

> [IANA URN Registration Request For BANK VTB v1.docx (14kB)]

There has been some discussion about this request on the URN mailing list, including references to discussions held in the past on the URN mailing list.  (See https://mailarchive.ietf.org/arch/msg/urn/oU0Q5MLm0qMQjWb2Zh0IaOYoAOo/
and messages in that thread.)  Some of those messages point to older discussions on the relevant mailing lists.

But the consensus seems to be against granting URN NIDs for namespaces that are intended entirely for use internally to one enterprise.

The suggestion has been made that VTB likely could satisfy its needs within the current URI infrastructure by using "tag" URIs.  URIs have a slightly different syntax and semantics, but the differences aren't usually significant in practice.
https://en.wikipedia.org/wiki/Tag_URI_scheme

In VTB's case, it would settle on a domain name that VTB owns and a particular date on which VTB owned the domain name.  E.g. "vtb.com" and 2024-11-12.  Then VTB can go ahead and use all of the identifiers with the format

    tag:vtb.com,2024-11-12:NSS

where NSS can be any string conforming to the standard NSS syntax -- without any formalities.

Dale

v2.46.0 | Report a Bug | By Email | System Status