dprive                                                         W. Toorop
Internet-Draft                                                NLnet Labs
Updates: 1995, 5936, 7766 (if approved)                     S. Dickinson
Intended status: Standards Track                              Sinodun IT
Expires: October 22, 27 November 2021                                       S. Sahib
                                                          Brave Software
                                                                 P. Aras
                                                               A. Mankin
                                                          April 20,
                                                             26 May 2021

                       DNS Zone Transfer-over-TLS


   DNS zone transfers are transmitted in clear text, which gives
   attackers the opportunity to collect the content of a zone by
   eavesdropping on network connections.  The DNS Transaction Signature
   (TSIG) mechanism is specified to restrict direct zone transfer to
   authorized clients only, but it does not add confidentiality.  This
   document specifies the use of TLS, rather than clear text, to prevent
   zone content collection via passive monitoring of zone transfers:
   XFR-over-TLS (XoT).  Additionally, this specification updates
   RFC1995, RFC1995
   and RFC5936 with respect to efficient use of TCP connections, and RFC7766.
   RFC7766 with respect to the recommended number of connections between
   a client and server for each transport.

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/. https://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 October 22, 27 November 2021.

Copyright Notice

   Copyright (c) 2021 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) (https://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 the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Document work via GitHub  . . . . . . . . . . . . . . . . . .   5   6
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5   6
   4.  Threat Model  . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Design Considerations for XoT . . . . . . . . . . . . . . . .   6   7
   6.  Connection and Data Flows in Existing XFR Mechanisms  . . . .   7   8
     6.1.  AXFR Mechanism  . . . . . . . . . . . . . . . . . . . . .   8
     6.2.  IXFR Mechanism  . . . . . . . . . . . . . . . . . . . . .   9  10
     6.3.  Data Leakage of NOTIFY and SOA Message Exchanges  . . . .  11
       6.3.1.  NOTIFY  . . . . . . . . . . . . . . . . . . . . . . .  11
       6.3.2.  SOA . . . . . . . . . . . . . . . . . . . . . . . . .  11  12
   7.  Updates to existing specifications  . . . . . . . . . . . . .  11  12
     7.1.  Update to RFC1995 for IXFR-over-TCP . . . . . . . . . . .  13
     7.2.  Update to RFC5936 for AXFR-over-TCP . . . . . . . . . . .  13  14
     7.3.  Updates to RFC1995 and RFC5936 for XFR-over-TCP . . . . .  13  14
       7.3.1.  Connection reuse  . . . . . . . . . . . . . . . . . .  13  14
       7.3.2.  AXFRs and IXFRs on the same connection  . . . . . . .  14  15
       7.3.3.  XFR limits  . . . . . . . . . . . . . . . . . . . . .  14  15
       7.3.4.  The edns-tcp-keepalive EDNS0 Option . . . . . . . . .  15
       7.3.5.  Backwards compatibility . . . . . . . . . . . . . . .  15  16
     7.4.  Update to RFC7766 . . . . . . . . . . . . . . . . . . . .  15  16
   8.  XoT specification . . . . . . . . . . . . . . . . . . . . . .  17
     8.1.  Connection establishment  . . . . . . . . . . . . . . . .  17
     8.2.  TLS versions  . . . . . . . . . . . . . . . . . . . . . .  17
     8.3.  Port selection  . . . . . . . . . . . . . . . . . . . . .  17
     8.3.  18
     8.4.  High level XoT descriptions . . . . . . . . . . . . . . .  17
     8.4.  18
     8.5.  XoT transfers . . . . . . . . . . . . . . . . . . . . . .  19
     8.5.  20
     8.6.  XoT connections . . . . . . . . . . . . . . . . . . . . .  20
     8.6.  21
     8.7.  XoT vs ADoT . . . . . . . . . . . . . . . . . . . . . . .  20
     8.7.  21
     8.8.  Response RCODES . . . . . . . . . . . . . . . . . . . . .  21
     8.8.  22
     8.9.  AXoT specifics  . . . . . . . . . . . . . . . . . . . . .  21
       8.8.1.  22
       8.9.1.  Padding AXoT responses  . . . . . . . . . . . . . . .  21
     8.9.  22

     8.10. IXoT specifics  . . . . . . . . . . . . . . . . . . . . .  22
       8.9.1.  23
       8.10.1.  Condensation of responses  . . . . . . . . . . . . . .  22
       8.9.2.  23
       8.10.2.  Fallback to AXFR . . . . . . . . . . . . . . . . . .  22
       8.9.3.  24
       8.10.3.  Padding of IXoT responses  . . . . . . . . . . . . . .  23
     8.10.  24
     8.11. Name compression and maximum payload sizes  . . . . . . .  23  24
   9.  Multi-primary Configurations  . . . . . . . . . . . . . . . .  23  25
   10. Authentication mechanisms . . . . . . . . . . . . . . . . . .  24  26
     10.1.  TSIG . . . . . . . . . . . . . . . . . . . . . . . . . .  25  26
     10.2.  SIG(0) . . . . . . . . . . . . . . . . . . . . . . . . .  25  26
     10.3.  TLS  . . . . . . . . . . . . . . . . . . . . . . . . . .  25  26
       10.3.1.  Opportunistic TLS  . . . . . . . . . . . . . . . . .  25  27
       10.3.2.  Strict TLS . . . . . . . . . . . . . . . . . . . . .  26  27
       10.3.3.  Mutual TLS . . . . . . . . . . . . . . . . . . . . .  26  27
     10.4.  IP Based ACL on the Primary  . . . . . . . . . . . . . .  26  28
     10.5.  ZONEMD . . . . . . . . . . . . . . . . . . . . . . . . .  27  28
   11. XoT authentication  . . . . . . . . . . . . . . . . . . . . .  27  28
   12. Policies for Both AXoT and IXoT . . . . . . . . . . . . . . .  28  29
   13. Implementation Considerations . . . . . . . . . . . . . . . .  29  30
   14. Operational Considerations  . . . . . . . . . . . . . . . . .  29  30
   15. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  29  31
   16. Implementation Status . . . . . . . . . . . . . . . . . . . .  29  31
   17. Security Considerations . . . . . . . . . . . . . . . . . . .  30  31
   18. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  30  32
   19. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  31  32
   20. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . .  31  32
   21. References  . . . . . . . . . . . . . . . . . . . . . . . . .  33
     21.1. Normative References  . . . . . . . . . . . . . . . . . .  33
     21.2.  Informative References . . . . . . . . . . . . . . . . .  35
     21.3.  URIs . . . . . . .
   22. Informative References  . . . . . . . . . . . . . . . . . . .  36  37
   Appendix A.  XoT server connection handling . . . . . . . . . . .  37  39
     A.1.  Only listen on TLS on a specific IP address . . . . . . .  37  39
     A.2.  Client specific TLS acceptance  . . . . . . . . . . . . .  37  39
     A.3.  SNI based TLS acceptance  . . . . . . . . . . . . . . . .  37  40
     A.4.  TLS  Transport specific response policies  . . . . . . . . . . . . .  38  40
       A.4.1.  SNI based response policies . . . . . . . . . . . . .  39  41
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  39  41

1.  Introduction

   DNS has a number of privacy vulnerabilities, as discussed in detail
   in [I-D.ietf-dprive-rfc7626-bis].  Stub client to recursive resolver
   query privacy has received the most attention to date, with standards
   track documents for both DNS-over-TLS (DoT) [RFC7858] and DNS-over-
   HTTPS (DoH) [RFC8484], and a proposal for DNS-over-QUIC
   [I-D.ietf-dprive-dnsoquic].  There is ongoing work on DNS privacy
   requirements for exchanges between recursive resolvers and
   authoritative servers [I-D.ietf-dprive-phase2-requirements] and some
   suggestions for how signaling of DoT support by authoritatives authoritative
   nameservers might work.  However  However, there is currently no RFC that
   specifically defines recursive to authoritative DNS-over-TLS (ADoT).

   [I-D.ietf-dprive-rfc7626-bis] established that stub client DNS query
   transactions are not public and needed protection, but on zone
   transfer [RFC1995] [RFC5936] it says only:

   "Privacy risks for the holder of a zone (the risk that someone
   gets the data) are discussed in [RFC5936] and [RFC5155]."

   In what way is exposing the full contents of a zone a privacy risk?
   The contents of the zone could include information such as names of
   persons used in names of hosts.  Best practice is not to use personal
   information for domain names, but many such domain names exist.  The
   contents of the zone could also include references to locations that
   allow inference about location information of the individuals
   associated with the zone's organization.  It could also include
   references to other organizations.  Examples of this could be:


   *  Person-laptop.example.org


   *  MX-for-Location.example.org


   *  Service-tenant-from-another-org.example.org

   Additionally, the full zone contents expose all the IP addresses of
   endpoints held in the DNS records which can make reconnaissance
   trivial, and
   attack targeting easier, particularly for IPv6 addresses. addresses or private
   networks.  There may also be regulatory, policy or other reasons why
   the zone contents in full must be treated as private.

   Neither of the RFCs mentioned in [I-D.ietf-dprive-rfc7626-bis]
   contemplates the risk that someone gets the data through
   eavesdropping on network connections, only via enumeration or
   unauthorized transfer as described in the following paragraphs.

   Zone enumeration is trivially possible for DNSSEC zones which use
   NSEC; i.e. queries for the authenticated denial of existences existence records
   allow a client to walk through the entire zone contents.  [RFC5155]
   specifies NSEC3, a mechanism to provide measures against zone
   enumeration for DNSSEC signed zones (a goal was to make it as hard to
   enumerate an a DNSSEC signed zone as an unsigned zone).  Whilst this is
   widely used, it has been demonstrated that zone walking is now possible with
   for precomputed NSEC3 due to
   crypto-breaking advances.  This has prompted further work using attacks such as those described in
   [NSEC3-attacks].  This prompted further work on an alternative
   mechanism for DNSSEC authenticated denial of existence - NSEC5
   [I-D.vcelak-nsec5] - however questions remain over the practicality
   of this mechanism.

   [RFC5155] does not address data obtained outside zone enumeration
   (nor does [I-D.vcelak-nsec5]).  Preventing eavesdropping of zone
   transfers (this draft) document) is orthogonal to preventing zone
   enumeration, though they aim to protect the same information.

   [RFC5936] specifies using TSIG [RFC8945] for authorization of the
   clients of a zone transfer and for data integrity, but does not
   express any need for confidentiality, and TSIG does not offer

   Section 8 of the NIST guide on 'Secure Domain Name System (DNS)
   Deployment' [nist-guide] discusses restricting access for zone
   transfers using ACLs and TSIG in more detail.  It also discusses the
   possibility that specific deployments might choose to use a lower
   level network layer to protect zone transfers, e.g., IPSec.

   It is noted that in all the common open source implementations such
   ACLs are applied on a per query basis. basis (at the time of writing).
   Since requests typically occur on TCP connections authoritatives must cater for accepting
   therefore accept any TCP connection and then handling the
   authentication of each XFR zone transfer (XFR) request individually.

   Because both AXFR (authoritative transfer) and IXFR zone transfers (incremental
   transfer) are typically carried out over TCP from authoritative DNS
   protocol implementations, encrypting zone transfers using TLS, TLS
   [RFC8499], based closely on DoT [RFC7858], seems like a simple step
   forward.  This document specifies how to use TLS (1.3 or later) as a
   transport to prevent zone collection from zone transfers.

   This document also updates the previous specifications for zone
   transfers to clarify and extend them, mainly with respect to TCP

   *  RFC1995 (IXFR) and RFC5936 (AXFR) are both updated to add further
      specification on efficient use of TCP connections

   *  Section 6.2.2 of RFC7766 (DNS Transport over TCP - Implementation
      Requirements) is updated with a new recommendation about the
      number of connections between a client and server for each

