Re: [urn] Registration request for urn:thread:

Peter Saint-Andre <stpeter@stpeter.im> Mon, 22 January 2024 19:43 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 1721DC151536 for <urn@ietfa.amsl.com>; Mon, 22 Jan 2024 11:43:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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="iZdtk0qA"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="JnF9zrcR"
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 7vHImYf5_RjJ for <urn@ietfa.amsl.com>; Mon, 22 Jan 2024 11:43:07 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61A3DC14F616 for <urn@ietf.org>; Mon, 22 Jan 2024 11:43:02 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 820515C0121; Mon, 22 Jan 2024 14:42:57 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Mon, 22 Jan 2024 14:42:57 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h=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=1705952577; x=1706038977; bh=T5k/CbOQfxg1XDrt/UVn4/E84B2zvYujwMuNUpfnPHM=; b= iZdtk0qAw5tx0aFTqe/VkwRhTQPRt/NedTK49zwwt0M3wCoP4Gu2tgW+D1SIrGaf KnGS7uvtw3gxShAlib91Syuc+HMq86C/HJ0aVMI6NjcShOCuu/sifTo4iOOVrPLH PyzAgrJ5mw8HjDu16pvQQdgCYnB/ZSf3dyHNW2OwKnLXf21jDTsPng+gR6VX1E3c 9fEPS56nxNfMAg3i8raCR9xsBXlZ5V0gK62FyES6YWZ+Gu03z1NVD1Y36dW0EIG2 QZTBJO7p9DTXlj10zt6Do3ismvn6DKlm3QVYRbZi8poiFvb545tEYkhXd/It4PAz CtoDpXKYOJCdhCgSjCBsVQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1705952577; x= 1706038977; bh=T5k/CbOQfxg1XDrt/UVn4/E84B2zvYujwMuNUpfnPHM=; b=J nF9zrcRztKJnRqaujnBWpb6g+1Q5iIET5GW/+321V3Qkir90aYx4MhYruhq+3X2E RL5dHlwfeG6vEoR0edZdaFgBPgxvdMpbpEcIbegpkB7T/c4n74b89BGvBkwefLE8 mK13dVKi6bHBQa3w4v2mLmZdRVD1N3T5fFu1JM01N9c51hY918y5Dlf4XwiL06XU M1Onr2+PJIpezQOvVJB1quoEsH8eYoT9DzXk7wERvexhtIcp9BTejKDJW8BB5Twm E98HXVo2g8fc4gEgX9ONBugEsvvF0uWHisrtzTvcweTb/gewwRbhZji8uU4sth+w ZloudXP1MUxT0FzUfnxig==
X-ME-Sender: <xms:QcWuZW3ChFKtgpqti9ZhyT6RRdvTZ9TjgeumRULeOWOOBnSBjCScaw> <xme:QcWuZZHSpnNvSm1ITcZQ4nVdsiKrAsvjk-FhV2EiaFu7QeJ1xq-GKAE_1qw3j_0Xz hvpIqW1p496I_hlCA>
X-ME-Received: <xmr:QcWuZe5FQvLMPD-g5jAAIPkz30En2SgIoPj6ckwABAIbdG4JZtgMAHY-Z6h3eA8v>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdekiedguddviecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpefrvght vghrucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhesshhtphgvthgvrhdrihhmqe enucggtffrrghtthgvrhhnpedvheelkeejjeekieejjeehvdegudffkeffveevhffghfdv vddvvedvfedvtdeuieenucffohhmrghinhepthhhrhgvrggughhrohhuphdrohhrghdpih gvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhf rhhomhepshhtphgvthgvrhesshhtphgvthgvrhdrihhm
X-ME-Proxy: <xmx:QcWuZX0GV9GbSC8-IUYspQuN-Td-g2pwJXPngtpgRKPGHmi9iDyexg> <xmx:QcWuZZHVYe9cSlE9vp-oszlgLge4C978qcCVktNPI0ZtRTwV1ZOR8g> <xmx:QcWuZQ_RGvO3eJWRPMvwN4LkZKkcYUEeFnkthvUAxBuxOFGpxvK7NQ> <xmx:QcWuZXOEp7fMP1SiPBPCnWTLt3jZVftP5d4s7tuVEz1cH_dETLlXVQ>
Feedback-ID: i24394279:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 22 Jan 2024 14:42:56 -0500 (EST)
Message-ID: <c5af069e-1538-443f-900c-eb77f299bf40@stpeter.im>
Date: Mon, 22 Jan 2024 12:42:55 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: Esko Dijk <esko.dijk@iotconsultancy.nl>, "urn@ietf.org" <urn@ietf.org>
References: <DU0P190MB197807533371C3C42A66D841FD752@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
From: Peter Saint-Andre <stpeter@stpeter.im>
Autocrypt: addr=stpeter@stpeter.im; keydata= xsFNBFETDzsBEAC0FOv1N3ZJzIIxN6cKD475KVS9CHDPeYpegcOIPnL5eY1DCHeh/IwS1S7R CePtmiybNoV9FsI4PKUknzXQxA6LVEdAR/LUlhgJKjq+gsgp8lqbEILhg13ecH66HwLS9rar bQkC47T7kL8miIPBFC6E3A4Lq1L+eueO6UcLhKgoYkMxOjdiWrMgKTnVpch5ydLkPm/z0Zo8 zRgqlPuTLeCrXXZYnjHXLVFN2xy04UzOs7P5u5KVfx5Z7uQisr8pXtyLd6SpTZo6SHgKBv15 uz0rqXhsJojiGtOXfWznAjaS5FUOORq9CklG5cMOUAT8TNftv0ktsxaWDL1ELDVQPy1m7mtz o+VREG+0xmU6AjMo/GHblW1UU7MI9yCiuMLsp/HLrFuiosqLVZ85wuLQ2junPe3tK8h15Ucx IXAcpQ1VqIaDQFbeuLOXJTF8YHpHdpHYt/ZM1ll7ZBKGAo8yd7uF7wJ9D3gUazwdz9fFjWV7 oIk7ATwOlFllzmWDn+M2ygbHOGUGMX5hSaa8eDSieiR2QoLdn27Fip7kMBTJ2+GISrfnJTN/ OQvmj0DXXAdxHmu2C4QgmZbkge35n129yzXn9NcqzrGLroV62lL3LgX6cSbiH5i7GgWY6CAP b1pMogV0K475n9FvOSDRiG4QSO5yqKiA3OP5aKrIRp2TNAk4IwARAQABzSZQZXRlciBTYWlu dC1BbmRyZSA8c3RwZXRlckBzdHBldGVyLmltPsLBeQQTAQIAIwUCURMPOwIbAwcLCQgHAwIB BhUIAgkKCwQWAgMBAh4BAheAAAoJEOoGpJErxa2p6bgQAKpxu07cMDOLc4+EG8H19NWXIVVy bOEvfGuHYZaLKkPrhrMZwJiOwBpyISNRt9qzX1eLCVaojaoEVX6kD8MGc5zKFfiJZy3j7lBW l+Ybr7FfXYy2BbAXKx49e1n6ci9LmBrmVfAEaxtDNPITZ9N9oUAb9vS0nrG036EwteEHAveQ vlDjO7lhz6+Cv7lZQgBj9rZ6khfcQ4S3nSCQaKLQ9Iav4fqxI7SfuPKnx6quHX3JNLGnVo3w l+j/foCK0iTrmtHxCI3kc/bx6g32pRjHEPX0ALMBhmzU2uca+TE0zCEC96mgYXAUCwdnCFWy beIEbt6pz65iML13kAVAq0H/GqncnMGN0MbOatnw1Tdz/vkLojIy7QbPcQ0plUFxv5491xPf IrHhOWdRXp6WUt88fcqhT6MHZpVRtusj2ornKVVn+Y0GLsMMCTcrXJRG7Ao1YV72t/pJpzfG WSaaxolxDIZ6B+76jrIhUhiWgo/4nf+DN6BIlCZQ6j6xxjjx462cu02kuhIILTk2pzaMOufT BWx0uJhZk/KP2Fay/41pX7pvVOwRC4uIlKsLnJKLPS7EDa4BUUxENfd/9LqOGwlII8BbSe98 PLMI8sXkcigc3UXMVda9ll0YhQa+lbP1NaszmnBhwuiCsgnPGbImsJuRzgEEgckwP/dNeyr6 MlFMyfaezsFNBFETDzsBEADBzOsEHpUmhkRUjH9Tek87dn5P/Yh/L/HptgCGk40TL/C+kYdk d3HyteMEf061PNmsS/Rq8k37Fu3VODYb9SPYKxtgksKSYUtIkPKvao09K9QNWPqyWuNf0F+i AjVMUudaEVFJ7bHF310RDwLY5IvLeCXxtvG+Vv/i+g77d2WdPDp+zLJ8306C4yBKjSJV8xW0 cn2fd7NviIEN6cNHTsZNDZVMlgYPrxnwSq8GTEPGC7HsLIwGcx3hIe9QjnPw9CpAmQENpDEy WcxgF5uwo2NJECoDswKz1Nb0gfawF3ZIbD+GcLujTu94iJuVg25jATWm9wTgcfZo4UPllRGX dIb8uWwUFQlLQgd4ROLZZtXNGmHIymJrV2crx53gxup+1j0XqhlzKg8xbImWhEfS9oHZkRK8 VHgmWSIt7TNwNir6N5j3lqwWVBhnu6GzF01sKGNySlqNRbd0fqhakCkK71b8ot8tYTcYG5Lg 10z6HTbgQx2UwLthUjqbblDQ+GLmrOhiWklLXRsnlnPMwnEyFePAnsT5tasy2Cn9qjpttNDa h7PB8iFUi9mtTF/XDVgpFaB5G3CDV7Q2NgbAI6g6QhLIAmXzSP635G83mda0TKXHQXHDyLJT Tn+WVFU7t4m4uLt+0DsWU8jXHQWyUTNG9WPUrXhusDUAPHxFCQ/n/lQVBwARAQABwsFfBBgB AgAJBQJREw87AhsMAAoJEOoGpJErxa2pqfgP/ApN+TRu2bBIgaw1dr3AznSSha84DIpXUDh3 udZvQrGbUtz8/mA+e3iZEN/cmmBw2LGlAuQoJNILTZQ318yTP+E5QU7fJH7FVsohUyvrMfyt 3IMA9jg0Z9MuloLezvIjjMfFeNa0ROgDb/ubOT7JQzi1kwN8Lu3lO80HwqBHXEeOLoislUSn ZajRKvITbKWkZ6PHRjlMw1Wk4oIi6VLHgGgj79zzL3uhML2663m7imShvz1QcHTwvyR5i8cZ bNOEkotZyERiA1p7YHuruS+QvTi3ZPoQbnMUB3a7py9d11bw1+w3LiAUGZE/z5hBWOFxYtw+ w/U/Vx0BwJGYlwU3M2W20uEXe+qxz7wnakygKjmLiD2z4njfKjcNCiV3FmXrpmWgADln1c4j fxDh0NrndrsM8FPDf1TMPtOZgFDkKripc9xkZ/25P6xn27oTOHWKcAC0QhxSH+HuVBBRk8Ag F+zAbDZe4/L6+kanSrycIXW+wCzwBq61aWsz2QhhuKjozVkhk4dRG+CfjzAFjnyxwYERn3uX VKQAwTwcdNcTI9RV98IsNrw9Y4lJEAg6CjNPmiD5+EASycqaOuToRSGukr8sOQLWLPyTnez/ aG8Xf7a+fntWzK2HuDYoSDhJJrylWw/lMklOBm4wtMeNA0zcQH6AQV/GzQVQkSGqrLuMVIV/
In-Reply-To: <DU0P190MB197807533371C3C42A66D841FD752@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/Pf8piBeW6N8TkSxiIWMRQ2Ibi4U>
Subject: Re: [urn] Registration request for urn:thread:
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, 22 Jan 2024 19:43:12 -0000

