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

Jon Shallow <supjps-ietf@jpshallow.com> Wed, 14 December 2022 19:05 UTC

Return-Path: <supjps-ietf@jpshallow.com>
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 62291C14F723 for <core@ietfa.amsl.com>; Wed, 14 Dec 2022 11:05: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 xhrTcoVAby09 for <core@ietfa.amsl.com>; Wed, 14 Dec 2022 11:05:17 -0800 (PST)
Received: from mail.jpshallow.com (mail.jpshallow.com [31.22.13.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5BF0C14E514 for <core@ietf.org>; Wed, 14 Dec 2022 11:05:16 -0800 (PST)
Received: from [192.168.0.78] (helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.92.3) (envelope-from <jon.shallow@jpshallow.com>) id 1p5X46-00055Q-O1; Wed, 14 Dec 2022 19:05:14 +0000
From: Jon Shallow <supjps-ietf@jpshallow.com>
To: 'Carsten Bormann' <cabo@tzi.org>
Cc: core@ietf.org
References: <004601d90ee3$dd59df80$980d9e80$@jpshallow.com> <E270AC49-755E-4275-9F69-2D08B542E537@tzi.org> <014a01d90fce$043349d0$0c99dd70$@jpshallow.com> <016701d90fe0$c49d3bb0$4dd7b310$@jpshallow.com> <B2096FE2-5FDB-4533-B0BC-F5308F6D820B@tzi.org>
In-Reply-To: <B2096FE2-5FDB-4533-B0BC-F5308F6D820B@tzi.org>
Date: Wed, 14 Dec 2022 19:04:53 -0000
Message-ID: <017801d90fee$f2d94a60$d88bdf20$@jpshallow.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI0eiyo13tkLZMJo+2rfTYfx7famQFWV2EZAjAko9ABWCLnOwJTlPfHrX1XcFA=
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/xRw9XBbDj33Z5UpDmqTUWysm6BU>
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 19:05:22 -0000

> > "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?
> 

Doh - scrap that idea then.

Regards

Jon