CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets

Metadata

Publisher: IETF
Doc Type: Standard
Abstract: The Constrained Application Protocol (CoAP), although inspired by HTTP, was designed to use UDP instead of TCP. The message layer of CoAP over UDP includes support for reliable delivery, simple congestion control, and flow control. Some environments benefit from the availability of CoAP carried over reliable transports such as TCP or Transport Layer Security (TLS). This document outlines the changes required to use CoAP over TCP, TLS, and WebSockets transports. It also formally updates RFC 7641 for use with these transports and RFC 7959 to enable the use of larger messages over a reliable transport.
Publication Date: 2018-02-01
Status Note: Proposed Standard
DOI: 10.17487/RFC8323
Link: https://doi.org/10.17487/RFC8323
Author(s): Carsten Bormann, Simon Lemay, Hannes Tschofenig, Klaus Hartke, Bill Silverajan, Brian Raymor
Keyword(s): CoAP, Constrained Application Protocol, REST, IoT, Internet Of Things, NAT Traversal, CoAP In Browsers

Latest version of IETF RFC 8323

Document Versions — IETF RFC 8323

▶ IETF RFC 8323 (2018-02-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Amended by:

RFC8974 NOT IN REGISTRY

Normative Reference(s)

IETF RFC 2119 [Active*]
IETF RFC 3986 [Active, Amended]
IETF RFC 5234 (2008, January) [Active, Amended]
IETF RFC 5246 [Superseded]
IETF RFC 5785 [Superseded]
RFC6066 NOT IN REGISTRY
RFC6455 NOT IN REGISTRY
RFC7252 NOT IN REGISTRY
RFC7301 NOT IN REGISTRY
RFC7525 NOT IN REGISTRY
RFC7595 NOT IN REGISTRY
RFC7641 NOT IN REGISTRY
RFC7925 NOT IN REGISTRY
RFC793 NOT IN REGISTRY
RFC7959 NOT IN REGISTRY
RFC8126 NOT IN REGISTRY
RFC8174 NOT IN REGISTRY
RFC8307 NOT IN REGISTRY

Bibliographic Reference(s)

10.1145-1879141.1879174 NOT IN REGISTRY
10.48550-arXiv.1612.07816 NOT IN REGISTRY
IAB.IETF-SAD.20110214 NOT IN REGISTRY
IANA.URI NOT IN REGISTRY
IETF.96P-QUIC.201607 NOT IN REGISTRY
IETF.draft-byrne-opsec-udp-advisory-00 NOT IN REGISTRY
IETF.draft-ietf-core-cocoa-02 NOT IN REGISTRY
IETF.draft-ietf-core-object-security-08 NOT IN REGISTRY
IETF.draft-ietf-lwig-tcp-constrained-node-networks-01 NOT IN REGISTRY
IETF.draft-silverajan-core-coap-alternative-transports-10 NOT IN REGISTRY
IETF.draft-thaler-appsawg-multi-transport-uris-01 NOT IN REGISTRY
OMA.TS-LightweightM2M.V1_0.20170208 NOT IN REGISTRY
RFC6335 NOT IN REGISTRY
RFC6347 NOT IN REGISTRY
IETF RFC 7230 [Active, Amended]
RFC7540 NOT IN REGISTRY
RFC768 NOT IN REGISTRY

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC8323.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 8323, CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets. Available at https://doi.org/10.17487/RFC8323

Snippet:

IETF RFC 8323, CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets. Available at https://doi.org/10.17487/RFC8323

HTML (ISO 690 compliant)

Preview:

IETF RFC 8323, CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets. Available at https://doi.org/10.17487/RFC8323

Snippet:

<span class="citation"><cite>IETF RFC 8323</cite>, CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets. Available at <a href="https://doi.org/10.17487/RFC8323" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8323</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 8323, CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets
doi: 10.17487/RFC8323
url: https://doi.org/10.17487/RFC8323

Snippet:

<li>
<cite id="bib-rfc8323">IETF RFC 8323</cite>, CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets
<span class="doi">10.17487/RFC8323</span>
</li>

Referenced By

IETF RFC 8615 [Active*]