Re: [urn] NEW NAMESPACE REGISTRATION: KNX

Peter Saint-Andre <stpeter@stpeter.im> Tue, 05 September 2023 15:52 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 8B17AC1516E3 for <urn@ietfa.amsl.com>; Tue, 5 Sep 2023 08:52:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level:
X-Spam-Status: No, score=-2.198 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, NICE_REPLY_A=-0.091, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=stpeter.im header.b="IOnVE6m/"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="kU6fG3U/"
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 N8_e8cCJLbX0 for <urn@ietfa.amsl.com>; Tue, 5 Sep 2023 08:52:15 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA146C14CE5D for <urn@ietf.org>; Tue, 5 Sep 2023 08:52:15 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 007185C00C1; Tue, 5 Sep 2023 11:52:15 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 05 Sep 2023 11:52:15 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h=cc :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:sender:subject:subject:to:to; s=fm2; t= 1693929134; x=1694015534; bh=ICF2Pw5xtjxoeypP9unTZ1B2Pg3YnUYSLoy VVug5aAQ=; b=IOnVE6m/WU2iAa+eNgF3WptJFC3UpXNzDez0ghwlfxY17svgz51 tovowO3lrhHyssOwC4YMZuaPQxoFCPO/i056Re783uJ1qQH8xi3A5I8cxXDSP/nk 9lPIizLerjiJtkABBBb0+MkrmBpGhQ00AW3/96zY2cDaxUkVOtN3EhFkPrTEUpI3 q2pYjP9szfriL5H8FZdDgRICldltYUvrly+mvPMA4Kz6phi+9x4GLd9thqcgjotP MRCcE0OaOCjrIFz2ZkiEXJZcHKC08kNlsO/NAivgmJSTJxbVCoynebm/VraU2SW+ NMYCIUpAaGDp4tb8HCgrSUa6T1Or+ni0Piw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1693929134; x=1694015534; bh=ICF2Pw5xtjxoeypP9unTZ1B2Pg3YnUYSLoy VVug5aAQ=; b=kU6fG3U/RoDJ33pPAdLkkf6BEoUJAT/gMBKlpyJ5MuqzNFNS4mb lJRnataBE1oILvnQ9OUhRLwKHbMmtLOTfZtK+u0V60xBLT7ZyTZC54r8lLALfe5L YF497MXE0Jv7eppIlnPSOKKjgbVD/zvv2/pY6ihpZYJHpXza+u8YqhfEZPpTQGws UpraaqYxmXHzqOLiCMKS7dw8sJsYK9HZSazZPj+K6ZNGiAbB62m81A6ASmmIVVts CWAyshJWkQXLj/21dDsWMQ5TaCkFdDxj5B0IhuPohOBrVBH7TpPvEZ8qJlD1T2w7 4LQNrjIi7Rn1W0GLR4ADqO10f5K3EjDxkvA==
X-ME-Sender: <xms:rk73ZFLSN0OJ0cV-p-SaO4KezY_rhigO444_e7JR5Y5Q5qqTWlgrpg> <xme:rk73ZBJVSA0YMI_v967RHhT54TSQZfGt_AGAKChxmeEhuzQ2xHpWBKpWj9AeUyB8q I_eq0hwafbyRCg6ig>
X-ME-Received: <xmr:rk73ZNu8MqRJVCDDw1VsX9GeQtSFoxYdu4SsP8Itq1OPUGPwzTK5fJwkc7Bahg4h>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudehuddgjeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfvfevfhfhufgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhesshhtphgvthgvrhdrihhmqe enucggtffrrghtthgvrhhnpedttdfgueeuiedtteeuieekhefhfeevleeihfevgfdtudef vdduveevieevgfetteenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehsthhpvghtvghrsehsthhpvghtvghrrdhimh
X-ME-Proxy: <xmx:rk73ZGaXDsjtFI0FJCYhYcNN5DOhXiaIIoAUMDJiVM9yLPs5qtO4SQ> <xmx:rk73ZMbeh4ziOzsyVYYOxakAkGZZeCMq1W9WIUDin9gUJK9JQl58iw> <xmx:rk73ZKBabnsfs8qkttQggOwO0-qz16Ssqps2-sVWcZwouzP4uRD94A> <xmx:rk73ZBNwZjl67SQanWTYFBuSRe8lyWWRUZaMaQU1B5bb3U729zPKNQ>
Feedback-ID: i24394279:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 5 Sep 2023 11:52:13 -0400 (EDT)
Message-ID: <6d751df7-5396-a874-3a98-c8c4e032a15d@stpeter.im>
Date: Tue, 05 Sep 2023 09:52:12 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.15.0
Content-Language: en-US
To: "Dale R. Worley" <worley@ariadne.com>, Michael Critchfield <michael.critchfield@knx.org>
Cc: urn@ietf.org, joost.demarest@knx.org, ahaenel@knx.org, steven.debruyne@knx.org, w.vanderbeek@cascoda.com
References: <87v8cp93bv.fsf@hobgoblin.ariadne.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <87v8cp93bv.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/nvbO5ozyzyd0RqLKyvJLPaCh0B4>
Subject: Re: [urn] NEW NAMESPACE REGISTRATION: KNX
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: Tue, 05 Sep 2023 15:52:20 -0000

On 9/4/23 12:54 PM, Dale R. Worley wrote:

> In regard to "relative URNs", comparing the KNX document line 272
> ("Relative URN without namespace identifier (with ":" at the
> beginning)") with RFC 8141 section 4.3 ("URNs and Relative References")
> and RFC 3986 (the syntax of "relative-ref"), I see that relative URNs
> (in the KNX sense) *must* start with ":", but relative URIs (in the IETF
> sense) *never* start with ":".  So though we might consider the KNX
> definition confusing, there is no contradiction, as syntax distinguishes
> whether a "relative URN" is to be interpreted per KNX or per RFC 3986.

I disagree. There *is* a contradiction, the KNX specification is using 
the term "relative URN" (which is undefined), and allowing this is not a 
responsible way to proceed.

Why do the authors of the KNX specification apparently feel the need to 
elide 'urn:knx' from the start of (some) URNs in the KNX namespace? Is 
this being done to save a few bytes over constrained links for IoT?

Peter