Re: [m2m-iwg] COAP

[Rick Bullotta <rick.bullotta@xxxxxxxxxxxxx>]

We’re a bit familiar with COAP.  Think of it like “HTTP lite”.  Might be OK for tunneling REST-ful stuff over MQTT, but unfortunately, it doesn’t bring a lot of additional capability in the core problems of providing a semantically meaningful model for those APIs, for representing entities and data, and so on.  That’s where the work needs to happen soon on MQTT.  Short explanation of COAP = all wrapper, no filler.  Useful for bridging bandwidth constrained devices with HTTP and the rest of the world, but falls far short of solving any actual applications.

 

From: m2m-iwg-bounces@xxxxxxxxxxx [mailto:m2m-iwg-bounces@xxxxxxxxxxx] On Behalf Of Ian Skerrett
Sent: Friday, April 12, 2013 11:22 AM
To: m2m Industry Working Group
Subject: [m2m-iwg] COAP

 

Does anyone have experience with Constrained Application Protocol (CoAP).  It certainly looks applicable in our space.

 

http://datatracker.ietf.org/doc/draft-ietf-core-coap/