Re: [urn] Registration request for urn:thread:
worley@ariadne.com Thu, 25 January 2024 18:49 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 67B70C14F61B for <urn@ietfa.amsl.com>; Thu, 25 Jan 2024 10:49:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.993
X-Spam-Level:
X-Spam-Status: No, score=-0.993 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_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 HZWzFJpuQ3sQ for <urn@ietfa.amsl.com>; Thu, 25 Jan 2024 10:49:12 -0800 (PST)
Received: from resqmta-c1p-023832.sys.comcast.net (resqmta-c1p-023832.sys.comcast.net [96.102.19.41]) (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 0AB21C14F682 for <urn@ietf.org>; Thu, 25 Jan 2024 10:43:31 -0800 (PST)
Received: from resomta-c1p-023411.sys.comcast.net ([96.102.18.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resqmta-c1p-023832.sys.comcast.net with ESMTP id T1nOrqVdjUSfCT4fKrr5OI; Thu, 25 Jan 2024 18:41:30 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1706208090; bh=kXxt3iJxkwfq3n2qsulR1ZQoC6Tnr/itbEudjaB1YZA=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:Xfinity-Spam-Result; b=eYoI6ylkxHElyT25x+L8pUFMKeGNAKPsI0/6nUiD0w9tZWyZ7fC46Fyzo44JX9s3O Lh4eTQneHeMG5FGajDO4AT8U1wnOQuJPqW8oB0XkhcztFYyvrTSDyvU7/hVuocoOGS h/1F/BDvQTktw8yLPQcy6xaAi7FIkvQgPV4oSrkMpSVN8g/RAOs/goV/wt1ilggXlZ O4VOz/nCRByMAtR6E2HXcXHqsptm4oeHzsESotnr+fxvMGVoPS1z4KZhERp6S493uH V3kUhzgZ2nRRylEn+DvCCCe4YJI1qt3JIIG5P43ErKanbiVwlZ6ELR5xAxpOStzkxN rmIhbNXa6EuIw==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430::c362]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resomta-c1p-023411.sys.comcast.net with ESMTPA id T4ekrWKMUyswkT4elrOU7r; Thu, 25 Jan 2024 18:41:07 +0000
Received: from hobgoblin.ariadne.com (localhost [127.0.0.1]) by hobgoblin.ariadne.com (8.16.1/8.16.1) with ESMTPS id 40PIes021284309 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Thu, 25 Jan 2024 13:40:54 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 40PIersW1284306; Thu, 25 Jan 2024 13:40:53 -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: worley@ariadne.com, urn@ietf.org
In-Reply-To: <DU0P190MB1978A4A40D7E779D25AD7B4DFD7A2@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> (esko.dijk@iotconsultancy.nl)
Sender: worley@ariadne.com
Date: Thu, 25 Jan 2024 13:40:53 -0500
Message-ID: <877cjxjlxm.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4xfFjqnI18gTwXPv1UDqPFHBX+kSb3x9PBmqIp/Xue8c36CbOpp/vyOt4IHc7kI/dJzRXvcnASd1U6KTbV+VDZuOoDgaxAQSaZdNil4gk4yMrLWNNLTeOM cHx+rOBCu18ffI1NVZ06+OKm+MRFEc3xbQUIoZUYE/BpQEee2IOAjCMFFAOdbIOsGJUyDe7VgWtAzwdvkSDIP4avfOVSFqaKFR9E5wu+NmzsmEpy+6dWpgCP 8O/bBhY2PiB6X2lYjX2zA+E96c1CWMxjkpEzlVmi52Ar6SsBAc2gJtwtWDcvfMGF
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/DPspbZNGbFJSeHokvACPZ5Lq924>
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: Thu, 25 Jan 2024 18:49:16 -0000
Esko Dijk <esko.dijk@iotconsultancy.nl> writes: >> This text says "published" but the page at the URL only allows access >> under NDA. > > Right, the "internal use only" in the EULA seems to prohibit public > discussion on content or quoting. Could we say "made available by > Thread Group to members and non-member licensees"? My opinion is "No", unless it's agreed that *all* non-members are licensed to see, copy, and discuss it in any forum. See, e.g., https://www.ietf.org/about/introduction/ Introduction to the IETF Mission The IETF wants the Internet to be useful for communities that share our commitment to openness and fairness. https://www.ietf.org/about/open-records/ Open records The IETF operates in an open and transparent fashion and we publish open records of most of the contributions, submissions, statements, and communications that we receive. https://www.ietf.org/privacy-statement/ IETF/IRTF/IAB Privacy Statement Our Commitment to Transparency The IETF/IRTF/IAB operates in an open and transparent fashion. As a part of this transparency, any contributions, submissions, statements or communications that you make to any Party including any Personal Data, other than as expressly excepted in this statement, will be made public through electronic and other means. Having a URN namespace whose fundamental rules and structure is trade secret is contrary to the spirit of the IETF. > For the sub-namespaces we can define the syntax & semantics already > now in the request doc; so that part at least is public. > > For the email addresses: if personal addresses are not preferred, we > could also list a single role address help&threadgroup.org which can > forward technical questions to the right people. Is this preferrable? It's definitely an improvement, as "help@..." is likely to remain valid for longer than personal addresses. OTOH, you may want to define a separate "technical role" address "technical@..." and for the time being, just forward it to "help@...", or even the two individuals you've listed. 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