[core] fyi: Non-traditional responses deployed in shelly.cloud
Christian Amsüss <christian@amsuess.com> Tue, 20 August 2019 08:48 UTC
Return-Path: <christian@amsuess.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 878B912091F for <core@ietfa.amsl.com>; Tue, 20 Aug 2019 01:48:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nZ6qbGGdQpju for <core@ietfa.amsl.com>; Tue, 20 Aug 2019 01:48:39 -0700 (PDT)
Received: from prometheus.amsuess.com (prometheus.amsuess.com [5.9.147.112]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E72C0120024 for <core@ietf.org>; Tue, 20 Aug 2019 01:48:38 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by prometheus.amsuess.com (Postfix) with ESMTPS id 06B6D40247 for <core@ietf.org>; Tue, 20 Aug 2019 10:48:35 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bf]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 741D926 for <core@ietf.org>; Tue, 20 Aug 2019 10:48:34 +0200 (CEST)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:b533:775a:25ba:8cbd]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 338017A for <core@ietf.org>; Tue, 20 Aug 2019 10:48:34 +0200 (CEST)
Received: (nullmailer pid 29066 invoked by uid 1000); Tue, 20 Aug 2019 08:47:55 -0000
Date: Tue, 20 Aug 2019 10:47:55 +0200
From: Christian Amsüss <christian@amsuess.com>
To: Core WG mailing list <core@ietf.org>
Message-ID: <20190820084750.GA25071@hephaistos.amsuess.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy"
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/V3kh_eAMaV2nea9qI00reSbNsBQ>
Subject: [core] fyi: Non-traditional responses deployed in shelly.cloud
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 20 Aug 2019 08:48:42 -0000
Hi CoRE, via a StackOverflow question[1] I found that there are home automation deployments that use something very similar to non-traditional responses: They send unsolicited representations with NON and 0.30 codes and Uri-Path options[2]. While the precise method they picked may be questionable (I really wouldn't want a dedicated code for that), this could be valuable input and implementation experience on the whole topic of nontraditional responses. Best regards Christian [1]: https://stackoverflow.com/questions/57558648/how-to-handle-custom-coap-options-non-standard [2]: https://shelly-api-docs.shelly.cloud/images/CoIoT%20for%20Shelly%20devices%20(rev%201.0)%20.pdf -- The detailed semantics of CoAP methods are "almost, but not entirely unlike" [HHGTTG] those of HTTP methods. [HHGTTG]: Adams, D., "The Hitchhiker's Guide to the Galaxy", October 1979. -- Shelby, et al., Internet-Draft Constrained Application Protocol (CoAP)
- [core] fyi: Non-traditional responses deployed in… Christian Amsüss