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

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 15 December 2022 01:19 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 52639C14CE25 for <core@ietfa.amsl.com>; Wed, 14 Dec 2022 17:19:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=sandelman.ca
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 cMUIVe9TLVhB for <core@ietfa.amsl.com>; Wed, 14 Dec 2022 17:19:43 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (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 EE973C14CF12 for <core@ietf.org>; Wed, 14 Dec 2022 17:19:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 9A76E38997; Wed, 14 Dec 2022 20:46:41 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 4SFB36x71Ld8; Wed, 14 Dec 2022 20:46:41 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id D3DE938994; Wed, 14 Dec 2022 20:46:40 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1671068800; bh=D/NviiQHL+sq9GkkuZTEWhAH3Wf6idAzZ0yYfB4mzXU=; h=From:To:Subject:In-Reply-To:References:Date:From; b=ttJkcYohnOjQovDDx7H0hkFVtycYS5PjGoMmpgE8H9ku6IzmwS91jEIYi9ckayUw9 OtJ6xIoXRbFz/wZFKQE9+B8ZDPjdx7mbkOFuWqAmrx3fTS2LxhEO0dYKX3JCBqEP4g HaOmI9f/DJMgqSva4bUC65uWQztzjt58atnDXkjGsD7H3taIBnGDaT1NK8Zpvplrzg wPFrc9HKbxw++4EVR+DV4pElb6S/4y5Ods+3uyhwhv1gOO7KV/3kVQSDhvKIgOa6Zc PqFdhlp33QL3EFS4plxLjPwX3sLlUYcEuNLr5DOXo/9v/kTvT1CDEpZG0u7oLjANDy 74/S//tPTxrIQ==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id CC6472E5; Wed, 14 Dec 2022 20:19:40 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: supjps-ietf@jpshallow.com, 'Carsten Bormann' <cabo@tzi.org>, core@ietf.org
In-Reply-To: <016701d90fe0$c49d3bb0$4dd7b310$@jpshallow.com>
References: <004601d90ee3$dd59df80$980d9e80$@jpshallow.com> <E270AC49-755E-4275-9F69-2D08B542E537@tzi.org> <014a01d90fce$043349d0$0c99dd70$@jpshallow.com> <016701d90fe0$c49d3bb0$4dd7b310$@jpshallow.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 14 Dec 2022 20:19:40 -0500
Message-ID: <15065.1671067180@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/5gH78ruYF3uX6y5z363z5_339Yc>
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 01:19:47 -0000

<supjps-ietf@jpshallow.com> wrote:
    > If the Unix Domain URI is encoded as
    > coap+unix://some.local.path/another/path, the host reg-name would be
    > "some.local.path" which when passed to the CoAP logic as the "host"

That seems wrong.
I think it should be:

coap+unix:///some/local/path/another/path

Just lile file:/// is.

BTW: Linux has a non-portable extension where you can start the path with \0
and then you wind up in some abstract non-file system name space.  If one
wanted to support that, then a different thing after the // might make sense.
    https://www.systutorials.com/docs/linux/man/7-unix/ See "Abstract"


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide