RFC 7252: The Constrained Application Protocol (CoAP)

The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy)…

Read RFC 7252 on the RFC Editor

Outgoing relationships (41 related RFCs)

Normative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Normative reference — RFC 5234: Augmented BNF for Syntax Specifications: ABNF
Normative reference — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Normative reference — RFC 3629: UTF-8, a transformation format of ISO 10646
Normative reference — RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
Normative reference — RFC 768: User Datagram Protocol
Normative reference — RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
Normative reference — RFC 6347: Datagram Transport Layer Security Version 1.2
Normative reference — RFC 6066: Transport Layer Security (TLS) Extensions: Extension Definitions
Normative reference — RFC 3023: XML Media Types
Normative reference — RFC 5952: A Recommendation for IPv6 Address Text Representation
Normative reference — RFC 4279: Pre-Shared Key Ciphersuites for Transport Layer Security (TLS)
Normative reference — RFC 5480: Elliptic Curve Cryptography Subject Public Key Information
Normative reference — RFC 5198: Unicode Format for Network Interchange
Normative reference — RFC 4395: Guidelines and Registration Procedures for New URI Schemes
Normative reference — RFC 5988: Web Linking
Normative reference — RFC 5785: Defining Well-Known Uniform Resource Identifiers (URIs)
Normative reference — RFC 6690: Constrained RESTful Environments (CoRE) Link Format
Normative reference — RFC 6920: Naming Things with Hashes
Normative reference — RFC 5147: URI Fragment Identifiers for the text/plain Media Type
Normative reference — RFC 3676: The Text/Plain Format and DelSp Parameters
Informative reference — RFC 793: Transmission Control Protocol
Informative reference — RFC 3264: An Offer/Answer Model with Session Description Protocol (SDP)
Informative reference — RFC 4086: Randomness Requirements for Security
Informative reference — RFC 792: Internet Control Message Protocol
Informative reference — RFC 4443: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification
Informative reference — RFC 20: ASCII format for network interchange
Informative reference — RFC 4821: Packetization Layer Path MTU Discovery
Informative reference — RFC 6120: Extensible Messaging and Presence Protocol (XMPP): Core
Informative reference — RFC 6335: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry
Informative reference — RFC 4944: Transmission of IPv6 Packets over IEEE 802.15.4 Networks
Informative reference — RFC 6090: Fundamental Elliptic Curve Cryptography Algorithms
Informative reference — RFC 6282: Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks
Informative reference — RFC 3828: The Lightweight User Datagram Protocol (UDP-Lite)
Informative reference — RFC 5405: Unicast UDP Usage Guidelines for Application Designers
Informative reference — RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums
Informative reference — RFC 4492: Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS)
Informative reference — RFC 3542: Advanced Sockets Application Program Interface (API) for IPv6
Informative reference — RFC 5489: ECDHE_PSK Cipher Suites for Transport Layer Security (TLS)
Informative reference — RFC 6655: AES-CCM Cipher Suites for Transport Layer Security (TLS)

Incoming relationships (51 related RFCs)

Showing 50 of 51 related RFCs.

