On 06/07/2015 18:04, internet-dra...@ietf.org wrote:
A New Internet-Draft is available from the on-line Internet-Drafts directories.
  This draft is a work item of the Domain Name System Operations Working Group 
of the IETF.

         Title           : DNS Transport over TCP - Implementation Requirements
         Authors         : John Dickinson
                           Sara Dickinson
                           Ray Bellis
                           Allison Mankin
                           Duane Wessels
        Filename        : draft-ietf-dnsop-5966bis-02.txt
        Pages           : 17
        Date            : 2015-07-06

Abstract:
    This document specifies the requirement for support of TCP as a
    transport protocol for DNS implementations and provides guidelines
    towards DNS-over-TCP performance on par with that of DNS-over-UDP.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-5966bis/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-dnsop-5966bis-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-5966bis-02


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Hi,

We have just submitted a -02 update to the 5966bis draft.

There have been significant changes made since –01 draft in light of the
comments made on list. These include:

 * Significant restructuring and re-wording of the Connection Handling
   section. Split into Current Practice and Recommendations. Provides
   more detail on current practices and divides Recommendations up into
   more granular sub-sections.
 * New text on recommendations for client idle behaviour. Added
   statement that servers MAY use 0 idle timeout.
 * Updated text on server limits on concurrent connections from a
   particular client.
 * Moved TCP message field length discussion to separate section to
   highlight its importance.
 * Added more discussion on DoS risks and mitigation in the Connection
   Handling and Security Considerations section.
 * Removed references to system calls in TFO section.
 * Added more text to Introduction as background to TCP use.
 * Added definitions of Persistent connection and Idle session to
   Terminology section.
 * Re-stated position of TCP as an alternative to UDP in Discussion.
 * Added text that client retry logic is outside the scope of this
   document.

There were a few things we didn't add/change:

 * There were suggestions on the list that both pipelining and
   out-of-order processing should only be performed after explicit
   signalling. We felt that the working group consensus was that this
   was not needed because of the behaviour of existing implementations.

We hope this document has addressed the working groups concerns and hope
that people feel it is ready to progress.

regards
John

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to