metasystema.org
UpdatedPROPOSED STANDARDIETF stream

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

Still current, but amended. Parts of this document are changed or extended by RFC 8974. Read both.

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC8323
Published
February 2018
Authors
C. Bormann; S. Lemay; H. Tschofenig; K. Hartke; B. Silverajan; B. Raymor
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
54
Also known as
—
Updates:
RFC 7641, RFC 7959
Updated by:
RFC 8974

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8323-coap-constrained-application-protocol-over-tcp-tls-and-websockets