2.  Document work via GitHub

   for this document is at <https://github.com/hanzhang0116/hzpa-dprive-
   xfr-over-tls>. https://github.com/hanzhang0116/hzpa-dprive-
   xfr-over-tls (https://github.com/hanzhang0116/hzpa-dprive-xfr-over-
   tls).  Proposed text and editorial changes are very much welcomed
   there, but any functional changes should always first be discussed on
   the IETF DPRIVE WG (dns-privacy) mailing list.

3.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] and [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

   Privacy terminology is as described in Section 3 of [RFC6973].

   DNS terminology is as described in [RFC8499].  Note that as in
   [RFC8499], the terms 'primary' and 'secondary' are used for two
   servers engaged in zone transfers.

   DoT: DNS-over-TLS as specified in [RFC7858]

   XFR-over-TCP: Used to mean both IXFR-over-TCP [RFC1995] and AXFR-
   over-TCP [RFC5936].

   XoT: XFR-over-TLS mechanisms as specified in this document which
   apply to both AXFR-over-TLS and IXFR-over-TLS

   AXoT: AXFR-over-TLS

   IXoT: IXFR over-TLS

4.  Threat Model

   The threat model considered here is one where the current contents
   and size of the zone are considered sensitive and should be protected
   during transfer.

   The threat model does not, however, consider the existence of a zone,
   the act of zone transfer between two entities, nor the identities of
   the nameservers hosting a zone (including both those acting as hidden
   primaries/secondaries or directly serving the zone) as sensitive
   information.  The proposed mechanisms mechanism does not attempt to obscure such
   information.  The reasons for this include:


   *  much of this information can be obtained by various methods methods,
      including active scanning of the DNS


   *  an attacker who can monitor network traffic can relatively easily
      infer relations between nameservers simply from traffic patterns,
      even when some or all of the traffic is encrypted (in terms of
      current deployments)

   The model does not consider attacks on the mechanisms that trigger a
   zone transfer, e.g., NOTIFY messages.

   It is noted that simply using XoT will indicate a desire by the zone
   owner that the contents of the zone remain confidential and so could
   be subject to blocking (e.g., via blocking of port 853) if an
   attacker had such capabilities.  However this threat is likely true
   of any such mechanism that attempts to encrypt data passed between
   nameservers, e.g., IPsec.

5.  Design Considerations for XoT


   The following principles were considered in the design for XoT:

   *  Confidentiality.  Clearly using an encrypted transport for zone
      transfers will defeat zone content leakage that can occur via
      passive surveillance.


   *  Authentication.  Use of single or mutual TLS (mTLS) authentication
      (in combination with ACLs) access control lists (ACLs)) can complement
      and potentially be an alternative to TSIG.

   o  Performance.

   *  Performance.

      -  Existing AXFR and IXFR mechanisms have the burden of backwards
         compatibility with older implementations based on the original
         specifications in [RFC1034] and [RFC1035].  For example, some
         older AXFR servers don't support using a TCP connection for
         multiple AXFR sessions or XFRs of different zones because they
         have not been updated to follow the guidance in [RFC5936].  Any
         implementation of XoT would obviously be required to implement
         optimized and interoperable transfers as described in
         [RFC5936], e.g., transfer of multiple zones over one


      -  Current usage of TCP for IXFR is sub-optimal in some cases i.e.
         connections are frequently closed after a single IXFR.

6.  Connection and Data Flows in Existing XFR Mechanisms

   The original specification for zone transfers in [RFC1034] and
   [RFC1035] was based on a polling mechanism: a secondary performed a
   periodic SOA query for the SOA (start of zone authority) record (based on
   the refresh timer) to determine if an AXFR was required.

   [RFC1995] and [RFC1996] introduced the concepts of IXFR and NOTIFY
   respectively, to provide for prompt propagation of zone updates.
   This has largely replaced AXFR where possible, particularly for
   dynamically updated zones.

   [RFC5936] subsequently redefined the specification of AXFR to improve
   performance and interoperability.

   In this document we use the term "XFR mechanism" to describe the
   entire set of message exchanges between a secondary and a primary
   that concludes in a successful AXFR or IXFR request/response.  This
   set may or may not include


   *  NOTIFY messages


   *  SOA queries


   *  Fallback from IXFR to AXFR


   *  Fallback from IXFR-over-UDP to IXFR-over-TCP

   The term is used to encompasses encompass the range of permutations that are
   possible and is useful to distinguish the 'XFR mechanism' from a
   single XFR request/response exchange.

