Difference between revisions of "Constrained Application Protocol"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
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 '''Constrained Application Protocol''' ('''CoAP''') is a specialized web transfer protocol, as defined in RFC 7252, 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. | The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation. | ||
== Features == | |||
The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM. | |||
CoAP has the following main features: | |||
* Web protocol fulfilling M2M requirements in constrained environments | |||
* UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests | |||
* Asynchronous message exchanges | |||
* Low header overhead and parsing complexity | |||
* URI and Content-type support | |||
* Simple proxy and caching capabilities | |||
* Stateless HTTP mapping | |||
* Security binding to Datagram Transport Layer Security (DTLS) | |||
== Message Formats == | |||
Revision as of 13:00, 11 March 2019
The Constrained Application Protocol (CoAP) is a specialized web transfer protocol, as defined in RFC 7252, 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.
Features
The work on Constrained Environments aims at realizing the REST architecture in a suitable form for the most constrained nodes and networks. The nodes usually consist of 8-bit microcontrollers with limited amounts of RAM and ROM.
CoAP has the following main features:
- Web protocol fulfilling M2M requirements in constrained environments
- UDP [RFC0768] binding with optional reliability supporting unicast and multicast requests
- Asynchronous message exchanges
- Low header overhead and parsing complexity
- URI and Content-type support
- Simple proxy and caching capabilities
- Stateless HTTP mapping
- Security binding to Datagram Transport Layer Security (DTLS)
Message Formats
Courses
References
- RFC 7252: https://tools.ietf.org/html/rfc7252
- CoAP: RFC 7252 Constrained Application Protocol https://coap.technology/
- Learning Internet of Things: https://www.oreilly.com/library/view/learning-internet-of/9781783553532/