The Constrained Application Protocol (CoAP)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 112
- Abstract
- 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.
- Publication Date
- 2014-06-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC7252- Link
- https://doi.org/10.17487/RFC7252
- Author(s)
- Zach ShelbyKlaus HartkeCarsten Bormann
Latest version of IETF RFC 7252
Document Versions — IETF RFC 7252
-
▶ IETF RFC 7252 (2014-06-01)THIS DOC [ACTIVE] [LATEST VERSION]
Amended by:
- IETF RFC 7959 [Active*]
- RFC8613 NOT IN REGISTRY
- RFC8974 NOT IN REGISTRY
- RFC9175 NOT IN REGISTRY
- RFC9876 NOT IN REGISTRY
Normative Reference(s)
- IETF RFC 768 [Active*]
- IETF RFC 2045 [Active*]
- IETF RFC 2046 [Active, Amended*]
- IETF RFC 2119 [Active*]
- IETF RFC 2616 [Superseded*]
- IETF RFC 3023 [Superseded*]
- IETF RFC 3629 [Active*]
- IETF RFC 3676 [Active*]
- IETF RFC 3986 [Active, Amended*]
- IETF RFC 4279 [Active*]
- IETF RFC 4395 [Superseded*]
- IETF RFC 5147 [Active*]
- IETF RFC 5198 [Active*]
- IETF RFC 5226 [Superseded*]
- IETF RFC 5234 [Active, Amended*]
- IETF RFC 5246 [Superseded*]
- IETF RFC 5280 [Active, Amended*]
- IETF RFC 5480 [Active*]
- IETF RFC 5785 [Superseded*]
- IETF RFC 5952 [Active*]
- IETF RFC 5988 [Superseded*]
- IETF RFC 6066 [Active*]
- IETF RFC 6347 [Superseded*]
- IETF RFC 6690 [Active*]
- IETF RFC 6920 [Active*]
- IETF RFC 7250 [Active*]
- IETF RFC 7251 [Active*]
Bibliographic Reference(s)
- IEEE.STD1003.1.2013 — TIME_T EXTERNAL
- ISBN.3320258648 — HHGTTG EXTERNAL
- Allman, M., "Retransmission Timeout Considerations" , Work in Progress, May 2012. EXTERNAL
- Fielding, R., "Architectural Styles and the Design of Network-based Software Architectures", Ph.D. Dissertation, University of California, Irvine, 2000, < http://www.ics.uci.edu/~fielding/pubs/dissertation/ fielding_dissertation.pdf >. EXTERNAL
- Rahman, A. and E. Dijk, "Group Communication for CoAP" , Work in Progress, December 2013. EXTERNAL
- Bormann, C. and K. Hartke, "Miscellaneous additions to CoAP", Work in Progress, December 2013. EXTERNAL
- Castellani, A., Loreto, S., Rahman, A., Fossati, T., and E. Dijk, "Guidelines for HTTP-CoAP Mapping Implementations", Work in Progress, February 2014. EXTERNAL
- Bormann, C. and Z. Shelby, "Blockwise transfers in CoAP" , Work in Progress, October 2013. EXTERNAL
- Hartke, K., "Observing Resources in CoAP" , Work in Progress, April 2014. EXTERNAL
- IEEE Standards Association, "Guidelines for 64-bit Global Identifier (EUI-64 (TM))", Registration Authority Tutorials, April 2010, < http://standards.ieee.org/regauth/ oui/tutorials/EUI64.html >. EXTERNAL
- Bormann, C., "Using CoAP with IPsec" , Work in Progress, December 2012. EXTERNAL
- Wenning, R., "Report of the XML Security PAG", W3C XML Security PAG, October 2012, < http://www.w3.org/2011/xmlsec-pag/pagreport.html >. EXTERNAL
- IETF RFC 20 [Active*]
- IETF RFC 791 [Active*]
- IETF RFC 792 [Active*]
- IETF RFC 793 [Superseded*]
- IETF RFC 1035 [Active, Amended*]
- IETF RFC 3264 [Active*]
- IETF RFC 3280 [Superseded*]
- IETF RFC 3542 [Active*]
- IETF RFC 3828 [Active*]
- IETF RFC 4086 [Active*]
- IETF RFC 4443 [Active*]
- IETF RFC 4492 [Superseded*]
- IETF RFC 4821 [Active*]
- IETF RFC 4944 [Active*]
- IETF RFC 5405 [Superseded*]
- IETF RFC 5489 [Active*]
- IETF RFC 6090 [Active*]
- IETF RFC 6120 [Active*]
- IETF RFC 6282 [Active*]
- IETF RFC 6335 [Active*]
- IETF RFC 6655 [Active*]
- IETF RFC 6936 [Active*]
- IETF RFC 6960 [Active*]
- IETF RFC 6961 [Superseded*]
- IETF RFC 7159 [Superseded*]
- IETF RFC 7228 [Active*]
- W3C.exi.20140211 — REC-exi-20140211 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7252.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7252, The Constrained Application Protocol (CoAP). Available at https://doi.org/10.17487/RFC7252
Snippet:
IETF RFC 7252, The Constrained Application Protocol (CoAP). Available at https://doi.org/10.17487/RFC7252
HTML (ISO 690 compliant)
Preview:
IETF RFC 7252, The Constrained Application Protocol (CoAP). Available at https://doi.org/10.17487/RFC7252
Snippet:
<span class="citation"><cite>IETF RFC 7252</cite>, The Constrained Application Protocol (CoAP). Available at <a href="https://doi.org/10.17487/RFC7252" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7252</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7252, The Constrained Application Protocol (CoAP)
doi: 10.17487/RFC7252
url: https://doi.org/10.17487/RFC7252
doi: 10.17487/RFC7252
url: https://doi.org/10.17487/RFC7252
Snippet:
<li> <cite id="bib-rfc7252">IETF RFC 7252</cite>, The Constrained Application Protocol (CoAP) <span class="doi">10.17487/RFC7252</span> </li>
Referenced By
- IETF draft-ietf-core-cocoa-02 [Active*]
- IETF draft-ietf-core-object-security-08 [Active*]
- IETF draft-silverajan-core-coap-alternative-transports-10 [Active*]
- IETF RFC 7250 [Active*]
- IETF RFC 7390 [Active*]
- IETF RFC 7452 [Active*]
- IETF RFC 7641 [Active*]
- IETF RFC 7925 [Active*]
- IETF RFC 7959 [Active*]
- IETF RFC 7967 [Active*]
- IETF RFC 8075 [Active*]
- IETF RFC 8132 [Active*]
- IETF RFC 8152 [Superseded*]
- IETF RFC 8307 [Active*]
- IETF RFC 8323 [Active*]
- IETF RFC 8615 [Active*]