Fwd: New Version Notification for draft-wouters-edns-tcp-keepalive-00.txt (fwd)

As discussed, I separated the EDNS TCP keep-alive option from the EDNS
chain-query document, and Joe Abley kindly offered his assistance in
(re)writing this document.

Paul


-------- Original Message --------
From: [email protected]
To: Paul Wouters <[email protected]>, Joe Abley <[email protected]>
Subject: New Version Notification for draft-wouters-edns-tcp-keepalive-00.txt
Date: Tue, 15 Oct 2013 09:39:54 -0700

A new version of I-D, draft-wouters-edns-tcp-keepalive-00.txt
has been successfully submitted by Paul Wouters and posted to the
IETF repository.

Filename:	 draft-wouters-edns-tcp-keepalive
Revision:	 00
Title:		 The edns-tcp-keepalive EDNS0 Option
Creation date:	 2013-10-15
Group:		 Individual Submission
Number of pages: 9
URL:             http://www.ietf.org/internet-drafts/draft-wouters-edns-tcp-keepalive-00.txt
Status:          http://datatracker.ietf.org/doc/draft-wouters-edns-tcp-keepalive
Htmlized:        http://tools.ietf.org/html/draft-wouters-edns-tcp-keepalive-00


Abstract:
    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 are currently
    limited in their use of the TCP transport as most implementations
    limit the TCP session to a single DNS query and answer, making use of
    TCP only suitable as a fallback protocol for UDP.

    This document defines an EDNS0 option ("edns-tcp-keepalive") that
    allows DNS clients and servers to signal their respective readiness
    to conduct multiple DNS transactions over individual TCP sessions.
    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.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


_______________________________________________
dnsext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsext