CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets
RFC 8323
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['CoAP', 'Constrained Application Protocol', 'REST', 'IoT', 'Internet of Things', 'NAT Traversal', 'CoAP in Browsers']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "B. Raymor": changed name from "Brian Raymor" to "B. Raymor", changed is_editor from "False" to "True", changed order from "5" to "6" |
|
2026-05-20
|
(System) | Changed author "B. Silverajan": changed name from "Bill Silverajan" to "B. Silverajan", cleared country (was "Finland"), changed order from "4" to "5" |
|
2026-05-20
|
(System) | Changed author "K. Hartke": changed name from "Klaus Hartke" to "K. Hartke", cleared country (was "Germany"), changed order from "3" to "4" |
|
2026-05-20
|
(System) | Changed author "H. Tschofenig": changed name from "Hannes Tschofenig" to "H. Tschofenig", cleared country (was "Great Britain"), changed order from "2" to "3" |
|
2026-05-20
|
(System) | Changed author "S. Lemay": changed name from "Simon Lemay" to "S. Lemay", cleared country (was "United States of America"), changed order from "1" to "2" |
|
2026-05-20
|
(System) | Changed author "C. Bormann": changed name from "Carsten Bormann" to "C. Bormann", cleared country (was "Germany"), changed order from "0" to "1" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2020-09-10
|
Marco Tiloca | Changed document external resources from: [] to: github_repo https://github.com/core-wg/coap-tcp-tls (Working Group Repo) |
|
2018-12-19
|
(System) | Received changes through RFC Editor sync (changed abstract to 'The Constrained Application Protocol (CoAP), although inspired by HTTP, was designed to use UDP instead of … Received changes through RFC Editor sync (changed abstract to '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.') |
|
2018-11-01
|
(System) | Received changes through RFC Editor sync (created updates relation between draft-ietf-core-coap-tcp-tls and RFC 7959) |
|
2018-02-20
|
(System) | IANA registries were updated to include RFC8323 |
|
2018-02-14
|
(System) | Received changes through RFC Editor sync (created alias RFC 8323, changed abstract to 'The Constrained Application Protocol (CoAP), although inspired by HTTP, was designed … Received changes through RFC Editor sync (created alias RFC 8323, changed abstract to '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.', changed pages to 54, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-02-14, changed IESG state to RFC Published, created updates relation between draft-ietf-core-coap-tcp-tls and RFC 7641, created updates relation between draft-ietf-core-coap-tcp-tls and RFC 7959) |
|
2018-02-14
|
(System) | RFC published |