Re: [urn] Registration request for urn:thread:
worley@ariadne.com Mon, 29 January 2024 20:09 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 B4816C14CF01 for <urn@ietfa.amsl.com>; Mon, 29 Jan 2024 12:09:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.992
X-Spam-Level:
X-Spam-Status: No, score=-0.992 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 Ev2htxKL16Ok for <urn@ietfa.amsl.com>; Mon, 29 Jan 2024 12:09:17 -0800 (PST)
Received: from resqmta-h1p-028596.sys.comcast.net (resqmta-h1p-028596.sys.comcast.net [96.102.200.4]) (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 87763C15107C for <urn@ietf.org>; Mon, 29 Jan 2024 12:09:17 -0800 (PST)
Received: from resomta-h1p-027909.sys.comcast.net ([96.102.179.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resqmta-h1p-028596.sys.comcast.net with ESMTP id UT0brCoSVESWJUXuVravu3; Mon, 29 Jan 2024 20:07:15 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1706558835; bh=Te+jljne0lfjKX3/nuuAgHIp9w/U7eNYozmSAYr/haU=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:Xfinity-Spam-Result; b=SMFIYhyS4Fg1nK4aZQ0MvscPg4CvsBzC422ceNgqOlH2UVY5T328YIt0UOVtWFImT GwOdjujjQcegZdwyi+R4pMeFznW1IyCnT1fjmEMfQFaVSOJTOgEH52SyZh4lY+AG9W /p6qinyuF1i99nAKYhCBVw0PNHyvohczR7jNzJ/a2n7Fpa7FrJ/uNBhgPDUxSM+TG5 p2+ho6H5OjYnUuBHk67tUwbIqt+2eH4d8NjLzZJTweKiX7PrJGDoQyLUvpEYnSO5kt MARZmCpWb4TEBCkDRsOMobBtnIFpoWOXGP0nO9EjIwBj2a79aYv+HsoCzOgHClqeF/ GOQ1uYAEVJ1rQ==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430::dd00]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resomta-h1p-027909.sys.comcast.net with ESMTPA id UXu6r5YnRFqJxUXu7rUUIs; Mon, 29 Jan 2024 20:06:53 +0000
Received: from hobgoblin.ariadne.com (localhost [127.0.0.1]) by hobgoblin.ariadne.com (8.16.1/8.16.1) with ESMTPS id 40TK6nwN1853938 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Mon, 29 Jan 2024 15:06:49 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 40TK6nwr1853935; Mon, 29 Jan 2024 15:06:49 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Esko Dijk <esko.dijk@iotconsultancy.nl>
Cc: urn@ietf.org
In-Reply-To: <DU0P190MB1978D9E87EAFED79FB331BE7FD7E2@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> (esko.dijk@iotconsultancy.nl)
Sender: worley@ariadne.com
Date: Mon, 29 Jan 2024 15:06:49 -0500
Message-ID: <87zfwn7vl2.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4xfJ/aPqdcVyqof3aQtpVK+RaK07TvpCa2lO50xnqwl+UnPRSqL+m0XDXl3lrvqWUYJyQAlNjZA72ikZeEaOVvphpeJBkUTJNoPGH2vkxKXwYNXBO/2JYI +N171porh6eco300rAgi5da6MDX3nT2LfaK36w6rwPtjJ5SAi9E/krEJCHBhZ8ee6hXkigYvOFVjn/BxDIcY8W1CacfumBeg61c+76LdEV0TcbtOapJP3BnA 6dZ0zyPVEoewMuUdmrlE6g==
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/7W51tveFjXpccDZBB_aCe9poR-8>
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, 29 Jan 2024 20:09:21 -0000
Esko Dijk <esko.dijk@iotconsultancy.nl> writes: >> Section 5.1 of RFC 8141 states: >> >> 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. >> >> In this case, I would say that the letter of RFC 8141 overrides the >> spirit of the IETF. > > Indeed this section was the basis for including a privately managed > (members-only) and non-public registry in the request. (Non-public, > because viewing it requires accepting the EULA.) > > There is a suggestion there to have at least the names - that are in > the registry - published. That is something we could add as a > requirement for any entries in the internal registry, if that helps? > > The public version of the registry would be in a separate document > that can be downloaded from www.threadgroup.org without providing a > name or accepting a EULA. And each registered URN would provide the > name and a short description also. Something like the table provided > by 3GPP > (https://www.3gpp.org/3gpp-groups/core-network-terminals-ct/ct-wg1/uniform-resource-identifier-uri-list) > for example. It would then provide a link / doc-reference pointing > into the non-public specification. Given what Peter and Lars have said (and what RFC 8141 says!), I agree that this is a reasonable solution to all of these concerns. Dale
- [urn] Registration request for urn:thread: Esko Dijk
- Re: [urn] Registration request for urn:thread: worley
- Re: [urn] Registration request for urn:thread: Peter Saint-Andre
- Re: [urn] Registration request for urn:thread: Esko Dijk
- Re: [urn] Registration request for urn:thread: Esko Dijk
- Re: [urn] Registration request for urn:thread: Peter Saint-Andre
- Re: [urn] Registration request for urn:thread: Peter Saint-Andre
- Re: [urn] Registration request for urn:thread: Peter Saint-Andre
- Re: [urn] Registration request for urn:thread: worley
- Re: [urn] Registration request for urn:thread: Esko Dijk
- Re: [urn] Registration request for urn:thread: worley
- Re: [urn] Registration request for urn:thread: Esko Dijk
- Re: [urn] Registration request for urn:thread: Lars G. Svensson
- Re: [urn] Registration request for urn:thread: worley
- Re: [urn] Registration request for urn:thread: Peter Saint-Andre
- Re: [urn] Registration request for urn:thread: Esko Dijk
- [urn] Re: Registration request for urn:thread: Esko Dijk
- [urn] Re: Registration request for urn:thread: worley
- [urn] Re: Registration request for urn:thread: Peter Saint-Andre
- [urn] Re: Registration request for urn:thread: Esko Dijk
- [urn] Re: Registration request for urn:thread: worley
- [urn] Re: Registration request for urn:thread: Esko Dijk
- [urn] Re: Registration request for urn:thread: Peter Saint-Andre
- [urn] Re: Registration request for urn:thread: Esko Dijk
- [urn] Re: Registration request for urn:thread: Esko Dijk
- [urn] Re: Registration request for urn:thread: Peter Saint-Andre
- [urn] Re: Registration request for urn:thread: worley