A TCP transport for CoAP
draft-bormann-core-coap-tcp-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Carsten Bormann | ||
| Last updated | 2015-01-05 (latest revision 2014-07-04) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
https://www.ietf.org/archive/id/draft-bormann-core-coap-tcp-01.txt
https://www.ietf.org/archive/id/draft-bormann-core-coap-tcp-01.txt
Abstract
CoAP (RFC 7252) is defined to be transported over datagram transports such as UDP or DTLS. For a number of applications, it may be useful to channel CoAP messages in a TCP connection. This draft discusses different ways to do that.
Authors
Carsten Bormann (cabo@tzi.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)