Also, the RFC is quite a nice read: https://tools.ietf.org/html/rfc7252 https://tools.ietf.org/html/rfc7252 I particularly like the introduction, which succinc

Also, the RFC is quite a nice read: https://tools.ietf.org/html/rfc7252 https://tools.ietf.org/html/rfc7252 I particularly like the introduction, which succinctly explains the value in realizing a subset of REST common with HTTP, while not just blindly trying to make a compressed version of HTTP. The end result is a protocol which is quite easy to map to each other, not just in terms of implementation but also in terms of mindset. Being familiar with HTTP means you won't feel completely lost in trying to learn CoAP, which is pretty cool.