Re: [core] Interest in defining CoAP over Unix Domain sockets?

Carsten Bormann <cabo@tzi.org> Thu, 15 December 2022 03:42 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A7F9C14CF12 for <core@ietfa.amsl.com>; Wed, 14 Dec 2022 19:42:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 lRhn_bmsRIor for <core@ietfa.amsl.com>; Wed, 14 Dec 2022 19:42:17 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (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 0421FC185B86 for <core@ietf.org>; Wed, 14 Dec 2022 19:41:42 -0800 (PST)
Received: from smtpclient.apple (p5089abf5.dip0.t-ipconnect.de [80.137.171.245]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4NXdM633nxzDCdR; Thu, 15 Dec 2022 04:41:38 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <15065.1671067180@localhost>
Date: Thu, 15 Dec 2022 04:41:37 +0100
Cc: Jon Shallow <supjps-ietf@jpshallow.com>, "core@ietf.org WG (core@ietf.org)" <core@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D1FE0244-A7A0-4B41-BA65-A5D1C3A32523@tzi.org>
References: <004601d90ee3$dd59df80$980d9e80$@jpshallow.com> <E270AC49-755E-4275-9F69-2D08B542E537@tzi.org> <014a01d90fce$043349d0$0c99dd70$@jpshallow.com> <016701d90fe0$c49d3bb0$4dd7b310$@jpshallow.com> <15065.1671067180@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/yOpJT7uuly2QUGqV4p0dsY0Ul7g>
Subject: Re: [core] Interest in defining CoAP over Unix Domain sockets?
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Dec 2022 03:42:22 -0000

On 15. Dec 2022, at 02:19, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> coap+unix:///some/local/path/another/path

Which part is the socket path, and which part is the URI path?

coap+unix://%2Fsome%2Flocal%2Fpath/another/path
…makes this well-defined.

coap://%2Fsome%2Flocal%2Fpath/another/path
…would actually work, too, as a leading %2F is not allowed in a DNS name and this therefore disambiguates nicely.

Grüße, Carsten