Skip to main content

The Constrained Application Protocol (CoAP)
RFC 7252

Revision differences

Document history

Date By Action
2023-01-19
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes …
Received changes through RFC Editor sync (changed abstract to 'The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine- to-machine (M2M) applications such as smart energy and building automation.

CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead, and simplicity for constrained environments.')
2016-12-24
(System) Received changes through RFC Editor sync (added Errata tag)
2015-10-14
(System) Notify list changed from core-chairs@ietf.org, draft-ietf-core-coap@ietf.org to (None)
2014-06-27
(System) IANA registries were updated to include RFC7252
2014-06-26
(System) RFC published