<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-dnsop-edns-tcp-keepalive" target="https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-edns-tcp-keepalive-02">
   <front>
      <title>The edns-tcp-keepalive EDNS0 Option</title>
      <author initials="P." surname="Wouters" fullname="Paul Wouters">
         </author>
      <author initials="J." surname="Abley" fullname="Joe Abley">
         </author>
      <author initials="S." surname="Dickinson" fullname="Sara Dickinson">
         </author>
      <author initials="R." surname="Bellis" fullname="Ray Bellis">
         </author>
      <date month="July" day="3" year="2015" />
      <abstract>
	 <t>   DNS messages between clients and servers may be received over either
   UDP or TCP.  UDP transport involves keeping less state on a busy
   server, but can cause truncation and retries over TCP.  Additionally,
   UDP can be exploited for reflection attacks.  Using TCP would reduce
   retransmits and amplification.  However, clients commonly use TCP
   only for fallback and servers typically use idle timeouts on the
   order of seconds.

   This document defines an EDNS0 option (&quot;edns-tcp-keepalive&quot;) that
   allows DNS servers to signal a variable idle timeout.  This
   signalling facilitates a better balance of UDP and TCP transport
   between individual clients and servers, reducing the impact of
   problems associated with UDP transport and allowing the state
   associated with TCP transport to be managed effectively with minimal
   impact on the DNS transaction time.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-dnsop-edns-tcp-keepalive-02" />
   
</reference>