6.1.  AXFR Mechanism

   The figure below provides an outline of an AXFR mechanism including

      Secondary                            Primary

          |              NOTIFY               |
          | <-------------------------------- |  UDP
          | --------------------------------> |
          |          NOTIFY Response          |
          |                                   |
          |                                   |
          |            SOA Request            |
          | --------------------------------> |  UDP (or part of
          | <-------------------------------- |  a TCP session)
          |           SOA Response            |
          |                                   |
          |                                   |
          |                                   |
          |            AXFR Request           | ---
          | --------------------------------> |   |
          | <-------------------------------- |   |
          |          AXFR Response 1          |   |
          |             (Zone data)           |   |
          |                                   |   |
          | <-------------------------------- |   | TCP
          |          AXFR Response 2          |   | Session
          |             (Zone data)           |   |
          |                                   |   |
          | <-------------------------------- |   |
          |          AXFR Response 3          |   |
          |             (Zone data)           | ---
          |                                   |

                 Figure 1. AXFR Mechanism

   1.  An AXFR is often (but not always) preceded by a NOTIFY (over UDP)
       from the primary to the secondary.  A secondary may also initiate
       an AXFR based on a refresh timer or scheduled/triggered zone

   2.  The secondary will normally (but not always) make a SOA query to
       the primary to obtain the serial number of the zone held by the

   3.  If the primary serial is higher than the secondaries secondary's serial
       (using Serial Number Arithmetic [RFC1982]), the secondary makes
       an AXFR request (over TCP) to the primary after which the AXFR
       data flows in one or more AXFR responses on the TCP connection.
       [RFC5936] defines this specific step as an 'AXFR session' i.e. as
       an AXFR query message and the sequence of AXFR response messages
       returned for it.

   [RFC5936] re-specified AXFR providing additional guidance beyond that
   provided in [RFC1034] and [RFC1035] and importantly specified that
   AXFR must use TCP as the transport protocol.

   Additionally, sections 4.1, 4.1.1 and 4.1.2 of [RFC5936] provide
   improved guidance for AXFR clients and servers with regard to re-use
   of TCP connections for multiple AXFRs and AXFRs of different zones.
   However [RFC5936] was constrained by having to be backwards
   compatible with some very early basic implementations of AXFR.  For
   example, it outlines that the SOA query can also happen on this
   connection.  However, this can cause interoperability problems with
   older implementations that support only the trivial case of one AXFR
   per connection.

6.2.  IXFR Mechanism

   The figure below provides an outline of the IXFR mechanism including

      Secondary                            Primary

          |              NOTIFY               |
          | <-------------------------------- |  UDP
          | --------------------------------> |
          |          NOTIFY Response          |
          |                                   |
          |                                   |
          |            SOA Request            |
          | --------------------------------> |  UDP or TCP
          | <-------------------------------- |
          |           SOA Response            |
          |                                   |
          |                                   |
          |                                   |
          |            IXFR Request           |
          | --------------------------------> |  UDP or TCP
          | <-------------------------------- |
          |            IXFR Response          |
          |             (Zone data)           |
          |                                   |
          |                                   | ---
          |            IXFR Request           |    |
          | --------------------------------> |    | Retry over
          | <-------------------------------- |    | TCP if
          |            IXFR Response          |    | required
          |             (Zone data)           | ---

                 Figure 2. IXFR Mechanism

   1.  An IXFR is normally (but not always) preceded by a NOTIFY (over
       UDP) from the primary to the secondary.  A secondary may also
       initiate an IXFR based on a refresh timer or scheduled/triggered
       zone maintenance.

   2.  The secondary will normally (but not always) make a SOA query to
       the primary to obtain the serial number of the zone held by the

   3.  If the primary serial is higher than the secondaries serial
       (using Serial Number Arithmetic [RFC1982]), the secondary makes
       an IXFR request to the primary after which the primary sends an
       IXFR response.

   [RFC1995] specifies that Incremental Transfer may use UDP if the
   entire IXFR response can be contained in a single DNS packet,
   otherwise, TCP is used.  In fact it says:

   "Thus, a client should first make an IXFR query using UDP."

   So there may be a fourth step above where the client falls back to
   IXFR-over-TCP.  There may also be a fourth additional step where the
   secondary must fall back to AXFR because, e.g., the primary does not
   support IXFR.

   However it is noted that most widely used open source authoritative
   nameserver implementations (including both [BIND] and [NSD]) do IXFR
   using TCP by default in their latest releases.  For BIND BIND, TCP
   connections are sometimes used for SOA queries but in general they
   are not used persistently and close after an IXFR is completed.

6.3.  Data Leakage of NOTIFY and SOA Message Exchanges

   This section attempts to presents a rationale for considering encrypting the
   other messages in the XFR mechanism.

   Since the SOA of the published zone can be trivially discovered by
   simply querying the publicly available authoritative servers servers, leakage
   of this RR resource record (RR) via such a direct query is not discussed
   in the following sections.

6.3.1.  NOTIFY

   Unencrypted NOTIFY messages identify configured secondaries on the

   [RFC1996] also states:

   "If ANCOUNT>0, then the answer section represents an
   unsecure hint at the new RRset for this (QNAME,QCLASS,QTYPE).

   But since the only supported QTYPE for NOTIFY defined at the time of this
   writing is SOA, this does not pose a potential leak.

6.3.2.  SOA

   For hidden XFR servers (either primaries or secondaries the secondaries), an SOA
   response leaks directly from that server only additionally leaks the degree
   of SOA serial number lag of any downstream secondary. secondary of that server.

7.  Updates to existing specifications

   For convenience, the term 'XFR-over-TCP' is used in this document to
   mean both IXFR-over-TCP and AXFR-over-TCP and therefore statements
   that use that term update both [RFC1995] and [RFC5936], and
   implicitly also apply to XoT.  Differences in behavior specific to
   XoT are discussed in Section 8.

   Both [RFC1995] and [RFC5936] were published sometime before TCP was
   considered a first class transport for DNS.  [RFC1995], in fact, says
   nothing with respect to optimizing IXFRs over TCP or re-using already
   open TCP connections to perform IXFRs or other queries.  Therefore,
   there arguably is an implicit assumption that a TCP connection is
   used for one and only one IXFR request.  Indeed, many major open
   source implementations currently take this approach. approach (at the time of this
   writing).  And whilst [RFC5936] gives guidance on connection re-use
   for AXFR, it pre-dates more recent specifications describing
   persistent TCP connections,
   e.g., connections (e.g., [RFC7766], [RFC7828] [RFC7828]), and AXFR
   implementations again often make less than optimal use of open

   Given this, new implementations of XoT will clearly benefit from
   specific guidance on TCP/TLS connection usage for XFR XFR, because this


   *  result in more consistent XoT implementations with better


   *  remove any need for XoT implementations to support legacy behavior
      for XoT connections that XFR-over-TCP implementations have
      historically often supported

   Therefore this document updates both the previous specifications for
   XFR-over-TCP ([RFC1995] and [RFC5936]) to clarify that

   *  Implementations MUST use [RFC7766] (DNS Transport over TCP -
      Implementation Requirements) to optimize the use of TCP


   *  Whilst RFC7766 states that 'DNS clients SHOULD pipeline their
      queries' on TCP connections, it did not distinguish between XFRs
      and other queries for this behavior.  It is now recognized that
      XFRs are not as latency sensitive as other queries, and can be
      significantly more complex for clients to handle handle, both because of
      the large amount of state that must be kept and because there may
      be multiple messages in the responses.  For these reasons reasons, it is
      clarified here that a valid reason for not pipelining queries is
      when they are all XFR queries i.e. clients sending multiple XFRs
      MAY choose not to pipeline those queries.  Clients that do not
      pipeline XFR queries, therefore, have no additional requirements
      to handle out-of-order or intermingled responses (as described
      later), since they will never receive them.


   *  Implementations SHOULD use [RFC7828] (The edns-tcp-keepalive EDNS0
      Option) to manage persistent connections. connections (which is more flexible
      than using just fixed timeouts).

   The following sections include detailed clarifications on the updates
   to XFR behavior implied in [RFC7766] and how the use of [RFC7828]
   applies specifically to XFR exchanges.  It  They also discusses discuss how IXFR
   and AXFR can reuse the same TCP connection.

   For completeness, we also mention here the recent specification of
   extended DNS error (EDE) codes [RFC8914].  For zone transfers, when
   returning REFUSED to a zone transfer request from an 'unauthorized'
   client (e.g., where the client is not listed in an ACL for zone
   transfers or does not sign the request with the correct a valid TSIG key), the
   extended DNS error code 18 (Prohibited) can also be sent.

7.1.  Update to RFC1995 for IXFR-over-TCP

   For clarity - an IXFR-over-TCP server compliant with this
   specification MUST be able to handle multiple concurrent IXoT
   requests on a single TCP connection (for the same and different
   zones) and SHOULD send the responses as soon as they are available,
   which might be out-of-order compared to the requests.

7.2.  Update to RFC5936 for AXFR-over-TCP

   For clarity - an AXFR-over-TCP server compliant with this
   specification MUST be able to handle multiple concurrent AXoT
   sessions on a single TCP connection (for the same and different
   zones).  The response streams for concurrent AXFRs MAY be
   intermingled and AXFR-over-TCP clients compliant with this
   specification which pipeline AXFR requests MUST be able to handle

7.3.  Updates to RFC1995 and RFC5936 for XFR-over-TCP