Updated by — RFC 8613: Object Security for Constrained RESTful Environments (OSCORE)
Updated by — RFC 7959: Block-Wise Transfers in the Constrained Application Protocol (CoAP)
Updated by — RFC 9175: Constrained Application Protocol (CoAP): Echo, Request-Tag, and Token Processing
Updated by, Normatively referenced by — RFC 8974: Extended Tokens and Stateless Clients in the Constrained Application Protocol (CoAP)
Updated by, Normatively referenced by — RFC 9876: Updates to the IANA Registration Procedures for Constrained Application Protocol (CoAP) Content-Formats
Normatively referenced by — RFC 7641: Observing Resources in the Constrained Application Protocol (CoAP)
Normatively referenced by — RFC 9132: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
Normatively referenced by — RFC 9200: Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)
Normatively referenced by — RFC 9176: Constrained RESTful Environments (CoRE) Resource Directory
Normatively referenced by — RFC 9711: The Entity Attestation Token (EAT)
Normatively referenced by — RFC 9528: Ephemeral Diffie-Hellman Over COSE (EDHOC)
Normatively referenced by — RFC 8075: Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)
Normatively referenced by — RFC 8768: Constrained Application Protocol (CoAP) Hop-Limit Option
Normatively referenced by — RFC 8782: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
Normatively referenced by — RFC 9193: Sensor Measurement Lists (SenML) Fields for Indicating Data Value Content-Format
Normatively referenced by — RFC 9244: Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry
Normatively referenced by — RFC 8352: Energy-Efficient Features of Internet of Things Protocols
Normatively referenced by — RFC 9202: Datagram Transport Layer Security (DTLS) Profile for Authentication and Authorization for Constrained Environments (ACE)
Normatively referenced by — RFC 9203: The Object Security for Constrained RESTful Environments (OSCORE) Profile of the Authentication and Authorization for Constrained Environments (ACE) Framework
Normatively referenced by — RFC 9482: Constrained Application Protocol (CoAP) Transfer for the Certificate Management Protocol
Normatively referenced by — RFC 8710: Multipart Content-Format for the Constrained Application Protocol (CoAP)
Normatively referenced by — RFC 9148: EST-coaps: Enrollment over Secure Transport with the Secure Constrained Application Protocol
Normatively referenced by — RFC 9290: Concise Problem Details for Constrained Application Protocol (CoAP) APIs
Normatively referenced by — RFC 9362: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission
Normatively referenced by — RFC 9363: A YANG Data Model for Static Context Header Compression (SCHC)
Normatively referenced by — RFC 9952: Application-Layer Protocol Negotiation (ALPN) ID for CoAP over DTLS
Normatively referenced by — RFC 9953: DNS over CoAP (DoC)
Normatively referenced by — RFC 7650: A Constrained Application Protocol (CoAP) Usage for REsource LOcation And Discovery (RELOAD)
Normatively referenced by — RFC 9237: An Authorization Information Format (AIF) for Authentication and Authorization for Constrained Environments (ACE)
Normatively referenced by — RFC 9472: A YANG Data Model for Reporting Software Bills of Materials (SBOMs) and Vulnerability Information
Normatively referenced by — RFC 9668: Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE)
Normatively referenced by — RFC 9770: Notification of Revoked Access Tokens in the Authentication and Authorization for Constrained Environments (ACE) Framework
Normatively referenced by — RFC 9820: Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP)
Normatively referenced by — RFC 9995: CBOR Object Signing and Encryption (COSE) Hash Envelope
Normatively referenced by — RFC 9999: Remote ATtestation procedureS (RATS) Conceptual Message Wrapper (CMW)
Normatively referenced by — RFC 10013: Entity Attestation Token (EAT) Measured Component
Informatively referenced by — RFC 8152: CBOR Object Signing and Encryption (COSE)
Informatively referenced by — RFC 9052: CBOR Object Signing and Encryption (COSE): Structures and Process
Informatively referenced by — RFC 9053: CBOR Object Signing and Encryption (COSE): Initial Algorithms
Informatively referenced by — RFC 9483: Lightweight Certificate Management Protocol (CMP) Profile
Informatively referenced by — RFC 7554: Using IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the Internet of Things (IoT): Problem Statement
Informatively referenced by — RFC 9201: Additional OAuth Parameters for Authentication and Authorization for Constrained Environments (ACE)
Informatively referenced by — RFC 9254: Encoding of Data Modeled with YANG in the Concise Binary Object Representation (CBOR)
Informatively referenced by — RFC 9277: On Stable Storage for Items in Concise Binary Object Representation (CBOR)
Informatively referenced by — RFC 7547: Management of Networks with Constrained Devices: Problem Statement and Requirements
Informatively referenced by — RFC 8387: Practical Considerations and Implementation Experiences in Securing Smart Object Networks
Informatively referenced by — RFC 8307: Well-Known URIs for the WebSocket Protocol
Informatively referenced by — RFC 8763: Deployment Considerations for Information-Centric Networking (ICN)
Informatively referenced by — RFC 9006: TCP Usage Guidance in the Internet of Things (IoT)
Informatively referenced by — RFC 9442: Static Context Header Compression (SCHC) over Sigfox Low-Power Wide Area Network (LPWAN)