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

Raymor, Brian; Silverajan, Bill; Bormann, Carsten; Hartke, Klaus; Tschofenig, Hannes; Lemay, Simon

doi:10.17487/rfc8323

Cited by 51 publications

(25 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…CoAP was originally designed over UDP, with optional, stop-and-wait reliability. However, deployment experience has shown the need to enable CoAP over TCP (Figure 1.b)) or over WebSockets (WS, Figure 1.c)), in order to overcome connectivity limitations introduced by corporate firewalls [8].…”

Section: Coapmentioning

confidence: 99%

See 1 more Smart Citation

TCP in the Internet of Things: From Ostracism to Prominence

Gómez

Arcia-Moret

Crowcroft

2018

IEEE Internet Comput.

View full text Add to dashboard Cite

TCP has traditionally been neglected as a transport-layer protocol for the Internet of Things (IoT). However, recent trends and industry needs are favoring TCP presence in IoT environments. In this paper, we first motivate and describe the main IoT scenarios where TCP will be used. We then analyze the historically claimed issues of TCP in the IoT context. We argue that, in contrast to generally accepted wisdom, most of those possible issues fall in one of the following categories: i) are also found in well accepted IoT end-to-end reliability mechanisms, ii) can be solved, or iii) are not actual issues. Considering the future prominent role of TCP in the IoT, we provide recommendations for lightweight TCP implementation and suitable operation in such scenarios, based on our IETF standardization work on the topic.

show abstract

Section: Coapmentioning

confidence: 99%

“…However, the need for graceful integration of CoAP with enterprise infrastructure has recently triggered the development of a CoAP over TCP specification [8]. On the other hand, HTTP, which relies on TCP at the transport layer, has been used and is being optimized for IoT environments, leveraging its mainstream position [9].…”

Section: Introductionmentioning

confidence: 99%

TCP in the Internet of Things: From Ostracism to Prominence

Gómez

Arcia-Moret

Crowcroft

2018

IEEE Internet Comput.

View full text Add to dashboard Cite

show abstract

“…Since duty cycling at the link layer may lead to long latency (i.e., even greater than the initial RTO value), CoAP RTO parameters should be tuned accordingly in order to avoid spurious RTOs that would unnecessarily waste node energy and other resources. On the other hand, note that CoAP can also run on top of TCP [RFC8323]. In that case, similar guidance applies to TCP timers, albeit with greater motivation to carefully configure TCP RTO parameters since [RFC6298] reduced the default initial TCP RTO to 1 second, which may interact more negatively with duty-cycled links than default CoAP RTO values.…”

Section: Coap Timersmentioning

confidence: 99%

Energy-Efficient Features of Internet of Things Protocols

Gómez¹,

Tian²,

Cao³

et al. 2018

View full text Add to dashboard Cite

This document describes the challenges for energy-efficient protocol operation on constrained devices and the current practices used to overcome those challenges. It summarizes the main link-layer techniques used for energy-efficient networking, and it highlights the impact of such techniques on the upper-layer protocols so that they can together achieve an energy-efficient behavior. The document also provides an overview of energy-efficient mechanisms available at each layer of the IETF protocol suite specified for constrained-node networks.

show abstract

“…В протоколе Etherbox программы (проглеты) представляются в виде байт-кода спе-циализированной виртуальной машины Etherbox32vm [10], который интерпретируется без предварительной подготовки. 6 CoAP использует UDP, но в настоящее время также разрабатывается версия CoAP на основе TCP [23] для случаев, когда прохождение пакетов UDP затруднено брандмауэрами или NAT.…”

Section: протокол Etherboxunclassified