CoAP support for IoT Hub
The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained networks in the Internet of Things. The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.
It would be helpful if you could support CoAP in IoT Hub. It provides a lightweight REST model messaging which can be used in constrained devices with ease.
COAP also provides stronger security at implementation level and will be a game changer for IoT Hub.
This is an important feature for products that for instance use (Open)Thread or related such as Project CHIP. Openthread is more and more used also for industrial applications. Therefor not being able to connect to IoT Hub through COAP is an issue for us.
Dulfer, Dirk commented
UDP reduces to overhead involved with transmitting the data to the (Edge) IoT endpoint that are currently TCP-based. For battery powered IoT devices, taking away this overhead translates into longer battery life and reduced maintenance requirements. Especially for sensors deployed in remote, hazardous or difficult to get to places low maintenance is a must have.
Remote battery powered IoT devices are oftenly connected via NB-IoT or LTE-M, which offer limited bandwidth.
Having support for CoAP (using UDP protocol) in IoT Hub (and Edge), would definitely make sense and would give Azure IoT a big advantage over other providers.
Support for DTLS (with symmetric key and certificate) and dtls connection id (https://datatracker.ietf.org/doc/draft-ietf-tls-dtls-connection-id/ - needed for most NB-IoT networks since they use carrier grade NAT) would be very useful. Without DTLS, CoAP would likely be unencrypted.
This is a make or break for Azure IOT relevance in the current marketplace
Richard Hubert commented
This is a must-do for the IoT-Hub and IoT-Edge. Announce it now, or lose serious ground. Sincerly.