7.3.1.  Connection reuse

   As specified, XFR-over-TCP clients SHOULD re-use any existing open
   TCP connection when starting any new XFR request to the same primary,
   and for issuing SOA queries, instead of opening a new connection.
   The number of TCP connections between a secondary and primary SHOULD
   be minimized (also see Section 7.4).

   Valid reasons for not re-using existing connections might include:


   *  as already noted in [RFC7766], separate connections for different
      zones might be preferred for operational reasons.  In this case case,
      the number of concurrent connections for zone transfers SHOULD be
      limited to the total number of zones transferred between the
      client and server.


   *  reaching a configured limit for the number of outstanding queries
      or XFR requests allowed on a single TCP connection


   *  the message ID pool has already been exhausted on an open


   *  a large number of timeouts or slow responses have occurred on an
      open connection


   *  an edns-tcp-keepalive EDNS0 option with a timeout of 0 has been
      received from the server and the client is in the process of
      closing the connection (see Section 7.3.4)

   If no TCP connections are currently open, XFR clients MAY send SOA
   queries over UDP or a new TCP connection.

7.3.2.  AXFRs and IXFRs on the same connection

   Neither [RFC1995] nor [RFC5936] explicitly discuss the use of a
   single TCP connection for both IXFR and AXFR requests.  [RFC5936]
   does make the general statement:

   "Non-AXFR session traffic can also use an open TCP connection."

   We clarify here that implementations capable of both AXFR and IXFR
   and compliant with this specification SHOULD


   *  use the same TCP connection for both AXFR and IXFR requests to the
      same primary


   *  pipeline such requests (if they pipeline XFR requests in general)
      and MAY intermingle them


   *  send the response(s) for each request as soon as they are
      available i.e. responses MAY be sent intermingled

7.3.3.  XFR limits

   The server MAY limit

   For some current implementations adding all the number above functionality
   would introduce significant code complexity.  In such a case, there
   will need to be an assessment of the trade-off between that and the
   performance benefits of the above for XFR.

7.3.3.  XFR limits

   The server MAY limit the number of concurrent IXFRs, AXFRs or total
   XFR transfers in progress, or from a given secondary, to protect
   server resources.  Servers SHOULD return SERVFAIL if this limit is
   hit, since it is a transient error and a retry at a later time might
   succeed (there is no previous specification for this behavior).

7.3.4.  The edns-tcp-keepalive EDNS0 Option

   XFR clients that send the edns-tcp-keepalive EDNS0 option on every
   XFR request provide the server with maximum opportunity to update the
   edns-tcp-keepalive timeout.  The XFR server may use the frequency of
   recent XFRs to calculate an average update rate as input to the
   decision of what edns-tcp-keepalive timeout to use.  If the server
   does not support edns-tcp-keepalive edns-tcp-keepalive, the client MAY keep the
   connection open for a few seconds ([RFC7766] recommends that servers
   use timeouts of at least a few seconds).

   Whilst the specification for EDNS0 [RFC6891] does not specifically
   mention AXFRs, it does say
   "If an OPT record is present in a received request, compliant
   responders MUST include an OPT record in their respective

   We clarify here that if an OPT record is present in a received AXFR
   request, compliant responders MUST include an OPT record in each of
   the subsequent AXFR responses.  Note that this requirement, combined
   with the use of edns-tcp-keepalive, enables AXFR servers to signal
   the desire to close a connection (when existing transactions have
   competed) due to low resources by sending an edns-tcp-keepalive EDNS0
   option with a timeout of 0 on any AXFR response.  This does not
   signal that the AXFR is aborted, just that the server wishes to close
   the connection as soon as possible.

7.3.5.  Backwards compatibility

   Certain legacy behaviors were noted in [RFC5936], with provisions
   that implementations may want to offer options to fallback to legacy
   behavior when interoperating with servers known not to not support
   [RFC5936].  For purposes of interoperability, IXFR and AXFR
   implementations may want to continue offering such configuration
   options, as well as supporting some behaviors that were
   underspecified prior to this work (e.g., performing IXFR and AXFRs on
   separate connections).  However, XoT implementations connections should have no need
   to do so.

7.4.  Update to RFC7766

   [RFC7766] made general implementation recommendations with regard to
   TCP/TLS connection handling:

   "To mitigate the risk of unintentional server overload, DNS
   clients MUST take care to minimize the number of concurrent TCP
   connections made to any individual server. It is RECOMMENDED
   that for any given client/server interaction there SHOULD be no
   more than one connection for regular queries, one for zone
   transfers, and one for each protocol that is being used on top
   of TCP (for example, if the resolver was using TLS). However,
   it is noted that certain primary/ secondary configurations with
   many busy zones might need to use more than one TCP connection
   for zone transfers for operational reasons (for example, to
   support concurrent transfers of multiple zones)."
   Whilst this recommends a particular behavior for the clients using
   TCP, it does not relax the requirement for servers to handle 'mixed'
   traffic (regular queries and zone transfers) on any open TCP/TLS
   connection.  It also overlooks the potential that other transports
   might want to take the same approach with regard to using separate
   connections for different purposes.

   This specification for XoT updates the above general guidance in [RFC7766] to
   provide the same separation of connection purpose (regular queries
   and zone transfers) for all transports being used on top of TCP.

   Therefore, it is RECOMMENDED that for each protocol used on top of
   TCP in any given client/server interaction interaction, there SHOULD be no more
   than one connection for regular queries and one for zone transfers.

   As an illustration, it could be imagined that in future such an
   interaction could hypothetically include one or all of the following:


   *  one TCP connection for regular queries


   *  one TCP connection for zone transfers


   *  one TLS connection for regular queries


   *  one TLS connection for zone transfers


   *  one DoH connection for regular queries


   *  one DoH connection for zone transfers

   Section 7.3.1 has provided specific details of reasons where more
   than one connection for a given transport might be required for zone
   transfers from a particular client.

8.  XoT specification

8.1.  Connection establishment

   During connection establishment the Application-Layer Protocol
   Negotiation (ALPN) token "dot" [DoT-ALPN] MUST be selected in the TLS

8.2.  TLS versions

   For improved security all

   All implementations of this specification MUST use only TLS 1.3
   [RFC8446] or later.


8.3.  Port selection

   The connection for XoT SHOULD be established using port 853, as
   specified in [RFC7858], unless there is mutual agreement between the
   secondary and primary to use a port other than port 853 for XoT.
   There MAY be agreement to use different ports for AXoT and IXoT, or
   for different zones.


8.4.  High level XoT descriptions

   It is useful to note that in XoT XoT, it is the secondary that initiates
   the TLS connection to the primary for a XFR request, so that in terms
   of connectivity connectivity, the secondary is the TLS client and the primary the
   TLS server.

   The figure below provides an outline of the AXoT mechanism including

      Secondary                            Primary

          |              NOTIFY               |
          | <-------------------------------- |  UDP
          | --------------------------------> |
          |          NOTIFY Response          |
          |                                   |
          |                                   |
          |            SOA Request            |
          | --------------------------------> |  UDP (or part of
          | <-------------------------------- |  a TCP/TLS session)
          |           SOA Response            |
          |                                   |
          |                                   |
          |                                   |
          |            AXFR Request           | ---
          | --------------------------------> |   |
          | <-------------------------------- |   |
          |          AXFR Response 1          |   |
          |             (Zone data)           |   |
          |                                   |   |
          | <-------------------------------- |   | TLS
          |          AXFR Response 2          |   | Session
          |             (Zone data)           |   |
          |                                   |   |
          | <-------------------------------- |   |
          |          AXFR Response 3          |   |
          |             (Zone data)           | ---
          |                                   |

                 Figure 3. AXoT Mechanism

   The figure below provides an outline of the IXoT mechanism including

      Secondary                            Primary

          |              NOTIFY               |
          | <-------------------------------- |  UDP
          | --------------------------------> |
          |          NOTIFY Response          |
          |                                   |
          |                                   |
          |            SOA Request            |
          | --------------------------------> |  UDP (or part of
          | <-------------------------------- |  a TCP/TLS session)
          |           SOA Response            |
          |                                   |
          |                                   |
          |                                   |
          |            IXFR Request           | ---
          | --------------------------------> |    |
          | <-------------------------------- |    |
          |            IXFR Response          |    |
          |             (Zone data)           |    |
          |                                   |    | TLS
          |                                   |    | session
          |            IXFR Request           |    |
          | --------------------------------> |    |
          | <-------------------------------- |    |
          |            IXFR Response          |    |
          |             (Zone data)           | ---

                 Figure 4. IXoT Mechanism


