Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updated by:

RFC 7959,RFC 8613,RFC 8974,RFC 9175,RFC 9876

Authors:

Z. Shelby
K. Hartke
C. Bormann

Stream:

IETF

Source:

core (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC7252

Discuss this RFC: Send questions or comments to the mailing listcore@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 7252

Abstract

The Constrained Application Protocol (CoAP) is a specialized webtransfer protocol for use with constrained nodes and constrained(e.g., low-power, lossy) networks. The nodes often have 8-bitmicrocontrollers with small amounts of ROM and RAM, while constrainednetworks such as IPv6 over Low-Power Wireless Personal Area Networks(6LoWPANs) often have high packet error rates and a typicalthroughput of 10s of kbit/s. The protocol is designed for machine-to-machine (M2M) applications such as smart energy and buildingautomation.

CoAP provides a request/response interaction model betweenapplication endpoints, supports built-in discovery of services andresources, and includes key concepts of the Web such as URIs andInternet media types. CoAP is designed to easily interface with HTTPfor integration with the Web while meeting specialized requirementssuch as multicast support, very low overhead, and simplicity forconstrained environments.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.