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

Carsten Bormann <cabo@tzi.org> Wed, 14 December 2022 17:49 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 A3B33C15171C for <core@ietfa.amsl.com>; Wed, 14 Dec 2022 09:49:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.19
X-Spam-Level:
X-Spam-Status: No, score=-4.19 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01] 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 nVaZWuTI3yF9 for <core@ietfa.amsl.com>; Wed, 14 Dec 2022 09:49:07 -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 3EE66C14CE47 for <core@ietf.org>; Wed, 14 Dec 2022 09:49:05 -0800 (PST)
Received: from [192.168.217.124] (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 4NXNCK2XHZzDCbG; Wed, 14 Dec 2022 18:49:01 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <016701d90fe0$c49d3bb0$4dd7b310$@jpshallow.com>
Date: Wed, 14 Dec 2022 18:49:00 +0100
Cc: core@ietf.org
X-Mao-Original-Outgoing-Id: 692732940.9009579-e596fdd2626f81af8882b646a1749f6c
Content-Transfer-Encoding: quoted-printable
Message-Id: <B2096FE2-5FDB-4533-B0BC-F5308F6D820B@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>
To: supjps-ietf@jpshallow.com
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/mVgWY4qlm__Xckh-HGXDq594oqw>
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: Wed, 14 Dec 2022 17:49:13 -0000

On 2022-12-14, at 18:23, supjps-ietf@jpshallow.com wrote:
> 
> "some.local.path" which when passed to the CoAP logic as the "host" would then get translated to "/some/local/path”

What if I want to have dots in my socket path?

Grüße, Carsten