Hallo Esko,

In general we are very supportive of registration requests from 
standards development organizations, so at a high level this seems fine.

However, it's unfortunate that you can provide no insights about the 
form of the URNs that will be generated (e.g., structure, allowable 
characters). As a result, we need to take it on faith that Thread Group 
will do the right thing. Would it be more sensible to make this request 
once the spec update is available?

Peter

On 1/22/24 7:55 AM, Esko Dijk wrote:
> Hi all,
> 
> Below is the RFC 8141 registration template for this request for 
> “urn:thread:”. I’m making this request on behalf of the registrant. Any 
> review comments or questions are welcome!
> 
> A spec update that shows concrete usage of URNs is expected to come 
> later in 2024 – so not available at this time.
> 
> Best regards,
> 
> Esko Dijk
> 
> **
> 
> *URN Namespace Registration for Thread Group, Inc.*
> 
> Namespace Identifier:  thread
> 
> Version:               1
> 
> Date:                  2024-01-22
> 
> Registrant:
> 
>    Name:                Thread Group, Inc.
> 
>    Address:             5000 Executive Parkway, Suite 302
> 
>                         San Ramon, CA 94583
> 
>                         United States of America
> 
>    Website: https://www.threadgroup.org/ <https://www.threadgroup.org/>
> 
>    Contact (general):   help&threadgroup.org
> 
>    Contacts(technical): tom&threadgroup.org
> 
>                         esko.dijk&iotconsultancy.nl
> 
>    Organization Type:   Standards Development Organization (non-profit corp)
> 
>                         (requesting fast-track registration procedure)
> 
> Purpose:
> 
> The Namespace Identifier (NID) "thread" for Uniform Resource Names 
> (URNs) will be used to identify resources, protocol elements, 
> specification elements, or structured data items that are either 1) 
> published by the Thread Group as part of its Thread Specification series 
> of standards, or 2) used in communication between devices implementing 
> the Thread Specification. The "thread" namespace URNs can be used in 
> standardized communication between Thread devices, or in communication 
> between Thread devices and non-Thread devices (e.g. carried over an IPv6 
> communication protocol, over a non-IP wired or wireless link, written 
> form, encoded as physical signals, etc.)
> 
> This communication is typically local to a site (e.g. home or business) 
> but may also be carried over the Internet in the future, for remote 
> management use cases. The main purposes for using URNs for the above 
> functions are interoperability and identifiability: there is a clear 
> semantic definition for each URN provided by the Thread Specification, 
> and the scope/purpose of the URN can be identified from its contents 
> alone. The latter is useful when e.g. scanning a URN in written form, 
> bar code, or as a QR code. Also by using the URN standard the data may 
> be easily handled or transited by third party software/processes that 
> are not necessarily aware of the Thread Specification.
> 
> Syntax:
> 
> The syntax of the URNs complies to the Namespace Specific String (NSS) 
> rules as defined by [RFC 8141]. The Thread Group will operate its own 
> registry for any URNs (including sub-namespaces) within the namespace; 
> and additional requirements for each of the allowed sub-namespaces will 
> be defined by the Thread Specification.
> 
> Any use of r-components, q-components or f-components will also be 
> defined by the Thread Specification and noted in the internal registry. 
> At the time of registration, no such use of components is foreseen yet.
> 
> Assignment:
> 
> Any assignment will be managed by the Technical Committee of the Thread 
> Group based on the rules of engagement as defined for this committee. 
> Assignments are recorded in the internal registry kept by Thread Group. 
> An assignment may consist of a final URN or a URN sub-namespace for a 
> particular purpose.
> 
> Security and Privacy:
> 
> Any registered URNs (or URN sub-namespaces) will not contain 
> privacy-sensitive information about persons such as names, addresses, or 
> personal data. URNs used in communication within designated 
> sub-namespaces may contain privacy-sensitive information or sensitive 
> security material only if the communication is cryptographically 
> protected as defined by the Thread Specification.
> 
> Interoperability:
> 
> There are no known interoperability issues at this time. Thread Group's 
> internal registration procedure aims to cross-check for interoperability 
> issues at the time of registration for each new addition to the internal 
> registry.
> 
> Resolution:
> 
> It is not foreseen that URNs within this namespace will undergo 
> resolution. Thread Group does not plan to operate any resolution 
> services for "thread" URNs. Usage of information encoded within these 
> URNs is as defined by the Thread Specification.
> 
> Documentation:
> 
> Thread Specification (most recent version higher than v1.3) as published 
> by Thread Group. Available at: https://www.threadgroup.org/ThreadSpec 
> <https://www.threadgroup.org/ThreadSpec>
> 
> Note: some versions of the Thread Specification are only available to 
> members of the Thread Group, or its affiliates. Future versions of the 
> Thread Specification are expected to contain URN definitions and the 
> contents of the internal registry as described in this registration request.
> 
> Additional Information:        None.
> 
> Revision Information:          Not applicable (this is version 1).
> 
> 
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn