@misc{rfc8323,
    series =    {Request for Comments},
    number =    8323,
    howpublished =  {RFC 8323},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC8323},
    url =       {https://www.rfc-editor.org/info/rfc8323},
    author =    {Carsten Bormann and Simon Lemay and Hannes Tschofenig and Klaus Hartke and Bill Silverajan and Brian Raymor},
    title =     {{CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets}},
    pagetotal = 54,
    year =      2018,
    month =     feb,
    abstract =  {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.},
}