Constrained Application Protocol: Difference between revisions

Content deleted Content added
Added link to official specification; removed link to an unofficial website (not updated)
added a list of RFC that define important extensions to CoAP (like the Observe Option)
Line 6:
CoAP is a [[service layer]] protocol that is intended for use in resource-constrained internet devices, such as [[wireless sensor network]] nodes. CoAP is designed to easily translate to [[HTTP]] for simplified integration with the web, while also meeting specialized requirements such as [[multicast]] support, very low overhead, and simplicity.<ref>[https://tools.ietf.org/html/rfc7252 RFC 7252, Constrained Application Protocol (CoAP)]</ref><ref>"[http://hinrg.cs.jhu.edu/joomla/images/stories/IPSN_2011_koliti.pdf Integrating Wireless Sensor Networks with the Web]" , Walter, Colitti 2011</ref> Multicast, low overhead, and simplicity are extremely important for [[Internet of Things]] (IoT) and [[Machine-to-Machine]] (M2M) devices, which tend to be deeply [[Embedded system|embedded]] and have much less memory and power supply than traditional internet devices have. Therefore, efficiency is very important. CoAP can run on most devices that support [[User Datagram Protocol|UDP]] or a UDP analogue.
 
The Internet Engineering Task Force ([[IETF]]) Constrained [[RESTful]] Environments Working Group ([https://datatracker.ietf.org/doc/charter-ietf-core/ CoRE]) has done the major standardization work for this protocol. In order to make the protocol suitable to IoT and M2M applications, various new functions have been added. The core of the protocol is specified in RFC 7252; important extensions are in various stages of the standardization process.
 
== FeaturesSpecification ==
The core of the protocol is specified in RFC 7252. Various extensions have been proposed, particularly:
* [https://datatracker.ietf.org/doc/html/rfc7641 RFC 7641] (2015) Observing Resources in the Constrained Application Protocol
* [https://datatracker.ietf.org/doc/html/rfc7959 RFC 7959] (2016) Block-Wise Transfers in the Constrained Application Protocol (CoAP)
* [https://datatracker.ietf.org/doc/html/rfc8323 RFC 8323] (2018) CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets
* [https://datatracker.ietf.org/doc/html/rfc8974 RFC 8974] (2021) Extended Tokens and Stateless Clients in the Constrained Application Protocol (CoAP)
 
==Message formats==