8.5.  XoT transfers

   For a zone transfer between two end points to be considered protected
   with XoT all XFR requests and response for that zone MUST be sent
   over TLS connections where at a minimum:


   *  the client MUST authenticate the server by use of an
      authentication domain name using a Strict Privacy Profile Profile, as
      described in [RFC8310]


   *  the server MUST validate the client is authorized to request or
      proxy a zone transfer by using one or both of the following:

      * following

      -  Mutual TLS (mTLS)
      -  an IP based ACL (which can be either per-message or per-

      *  Mutual TLS (mTLS)

   The server MAY also require combined with a valid TSIG/SIG(0) signature, but this
   alone is not sufficient to authenticate signature on the client or server.
         XFR request

   If only one method is selected then mTLS is preferred because it
   provides strong cryptographic protection at both endpoints.

   Authentication mechanisms are discussed in full in Section 10 and the
   rationale for the above requirement in Section 11.  Transfer group
   policies are discussed in Section 12.


8.6.  XoT connections

   The details in Section 7 about, e.g., persistent connections and XFR
   message handling are fully applicable to XoT connections as well.
   However, any behavior specified here takes precedence for XoT.

   If no TLS connections are currently open, XoT clients MAY send SOA
   queries over UDP or TCP, or TLS.


8.7.  XoT vs ADoT

   As noted earlier, there is currently no specification for encryption
   of connections from recursive resolvers to authoritative servers.
   Some authoritatives are experimenting with ADoT and opportunistic
   encryption has also been raised as a possibility; it is therefore
   highly likely that use of encryption by authoritative servers will
   evolve in the coming years.

   This raises questions in the short term with regard to TLS connection
   and message handling for authoritative servers.  In particular, there
   is likely to be a class of authoritatives that wish to use XoT in the
   near future with a small number of configured secondaries secondaries, but that
   do not wish to support DoT for regular queries from recursive recursives in
   that same time frame.  These servers have to potentially cope with
   probing and direct queries from recursives and from test servers, and
   also potential attacks that might wish to make use of TLS to overload
   the server.

   [RFC5936] clearly states that non-AXFR session traffic can use an
   open TCP connection, however, this requirement needs to be re-
   evaluated when considering applying the same model to XoT.  Proposing
   that a server should also start responding to all queries received
   over TLS just because it has enabled XoT would be equivalent to
   defining a form of authoritative DoT.  This specification does not
   propose that, but it also does not prohibit servers from answering
   queries unrelated to XFR exchanges over TLS.  Rather, this
   specification simply outlines in later sections:


   *  how XoT implementations should utilize EDE codes in response to
      queries on TLS connections they are not willing to answer (see
      Section 8.7)

   o 8.8)

   *  the operational and policy options that a XoT server operator has
      with regard to managing TLS connections and messages (see
      Appendix A)


8.8.  Response RCODES

   XoT clients and servers MUST implement EDE codes.  If a XoT server
   receives non-XoT traffic it is not willing to answer on a TLS
   connection, it SHOULD respond with REFUSED and the extended DNS error
   code 21 - Not Supported [RFC8914].  XoT clients should not send any
   further queries of this type to the server for a reasonable period of
   time (for example, one hour) i.e., long enough that the server
   configuration or policy might be updated.


   Historically, servers have used the REFUSED RCODE for many
   situations, and so clients often had no detailed information on which
   to base an error or fallback path when queries were refused.  As a result
   result, the client behavior could vary significantly.  XoT servers
   that refuse queries must cater for the fact that client behavior
   might vary from continually retrying queries regardless of receiving
   REFUSED to every query, or at the other extreme clients may decide to
   stop using the server over any transport.  This might be because
   those clients are either non-XoT clients or do not implement EDE


8.9.  AXoT specifics


8.9.1.  Padding AXoT responses

   The goal of padding AXoT responses would be is two fold:


   *  to obfuscate the actual size of the transferred zone to minimize
      information leakage about the entire contents of the zone.


   *  to obfuscate the incremental changes to the zone between SOA
      updates to minimize information leakage about zone update activity
      and growth.

   Note that the re-use of XoT connections for transfers of multiple
   different zones slightly complicates any attempt to analyze the
   traffic size and timing to extract information.  Also, effective
   padding may require state to be kept as zones may grow and/or shrink
   over time.

   It is noted here that, depending on the padding policies eventually
   developed for XoT, the requirement to obfuscate the total zone size
   might require a server to create 'empty' AXoT responses.  That is,
   AXoT responses that contain no RR's apart from an OPT RR containing
   the EDNS(0) option for padding.  For example, without this capability
   the maximum size that a tiny zone could be padded to would
   theoretically be limited if there had to be a minimum of 1 RR per

   However, as with existing AXFR, the last AXoT response message sent
   MUST contain the same SOA that was in the first message of the AXoT
   response series in order to signal the conclusion of the zone

   [RFC5936] says:

   "Each AXFR response message SHOULD contain a sufficient number
   of RRs to reasonably amortize the per-message overhead, up to
   the largest number that will fit within a DNS message (taking
   the required content of the other sections into account, as
   described below)."

   'Empty' AXoT responses generated in order to meet a padding
   requirement will be exceptions to the above statement.  For
   flexibility, future proofing and in order to guarantee support for
   future padding policies, we state here that secondary implementations
   MUST be resilient to receiving padded AXoT responses, including
   'empty' AXoT responses that contain only an OPT RR containing the
   EDNS(0) option for padding.

   Recommendation of specific policies for padding AXoT responses are
   out of scope for this specification.  Detailed considerations of such
   policies and the trade-offs involved are expected to be the subject
   of future work.


8.10.  IXoT specifics


8.10.1.  Condensation of responses

   [RFC1995] says condensation of responses is optional and MAY be done.
   Whilst it does add complexity to generating responses responses, it can
   significantly reduce the size of responses.  However any such
   reduction might be offset by increased message size due to padding.
   This specification does not update the optionality of condensation
   for XoT responses.


8.10.2.  Fallback to AXFR

   Fallback to AXFR can happen, for example, if the server is not able
   to provide an IXFR for the requested SOA.  Implementations differ in
   how long they store zone deltas and how many may be stored at any one

   Just as with IXFR-over-TCP, after a failed IXFR a IXoT client SHOULD
   request the AXFR on the already open XoT connection.


8.10.3.  Padding of IXoT responses

   The goal of padding IXoT responses would be is to obfuscate the incremental
   changes to the zone between SOA updates to minimize information
   leakage about zone update activity and growth.  Both the size and
   timing of the IXoT responses could reveal information.

   IXFR responses can vary greatly in size greatly from the order of 100 bytes
   for one or two record updates, to tens of thousands of bytes for
   large dynamic DNSSEC signed zones.  The frequency of IXFR responses
   can also depend greatly on if and how the zone is DNSSEC signed.

   In order to guarantee support for future padding policies, we state
   here that secondary implementations MUST be resilient to receiving
   padded IXoT responses.

   Recommendation of specific policies for padding IXoT responses are
   out of scope for this specification.  Detailed considerations of such
   padding policies, the use of traffic obfuscation techniques (such as
   'dummy' traffic), and the trade-offs involved are expected to be the
   subject of future work.


8.11.  Name compression and maximum payload sizes

   It is noted here that name compression [RFC1035] can be used in XFR
   responses to reduce the size of the payload, however however, the maximum
   value of the offset that can be used in the name compression pointer
   structure is 16384.  For some DNS implementations this limits the
   size of an individual XFR response used in practice to something
   around the order of 16kB.  In principle, larger payload sizes can be
   supported for some responses with more sophisticated approaches
   (e.g., by pre-calculating the maximum offset required).

   Implementations may wish to offer options to disable name compression
   for XoT responses to enable larger payloads.  This might be
   particularly helpful when padding is used since minimizing the
   payload size is not necessarily a useful optimization in this case
   and disabling name compression will reduce the resources required to
   construct the payload.

