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

Michael Richardson <mcr@sandelman.ca> Thu, 15 December 2022 16:05 UTC

Return-Path: <mcr@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 F2B1DC151709 for <core@ietfa.amsl.com>; Thu, 15 Dec 2022 08:05:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 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_HI=-5, 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 6Ddgyndqz_e7 for <core@ietfa.amsl.com>; Thu, 15 Dec 2022 08:05:16 -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 C8DF0C1524A2 for <core@ietf.org>; Thu, 15 Dec 2022 08:05:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 11E733898E; Thu, 15 Dec 2022 11:32:17 -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 tI50O-rASUvW; Thu, 15 Dec 2022 11:32:16 -0500 (EST)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 281603898C; Thu, 15 Dec 2022 11:32:16 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1671121936; bh=ocg0R1FAgIc6auuAXs/pJUCXktej8lCuG9rPTYTLlJg=; h=From:To:Subject:In-Reply-To:References:Date:From; b=w7hegmKcgkFqTF+ZlF+zoqj40nePKkBHvpesywnRPtu7ezVJ6tBknbj5rslQYUn21 ja8d99wV5PW3zHqAPXYdk1oahAgXhkm1tmblymXqT2L3A7ztLItpjDbghSeIwi2+8p RGexG4r8mFwgnYqF1iNOpGdYrRL9g/VZBjlaCvRz9pEkDp4wCczatLR/0gzWeKQPL4 P0xkniVCPwl8529sSzS0HVnh4z7N7Ot1Gux8VQ06tMUouxhVOItPCTU56c4o+kFpWr eE60tjl9fWk5hE2X8xSjfYKqIajYOIoSOu2q0obTOM9D9hWMQ9x8hF1DHaiQu/JTtT 9a0Slvmxz1lPQ==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id CD2853C; Thu, 15 Dec 2022 11:05:13 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>, Jon Shallow <supjps-ietf@jpshallow.com>, "core@ietf.org WG (core@ietf.org)" <core@ietf.org>
In-Reply-To: <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> <D1FE0244-A7A0-4B41-BA65-A5D1C3A32523@tzi.org>
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: text/plain; charset="us-ascii"
Content-ID: <20210.1671120313.1@localhost>
Date: Thu, 15 Dec 2022 11:05:13 -0500
Message-ID: <20211.1671120313@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/MdqCQKt6wxxlaJTcZDLy3XHCETc>
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 16:05:21 -0000

Carsten Bormann <cabo@tzi.org> wrote:
    >> coap+unix:///some/local/path/another/path

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

Oh. Yes.  I wasn't thinking that there would ever be a URI path, because in
Jon's use case, he is always just proxying to some servers.
But, of course there are other use cases.