<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-core-coap-tcp-tls" target="https://datatracker.ietf.org/doc/html/draft-ietf-core-coap-tcp-tls-01">
   <front>
      <title>A TCP and TLS Transport for the Constrained Application Protocol (CoAP)</title>
      <author initials="C." surname="Bormann" fullname="Carsten Bormann">
         </author>
      <author initials="S." surname="Lemay" fullname="Simon Lemay">
         </author>
      <author initials="Z." surname="Technologies" fullname="Zebra Technologies">
         </author>
      <author initials="H." surname="Tschofenig" fullname="Hannes Tschofenig">
         </author>
      <date month="November" day="19" year="2015" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-core-coap-tcp-tls-01" />
   
</reference>