9.  Multi-primary Configurations

   This model can provide flexibility and redundancy particularly for
   IXFR.  A secondary will receive one or more NOTIFY messages and can
   send an SOA to all of the configured primaries.  It can then choose
   to send an XFR request to the primary with the highest SOA (or based
   on other criteria, e.g., RTT).

   When using persistent connections connections, the secondary may have a XoT
   connection already open to one or more primaries.  Should a secondary
   preferentially request an XFR from a primary to which it already has
   an open XoT connection or the one with the highest SOA (assuming it
   doesn't have a connection open to it already)?

   Two extremes can be envisaged here.  The first one can be considered
   a 'preferred primary connection' model.  In this case case, the secondary
   continues to use one persistent connection to a single primary until
   it has reason not to.  Reasons not to might include the primary
   repeatedly closing the connection, long query/response RTTs on
   transfers or the SOA of the primary being an unacceptable lag behind
   the SOA of an alternative primary.

   The other extreme can be considered a 'parallel primary connection'
   model.  Here  Here, a secondary could keep multiple persistent connections
   open to all available primaries and only request XFRs from the
   primary with the highest serial number.  Since normally the number of
   secondaries and primaries in direct contact in a transfer group is
   reasonably low this might be feasible if latency is the most
   significant concern.

   Recommendation of a particular scheme is out of scope of this
   document, but implementations are encouraged to provide configuration
   options that allow operators to make choices about this behavior.

10.  Authentication mechanisms

   To provide context to the requirements in section Section 8.4, 8.5, this section
   provides a brief summary of some of the existing authentication and
   validation mechanisms (both transport independent and TLS specific)
   that are available when performing zone transfers.  Section 11 then
   discusses in more details specifically how a combination of TLS
   authentication, TSIG and IP based ACLs interact for XoT.

   We classify the mechanisms based on the following properties:


   *  'Data Origin Authentication' (DO): Authentication that the DNS
      message originated from the party with whom credentials were
      shared, and of the data integrity of the message contents (the
      originating party may or may not be party operating the far end of
      a TCP/TLS connection in a 'proxy' scenario).


   *  'Channel Confidentiality' (CC): Confidentiality of the
      communication channel between the client and server (i.e. the two
      end points of a TCP/TLS connection) from passive surveillance.


   *  'Channel Authentication' (CA): Authentication of the identity of
      party to whom a TCP/TLS connection is made (this might not be a
      direct connection between the primary and secondary in a proxy

10.1.  TSIG

   TSIG [RFC8945] provides a mechanism for two or more parties to use
   shared secret keys which can then be used to create a message digest
   to protect individual DNS messages.  This allows each party to
   authenticate that a request or response (and the data in it) came
   from the other party, even if it was transmitted over an unsecured
   channel or via a proxy.

   Properties: Data origin authentication

10.2.  SIG(0)

   SIG(0) [RFC2931] similarly also provides a mechanism to digitally sign a
   DNS message but uses public key authentication, where the public keys
   are stored in DNS as KEY RRs and a private key is stored at the

   Properties: Data origin authentication

10.3.  TLS
10.3.1.  Opportunistic TLS

   Opportunistic TLS for DoT is defined in [RFC8310] and can provide a
   defense against passive surveillance, providing on-the-wire
   confidentiality.  Essentially


   *  clients that know authentication information for a server SHOULD
      try to authenticate the server


   *  however they MAY fallback to using TLS without authentication and


   *  they MAY fallback to using cleartext if TLS is not available.

   As such such, it does not offer a defense against active attacks (e.g., an
   on path active attacker on the connection from client to server), and
   is not considered as useful for XoT.

   Properties: None guaranteed.

10.3.2.  Strict TLS

   Strict TLS for DoT [RFC8310] requires that a client is configured
   with an authentication domain name (and/or SPKI pinset) that MUST be
   used to authenticate the TLS handshake with the server.  If
   authentication of the server fails, the client will not proceed with
   the connection.  This provides a defense for the client against
   active surveillance, providing client-to-server authentication and
   end-to-end channel confidentiality.

   Properties: Channel confidentiality and channel authentication (of
   the server).

10.3.3.  Mutual TLS

   This is an extension to Strict TLS [RFC8310] which requires that a
   client is configured with an authentication domain name (and/or SPKI
   pinset) and a client certificate.  The client offers the certificate
   for authentication by the server and the client can authenticate the
   server the same way as in Strict TLS.  This provides a defense for
   both parties against active surveillance, providing bi-directional
   authentication and end-to-end channel confidentiality.

   Properties: Channel confidentiality and mutual channel

10.4.  IP Based ACL on the Primary

   Most DNS server implementations offer an option to configure an IP
   based Access Control List (ACL), which is often used in combination
   with TSIG based ACLs to restrict access to zone transfers on primary
   servers on a per query basis.

   This is also possible with XoT XoT, but it must be noted that, as with
   TCP, the implementation of such an ACL cannot be enforced on the
   primary until an XFR request is received on an established

   As discussed in Appendix A A, an IP based per connection ACL could also
   be implemented where only TLS connections from recognized secondaries
   are accepted.

   Properties: Channel authentication of the client.

10.5.  ZONEMD

   For completeness, we also describe Message Digest for DNS Zones
   (ZONEMD) [RFC8976] here.  The message digest is a mechanism that can
   be used to verify the content of a standalone zone.  It is designed
   to be independent of the transmission channel or mechanism, allowing
   a general consumer of a zone to do origin authentication of the
   entire zone contents.  Note that the current version of [RFC8976]

   "As specified herein, ZONEMD is impractical for large, dynamic zones
   due to the time and resources required for digest calculation.
   However, The ZONEMD record is extensible so that new digest schemes
   may be added in the future to support large, dynamic zones."

   It is complementary but orthogonal the above mechanisms; and can be
   used in conjunction with XoT XoT, but is not considered further here.

11.  XoT authentication

   It is noted that zone transfer scenarios can vary from a simple
   single primary/secondary relationship where both servers are under
   the control of a single operator to a complex hierarchical structure
   which includes proxies and multiple operators.  Each deployment
   scenario will require specific analysis to determine which
   combination of authentication methods are best suited to the
   deployment model in question.

   The XoT authentication requirement specified in Section 8.4 8.5 addresses
   the issue of ensuring that the transfers is are encrypted between the
   two endpoints directly involved in the current transfers.  The
   following table summarized summarizes the properties of a selection of the
   mechanisms discussed in Section 10.  The two letter acronyms for the
   properties are used below and (S) indicates the secondary and (P)
   indicates the primary.


    | Method         | DO(S) | CC(S) | CA(S) | DO(P) | CC(P) | CA(P) |
    | Strict TLS     |       |   Y   |   Y   |       |   Y   |       |
    | Mutual TLS     |       |   Y   |   Y   |       |   Y   |   Y   |
    | ACL on primary |       |       |       |       |       |   Y   |
    | TSIG           |   Y   |       |       |   Y   |       |       |

                                 Table 1

   Table 1: Properties of Authentication methods for XoT

   Based on this analysis it can be seen that:


   *  Using just mutual TLS can be considered a standalone solution
      since both end points are cryptographically authenticated


   *  Using secondary side Strict TLS with a primary side IP ACL and
      TSIG/SIG(0) combination provides sufficient protection to be

   Using just an IP based ACL on the primary also provides
      authentication of both end points

   o  Additional use of TSIG (or equally SIG(0)) can also provide data
      origin authentication which might could be desirable for deployments susceptible to attacks that include a proxy between the secondary and primary, but is not
      part of the XoT requirement because it does nothing can spoof
   TCP IP addresses, using TSIG/SIG(0) alone could be susceptible to guarantee
      channel confidentiality or authentication.
   attacks that were able to capture such messages should they be
   accidentally sent in clear text by any server with the key.

12.  Policies for Both AXoT and IXoT

   Whilst the protection of the zone contents in a transfer between two
   end points can be provided by the XoT protocol, the protection of all
   the transfers of a given zone requires operational administration and
   policy management.

   We call the entire group of servers involved in XFR for a particular
   set of zones (all the primaries and all the secondaries) the
   'transfer group'.

   Within any transfer group both AXFRs and IXFRs for a zone MUST all
   use the same policy, e.g., if AXFRs use AXoT then all IXFRs MUST use

   In order to assure the confidentiality of the zone information, the
   entire transfer group MUST have a consistent policy of requiring
   confidentiality. using XoT.  If
   any do not, this is a weak link for attackers to exploit.  For
   clarification, this means that within any transfer group both AXFRs
   and IXFRs for a zone MUST all use XoT.

   An individual zone transfer is not considered protected by XoT unless
   both the client and server are configured to use only XoT and the
   overall zone transfer is not considered protected until all members
   of the transfer group are configured to use only XoT with all other
   transfers servers (see Section 13).

   A XoT policy should MUST specify

   o  What kind of if

   *  mutual TLS is required (Strict or Mutual TLS)

   o  or if an used and/or

   *  a IP based ACL is required.

   o  (optionally) if and TSIG/SIG(0) combination is required used

   Since this may require configuration of a number of servers who may
   be under the control of different operators the desired consistency
   could be hard to enforce and audit in practice.

   Certain aspects of the Policies can be relatively easily tested
   independently, e.g., by requesting zone transfers without TSIG, from
   unauthorized IP addresses or over cleartext DNS.  Other aspects such
   as if a secondary will accept data without a TSIG digest or if
   secondaries are using Strict as opposed to Opportunistic TLS are more

   The mechanics of co-ordinating or enforcing such policies are out of
   the scope of this document but may be the subject of future
   operational guidance.

13.  Implementation Considerations

   Server implementations may want to also offer options that allow ACLs
   on a zone to specify that a specific client can use either XoT or
   TCP.  This would allow for flexibility while clients are migrating to

   Client implementations may similarly want to offer options to cater
   for the multi-primary case where the primaries are migrating to XoT.

14.  Operational Considerations

   If the options described in Section 13 are available, such
   configuration options MUST only be used in a 'migration mode', and
   therefore should be used with great care.

   It is noted that use of a TLS proxy in front of the primary server is
   a simple deployment solution that can enable server side XoT.

15.  IANA Considerations


16.  Implementation Status

   the status of known implementations of the protocol defined by this
   specification at the time of posting of this Internet-Draft, and is
   based on a proposal described in [RFC7942].

   A summary of current behavior and implementation status can be found
   here: XoT implementation status [1]

   Specific recent activity includes:

   1.  The 1.9.2 version of Unbound [2]
       Changelog) includes an option to perform AXoT (instead of AXFR-over-TCP). AXFR-

   2.  There are currently open pull requests against NSD to implement

       1.  Connection re-use by default during XFR-over-TCP [3]

       2.  Client side XoT [4] (https://github.com/NLnetLabs/nsd/pull/149)

   3.  Version 9.17.7 of BIND contained an initial implementation of
       DoT, implementation of XoT is planned for early 2021 [5]

   Both items 1. and 2.2. listed above require the client (secondary) to
   authenticate the server (primary) using a configured authentication
   domain name if XoT is used.

17.  Security Considerations

   This document specifies a security measure against a DNS risk: the
   risk that an attacker collects entire DNS zones through eavesdropping
   on clear text DNS zone transfers.

   This does not mitigate:


   *  the risk that some level of zone activity might be inferred by
      observing zone transfer sizes and timing on encrypted connections
      (even with padding applied), in combination with obtaining SOA
      records by directly querying authoritative servers.


   *  the risk that hidden primaries might be inferred or identified via
      observation of encrypted connections.


   *  the risk of zone contents being obtained via zone enumeration

   Security concerns of DoT are outlined in [RFC7858] and [RFC8310].

18.  Acknowledgements

   The authors thank Tony Finch, Benno Overeinder, Shumon Huque and Tim
   Wicinski and many other members of DPRIVE for review and discussions.

   The authors particularly thank Peter van Dijk, Ondrej Sury, Brian
   Dickson and several other open source DNS implementers for valuable
   discussion and clarification on the issue associated with pipelining
   XFR queries and handling out-of-order/intermingled responses.

19.  Contributors

   Significant contributions to the document were made by:

   Han Zhang
   San Francisco, CA
   United States

   Email: hzhang@salesforce.com

20.  Changelog



   *  Changes from IESG review

   *  Add section 8.1 on the requirement to use the DoT ALPN

   *  Modify the one of the options for validation of a client from just
      an IP ACL to a combination of IP ACL and TSIG/SIG(0)
      -  Update Abstract and Introduction with clear descriptions of how
         earlier specifications are updated

      -  Add reference on NSEC3 attacks

      -  Justify use of SHOULD in sections 7.3.2 and 7.3.3.

      -  Clarify the Appendix is non-normative

      -  Numerous typos and editorial improvements.

      -  Use xml2rfc v3 (some format changes occur as a result)


   *  Fix definition update missed in -10



   *  Address issued raised from IETF Last Call



   *  Address issued raised in the AD review



   *  RFC2845 -> (obsoleted by) RFC8945


   *  I-D.ietf-dnsop-dns-zone-digest -> RFC8976


   *  Minor editorial changes + email update



   *  Reference RFC7942 in the implementation status section


   *  Convert the URIs that will remain on publication to references


   *  Correct typos in acknowledgments



   *  Update text relating to pipelining and connection reuse after WGLC


   *  Add link to implementation status matrix

   *  Various typos


   *  Remove the open questions that received no comments.


   *  Add more detail to the implementation section



   *  Add Github repository


   *  Fix typos and references and improve layout.



   *  Remove propose to use ALPN


   *  Clarify updates to both RFC1995 and RFC5936 by adding specific
      sections on this


   *  Add a section on the threat model


   *  Convert all SVG diagrams to ASCII art


   *  Add discussions on concurrency limits


   *  Add discussions on Extended DNS error codes


   *  Re-work authentication requirements and discussion


   *  Add appendix discussion TLS connection management



   *  Significantly update descriptions for both AXoT and IXoT for
      message and connection handling taking into account previous
      specifications in more detail


   *  Add use of APLN and limitations on traffic on XoT connections.


   *  Add new discussions of padding for both AXoT and IXoT


   *  Add text on SIG(0)


   *  Update security considerations

   *  Move multi-primary considerations to earlier as they are related
      to connection handling



   *  Minor editorial updates


   *  Add requirement for TLS 1.3. or later



   *  Rename after adoption and reference update.


   *  Add placeholder for SIG(0) discussion


   *  Update section on ZONEMD



   *  Substantial re-work of the document.



   *  Editorial changes, updates to references.



   *  Initial commit


21.  References

21.1.  Normative References

              Wicinski, T., "DNS Privacy Considerations", draft-ietf-
              dprive-rfc7626-bis-08 (work in progress), October 2020.

   [DoT-ALPN] IANA, "TLS Application-Layer Protocol Negotiation (ALPN)
              Protocol IDs", 2021, <https://www.iana.org/assignments/

   [RFC1034]  Mockapetris, P., "Domain names - concepts and facilities",
              STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987,

   [RFC1035]  Mockapetris, P., "Domain names - implementation and
              specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
              November 1987, <https://www.rfc-editor.org/info/rfc1035>.

   [RFC1995]  Ohta, M., "Incremental Zone Transfer in DNS", RFC 1995,
              DOI 10.17487/RFC1995, August 1996, <https://www.rfc-

   [RFC1996]  Vixie, P., "A Mechanism for Prompt Notification of Zone
              Changes (DNS NOTIFY)", RFC 1996, DOI 10.17487/RFC1996,
              August 1996, <https://www.rfc-editor.org/info/rfc1996>.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997, <https://www.rfc-

   [RFC2931]  Eastlake 3rd, D., "DNS Request and Transaction Signatures
              ( SIG(0)s )", RFC 2931, DOI 10.17487/RFC2931, September
              2000, <https://www.rfc-editor.org/info/rfc2931>.

   [RFC5936]  Lewis, E. and A. Hoenes, Ed., "DNS Zone Transfer Protocol
              (AXFR)", RFC 5936, DOI 10.17487/RFC5936, June 2010,

   [RFC6973]  Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,
              Morris, J., Hansen, M., and R. Smith, "Privacy
              Considerations for Internet Protocols", RFC 6973,
              DOI 10.17487/RFC6973, July 2013, <https://www.rfc-

   [RFC7766]  Dickinson, J., Dickinson, S., Bellis, R., Mankin, A., and
              D. Wessels, "DNS Transport over TCP - Implementation
              Requirements", RFC 7766, DOI 10.17487/RFC7766, March 2016,

   [RFC7828]  Wouters, P., Abley, J., Dickinson, S., and R. Bellis, "The
              edns-tcp-keepalive EDNS0 Option", RFC 7828,
              DOI 10.17487/RFC7828, April 2016, <https://www.rfc-

   [RFC7858]  Hu, Z., Zhu, L., Heidemann, J., Mankin, A., Wessels, D.,
              and P. Hoffman, "Specification for DNS over Transport
              Layer Security (TLS)", RFC 7858, DOI 10.17487/RFC7858, May
              2016, <https://www.rfc-editor.org/info/rfc7858>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

   [RFC8310]  Dickinson, S., Gillmor, D., and T. Reddy, "Usage Profiles
              for DNS over TLS and DNS over DTLS", RFC 8310,
              DOI 10.17487/RFC8310, March 2018, <https://www.rfc-

   [RFC8446]  Rescorla, E., "The Transport Layer Security (TLS) Protocol
              Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,

   [RFC8499]  Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
              Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499,
              January 2019, <https://www.rfc-editor.org/info/rfc8499>.

   [RFC8914]  Kumari, W., Hunt, E., Arends, R., Hardaker, W., and D.
              Lawrence, "Extended DNS Errors", RFC 8914,
              DOI 10.17487/RFC8914, October 2020, <https://www.rfc-

   [RFC8945]  Dupont, F., Morris, S., Vixie, P., Eastlake 3rd, D.,
              Gudmundsson, O., and B. Wellington, "Secret Key
              Transaction Authentication for DNS (TSIG)", STD 93,
              RFC 8945, DOI 10.17487/RFC8945, November 2020,


22.  Informative References

   [BIND]     ISC, "BIND 9", 9.16.16", 2021, <https://www.isc.org/bind/>.

              Huitema, C., Mankin, A., and S. Dickinson, "Specification
              of DNS over Dedicated QUIC Connections", draft-ietf-
              dprive-dnsoquic-01 (work Work in progress), October 2020. Progress,
              Internet-Draft, draft-ietf-dprive-dnsoquic-02, 22 February
              2021, <https://tools.ietf.org/html/draft-ietf-dprive-

              Livingood, J., Mayrhofer, A., and B. Overeinder, "DNS
              Privacy Requirements for Exchanges between Recursive
              Resolvers and Authoritative Servers", draft-ietf-dprive-
              phase2-requirements-02 (work Work in progress), Progress,
              Internet-Draft, draft-ietf-dprive-phase2-requirements-02,
              2 November 2020. 2020, <https://tools.ietf.org/html/draft-ietf-

              Wicinski, T., "DNS Privacy Considerations", Work in
              Progress, Internet-Draft, draft-ietf-dprive-rfc7626-bis-
              09, 9 March 2021, <https://tools.ietf.org/html/draft-ietf-

              Rescorla, E., Oku, K., Sullivan, N., and C. A. Wood, "TLS
              Encrypted Client Hello", draft-ietf-tls-esni-09 (work Work in
              progress), December 2020. Progress, Internet-Draft,
              draft-ietf-tls-esni-10, 8 March 2021,

              Vcelak, J., Goldberg, S., Papadopoulos, D., Huque, S., and
              D. Lawrence, "NSEC5, DNSSEC Authenticated Denial of
              Existence", draft-vcelak-nsec5-08 (work Work in progress), Progress, Internet-Draft, draft-
              vcelak-nsec5-08, 29 December 2018.

              Chandramouli, R. and S. Rose, "Secure Domain Name System
              (DNS) Deployment Guide", 2013,
              NIST.SP.800-81-2.pdf>. 2018,

   [NSD]      NLnet Labs, "NSD", "NSD 4.3.6", 2021,

              Goldberf, S., Naor, N., Papadopoulos, D., Reyzin, L.,
              Vasant, S., and A. Ziv, "Stretching NSEC3 to the Limit:
              Efficient Zone Enumeration Attacks on NSEC3 Variants",

   [RFC1982]  Elz, R. and R. Bush, "Serial Number Arithmetic", RFC 1982,
              DOI 10.17487/RFC1982, August 1996, <https://www.rfc-

   [RFC2931]  Eastlake 3rd, D., "DNS Request and Transaction Signatures
              ( SIG(0)s )", RFC 2931, DOI 10.17487/RFC2931, September
              2000, <https://www.rfc-editor.org/info/rfc2931>.

   [RFC5155]  Laurie, B., Sisson, G., Arends, R., and D. Blacka, "DNS
              Security (DNSSEC) Hashed Authenticated Denial of
              Existence", RFC 5155, DOI 10.17487/RFC5155, March 2008,

   [RFC6891]  Damas, J., Graff, M., and P. Vixie, "Extension Mechanisms
              for DNS (EDNS(0))", STD 75, RFC 6891,
              DOI 10.17487/RFC6891, April 2013, <https://www.rfc-

   [RFC7942]  Sheffer, Y. and A. Farrel, "Improving Awareness of Running
              Code: The Implementation Status Section", BCP 205,
              RFC 7942, DOI 10.17487/RFC7942, July 2016,

   [RFC8484]  Hoffman, P. and P. McManus, "DNS Queries over HTTPS
              (DoH)", RFC 8484, DOI 10.17487/RFC8484, October 2018,

   [RFC8976]  Wessels, D., Barber, P., Weinberg, M., Kumari, W., and W.
              Hardaker, "Message Digest for DNS Zones", RFC 8976,
              DOI 10.17487/RFC8976, February 2021, <https://www.rfc-

21.3.  URIs

   [1] https://dnsprivacy.org/wiki/display/DP/

   [2] https://github.com/NLnetLabs/unbound/blob/release-1.9.2/doc/

   [3] https://github.com/NLnetLabs/nsd/pull/145

   [4] https://github.com/NLnetLabs/nsd/pull/149

   [5] https://gitlab.isc.org/isc-projects/bind9/-/issues/1784

              Chandramouli, R. and S. Rose, "Secure Domain Name System
              (DNS) Deployment Guide", 2013,

Appendix A.  XoT server connection handling

   This appendix provides a non-normative outline of the pros and cons
   of XoT server connection handling options.

   For completeness, it is noted that an earlier version of the
   specification suggested using a XoT specific ALPN to negotiate TLS
   connections that supported only a limited set of queries (SOA, XRFs)
   however XRFs),
   however, this did not gain support.  Reasons given included
   additional code complexity and proxies having no natural way to forward the ALPN
   signal to fact that XoT and ADoT are both
   DNS nameservers over TCP connections. wire format and so should share the "dot" ALPN.

