%% You should probably cite draft-ietf-core-coap-tcp-tls instead of this I-D.
@techreport{tschofenig-core-coap-tcp-tls-00,
    number =    {draft-tschofenig-core-coap-tcp-tls-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-tschofenig-core-coap-tcp-tls/00/},
    author =    {Zebra Technologies and Hannes Tschofenig},
    title =     {{A TCP and TLS Transport for the Constrained Application Protocol (CoAP)}},
    pagetotal = 5,
    year =      2014,
    month =     sep,
    day =       3,
    abstract =  {The Hypertext Transfer Protocol (HTTP) has been designed with TCP as an underlying transport protocol. The Constrained Application Protocol (CoAP), which has been inspired by HTTP, has on the other hand been defined to make use of UDP. Reliable delivery, a simple congestion control mechanism, and flow control had been added to the CoAP protocol. UDP is a good choice for networks that do not perform any form of filtering and firewalling. There are, however, many deployment environments where UDP is either firewalled or subject to deep packet inspection. These environments make the use of CoAP brittle. This document defines the use of CoAP over TCP as well as CoAP over TLS.},
}