Re: [urn] corporate URN namespaces
worley@ariadne.com Mon, 29 January 2024 20:16 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 35081C151553 for <urn@ietfa.amsl.com>; Mon, 29 Jan 2024 12:16:35 -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 TNeuLnWWh0tV for <urn@ietfa.amsl.com>; Mon, 29 Jan 2024 12:16:31 -0800 (PST)
Received: from resqmta-c1p-023462.sys.comcast.net (resqmta-c1p-023462.sys.comcast.net [96.102.19.34]) (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 5491FC15154A for <urn@ietf.org>; Mon, 29 Jan 2024 12:16:30 -0800 (PST)
Received: from resomta-c1p-023413.sys.comcast.net ([96.102.18.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resqmta-c1p-023462.sys.comcast.net with ESMTP id UQpkrXc9zSlFzUY1VrOlUH; Mon, 29 Jan 2024 20:14:29 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1706559269; bh=baOA6i8RtB66mqIr6yV0VL1Mg8kPCqd/VEAFleOJUkM=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:Xfinity-Spam-Result; b=ufafdSRo0jMq9saVdA5TOWT7/JzODZFKPI3TcsDIWNdT35zvx2lZ3GSlD/dH/WDuH fviM5yeANEf+Rh4fJcVNPM14W21D7YvlGVuncO2dFAraWoJNNIngwWtU5jH1yl9v+I sCTktT8qOKQq5S3mfPG+qfx6241KdA/wkplaRiMCalQar6fAq4A7OwbGLr5135w7qA rsZxqHXXIwtbncm6cCsdtiJErQF1KnrC3iwjILUMFidNs4aC3LLDJywAcTlpsfdwI4 nU5NF5VLOqcy/xU+fuy7b8RT9knzuSDKuw+CM0C3Ub18qEEeDl7sLFhGvqoeOHWejK vkPGfLWHeR2/A==
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-c1p-023413.sys.comcast.net with ESMTPA id UY1JrjTiPS6dCUY1UrIuhN; Mon, 29 Jan 2024 20:14:29 +0000
Received: from hobgoblin.ariadne.com (localhost [127.0.0.1]) by hobgoblin.ariadne.com (8.16.1/8.16.1) with ESMTPS id 40TKEG551854779 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for <urn@ietf.org>; Mon, 29 Jan 2024 15:14:16 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 40TKEG4g1854776; Mon, 29 Jan 2024 15:14:16 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: urn@ietf.org
In-Reply-To: <6c0de4ca-dbc0-401d-b1df-34147ec9829b@stpeter.im>
Sender: worley@ariadne.com
Date: Mon, 29 Jan 2024 15:14:16 -0500
Message-ID: <87wmrr7v8n.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4xfGvrixe6nNUdO8Rml/TiZVKaXSwLVZFq60GpcMENkCxbcpePET6x0B1FRlEuiuFmmEHtyx8PS17/k1pjh/odMOdnP88PhwWcFPGK4Kx9+IWIu8d1ZKDo OQ1sXsELQNFVB8jQZsRHmJ6XXC6E5tm+DKVG2vfMU5Ah38QQZzrs9FDfkFbuKHVPzX7bWS6niNI6R0pJv26XjL7ki55msJ5J9jo=
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/B00jD6vT8CQeUIGkaz_jMVFca_E>
Subject: Re: [urn] corporate URN namespaces
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:16:35 -0000
Peter Saint-Andre <stpeter@stpeter.im> writes: > I'm curious how community participants and expert review team members > see the matter. Hmmmm... I'm not so concerned by circumscribed organizations creating their own pseudo-URNs for their internal usage. I am concerned, though, about a namespace that's meant to be used to interoperate between systems operated by many organizations, but the details of the namespace are not made public. This happens particularly when a trade group standardizes a bundle of technology but keeps the details secret. "*This* part of the Internet is private to members of the club!" Even in the situation of the Thread Group, where it seems anybody can obtain the details, but nobody is allowed to discuss them in public. But the distinction I am making may not be rational ... Dale
- [urn] corporate URN namespaces Peter Saint-Andre
- Re: [urn] corporate URN namespaces worley
- Re: [urn] corporate URN namespaces Lars G. Svensson
- Re: [urn] corporate URN namespaces Peter Saint-Andre
- Re: [urn] corporate URN namespaces Palek, Stephanie
- Re: [urn] corporate URN namespaces Peter Saint-Andre
- Re: [urn] corporate URN namespaces Peter Saint-Andre
- Re: [urn] corporate URN namespaces John C Klensin
- Re: [urn] corporate URN namespaces John C Klensin
- Re: [urn] corporate URN namespaces Peter Saint-Andre
- Re: [urn] corporate URN namespaces John C Klensin
- Re: [urn] corporate URN namespaces Peter Saint-Andre
- Re: [urn] corporate URN namespaces Peter Saint-Andre
- Re: [urn] corporate URN namespaces John C Klensin