A.1.  Only listen on TLS on a specific IP address

   Obviously a nameserver which hosts a zone and services queries for
   the zone on an IP address published in an NS record may wish to use a
   separate IP address for listening on TLS for XoT, only publishing
   that address to its secondaries.

   Pros: Probing of the public IP address will show no support for TLS.
   ACLs will prevent zone transfer on all transports on a per query

   Cons: Attackers passively observing traffic will still be able to
   observe TLS connections to the separate address.

A.2.  Client specific TLS acceptance

   Primaries that include IP based ACLs and/or mutual TLS in their
   authentication models have the option of only accepting TLS
   connections from authorized clients.  This could be implemented using
   a proxy or directly in DNS implementation.

   Pros: Connection management happens at setup time.  The maximum
   number of TLS connections a server will have to support can be easily
   assessed.  Once the connection is accepted the server might well be
   willing to answer any query on that connection since it is coming
   from a configured secondary and a specific response policy on the
   connection may not be needed (see below).

   Cons: Currently, none of the major open source DNS authoritative
   implementations support such an option.

A.3.  SNI based TLS acceptance

   Primaries could also choose to only accept TLS connections based on
   an SNI that was published only to their secondaries.

   Pros: Reduces the number of accepted connections.

   Cons: As above.  Also, this is not a recommended use of SNI.  For
   SNIs sent in the clear, this would still allow attackers passively
   observing traffic to potentially abuse this mechanism.  The use of
   Encrypted Client Hello [I-D.ietf-tls-esni] may be of use here.

