From nobody Fri Dec 16 04:23:29 2022
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 6CD18C1526FC
 for <core@ietfa.amsl.com>; Fri, 16 Dec 2022 04:23:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5,
 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 RfwZcstTmDtk for <core@ietfa.amsl.com>;
 Fri, 16 Dec 2022 04:23:24 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.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 EF16DC152593
 for <core@ietf.org>; Fri, 16 Dec 2022 04:23:22 -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 4NYStZ46vMzDCfg;
 Fri, 16 Dec 2022 13:23:18 +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: <DU0P190MB197805BF4E0CBE19A3CA9C78FDE69@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
Date: Fri, 16 Dec 2022 13:23:18 +0100
Cc: Michael Richardson <mcr@sandelman.ca>,
 Jon Shallow <supjps-ietf@jpshallow.com>,
 "core@ietf.org WG (core@ietf.org)" <core@ietf.org>
X-Mao-Original-Outgoing-Id: 692886198.099798-67282774c3c2e5339024c2da4cd25292
Content-Transfer-Encoding: quoted-printable
Message-Id: <CB5A024D-6009-4EA4-8F89-A308641DA696@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>
 <D1FE0244-A7A0-4B41-BA65-A5D1C3A32523@tzi.org> <20211.1671120313@localhost>
 <DU0P190MB197805BF4E0CBE19A3CA9C78FDE69@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
To: Esko Dijk <esko.dijk@iotconsultancy.nl>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/lV9OmD109WtGMz36HfFs1zNPj-o>
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: Fri, 16 Dec 2022 12:23:28 -0000

On 2022-12-16, at 13:00, Esko Dijk <esko.dijk@iotconsultancy.nl> wrote:
>=20
> coap+unix:///some/local/path/coap+tcp:///another/path
>=20
> So then only one new additional scheme would be required.

A problem with this is, when this is actually about using a proxy, the =
inner scheme (coap+tcp: here) does not predict the form of the =
communication over the unix domain socket (datagram vs. stream).  (Also, =
the proxy could translate from coap to coaps, so there is another =
dimension as well, requiring coap and coaps.)

Gr=C3=BC=C3=9Fe, Carsten