A TCP and TLS Transport for the Constrained Application Protocol (CoAP)

Document Type Replaced Internet-Draft (individual)
Authors Carsten Bormann  , Simon Lemay  , Zebra Technologies  , Hannes Tschofenig 
Last updated 2015-11-02
Replaced by RFC 8323
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-core-coap-tcp-tls
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The Hypertext Transfer Protocol (HTTP) was designed with TCP as the underlying transport protocol. The Constrained Application Protocol (CoAP), while inspired by HTTP, has been defined to make use of UDP instead of TCP. Therefore, reliable delivery and a simple congestion control and flow control mechanism are provided by the message layer of the CoAP protocol. A number of environments benefit from the use of CoAP directly over a reliable byte stream such as TCP, which already provides these services. This document defines the use of CoAP over TCP as well as CoAP over TLS.


Carsten Bormann (cabo@tzi.org)
Simon Lemay (slemay@zebra.com)
Zebra Technologies (vsolorzanobarboza@zebra.com)
Hannes Tschofenig (Hannes.Tschofenig@gmx.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)