A.4.  TLS  Transport specific response policies

   Some primaries might rely on TSIG/SIG(0) combined with per-query IP
   based ACLs to authenticate secondaries.  In this case the primary
   must accept all incoming TLS TLS/TCP connections and then apply a TLS
   transport-specific response policy on a per query basis.

   As an aside, whilst [RFC7766] makes a general purpose distinction to
   clients in
   the advice to clients about their usage of connections (between
   regular queries and zone transfers) this is not strict and nothing in
   the DNS protocol prevents using the same connection for both types of
   traffic.  Hence a server cannot know the intention of any client that
   connects to it, it can only inspect the messages it receives on such
   a connection and make per query per-query decisions about whether or not to
   answer those queries.

   Example policies a XoT server might implement are:


   *  strict: REFUSE all queries on TLS connections except SOA and
      authorized XFR requests


   *  moderate: REFUSE all queries on TLS connections until one is
      received that is signed by a recognized TSIG/SIG(0) key, then
      answer all queries on the connection after that


   *  complex: apply a heuristic to determine which queries on a TLS
      connections to REFUSE


   *  relaxed: answer all non-XoT queries on all TLS connections with
      the same policy applied to TCP queries

   Pros: Allows for flexible behavior by the server that could be
   changed over time.

   Cons: The server must handle the burden of accepting all TLS
   connections just to perform XFRs with a small number of secondaries.
   Client behavior to REFUSED response is not clearly defined (see
   Section 8.8).  Currently, none of the major open source DNS
   authoritative implementations offer an option for different response
   policies in different transports (but such functionality could
   potentially be implemented using a proxy).

A.4.1.  SNI based response policies

   In a similar fashion, XoT servers might use the presence of an SNI in
   the client hello to determine which response policy to initially
   apply to the TLS connections.

   Pros: This has to potential to allow a clean distinction between a
   XoT service and any future DoT based service for answering recursive

   Cons: As above.

Authors' Addresses

   Willem Toorop
   NLnet Labs
   Science Park 400
   Amsterdam  1098 XH
   The Netherlands

   Email: willem@nlnetlabs.nl

   Sara Dickinson
   Sinodun IT
   Magdalen Centre
   Oxford Science Park
   OX4 4GA
   United Kingdom

   Email: sara@sinodun.com
   Shivan Sahib
   Brave Software
   Vancouver, BC

   Email: shivankaulsahib@gmail.com

   Pallavi Aras
   Herndon, VA VA,
   United States

   Email: paras@salesforce.com

   Allison Mankin
   Herndon, VA VA,
   United States

   Email: allison.mankin@gmail.com