DNS Transport over TCP - Implementation Requirements
draft-ietf-dnsop-5966bis-01

The information below is for an old version of the document
Document Type Active Internet-Draft (dnsop WG)
Authors John Dickinson  , Ray Bellis  , Allison Mankin  , Duane Wessels 
Last updated 2015-06-26 (latest revision 2015-03-09)
Replaces draft-dickinson-dnsop-5966-bis
Stream IETF
Intended RFC status Internet Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
dnsop                                                       J. Dickinson
Internet-Draft                             Sinodun Internet Technologies
Obsoletes: 5966 (if approved)                                  R. Bellis
Intended status: Standards Track                                 Nominet
Expires: September 10, 2015                                    A. Mankin
                                                              D. Wessels
                                                           Verisign Labs
                                                           March 9, 2015

          DNS Transport over TCP - Implementation Requirements
                      draft-ietf-dnsop-5966bis-01

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 10, 2015.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Dickinson, et al.      Expires September 10, 2015               [Page 1]
Internet-Draft                DNS over TCP                    March 2015

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Terminology  . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Transport Protocol Selection  . . . . . . . . . . . . . . . .   4
   6.  Connection Handling . . . . . . . . . . . . . . . . . . . . .   5
   7.  Query Pipelining  . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Response Reordering . . . . . . . . . . . . . . . . . . . . .   7
   9.  TCP Fast Open . . . . . . . . . . . . . . . . . . . . . . . .   8
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   11. Security Considerations . . . . . . . . . . . . . . . . . . .   8
   12. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     13.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     13.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Appendix A.  Summary of Advantages and Disadvantages to using TCP
                for DNS  . . . . . . . . . . . . . . . . . . . . . .  11
   Appendix B.  Changes -00 to -01 . . . . . . . . . . . . . . . . .  11
   Appendix C.  Changes to RFC 5966  . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   Most DNS [RFC1034] transactions take place over UDP [RFC0768].  TCP
   [RFC0793] is always used for full zone transfers (AXFR) and is often
   used for messages whose sizes exceed the DNS protocol's original
   512-byte limit.

   Section 6.1.3.2 of [RFC1123] states:

      DNS resolvers and recursive servers MUST support UDP, and SHOULD
      support TCP, for sending (non-zone-transfer) queries.

   However, some implementors have taken the text quoted above to mean
   that TCP support is an optional feature of the DNS protocol.

   The majority of DNS server operators already support TCP and the
   default configuration for most software implementations is to support
   TCP.  The primary audience for this document is those implementors
   whose failure to support TCP restricts interoperability and limits
   deployment of new DNS features.

Dickinson, et al.      Expires September 10, 2015               [Page 2]
Internet-Draft                DNS over TCP                    March 2015

   This document therefore updates the core DNS protocol specifications
Show full document text