Last Call: <draft-ietf-dnsop-dns-tcp-requirements-12.txt> (DNS Transport over TCP - Operational Requirements) to Best Current Practice

The IESG <iesg-secretary@ietf.org> Fri, 20 August 2021 18:57 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-dnsop-dns-tcp-requirements-12.txt> (DNS Transport over TCP - Operational Requirements) to Best Current Practice
Auto-Submitted: auto-generated
Precedence: bulk
CC: Suzanne Woolf <suzworldwide@gmail.com>, dnsop-chairs@ietf.org, dnsop@ietf.org, draft-ietf-dnsop-dns-tcp-requirements@ietf.org, suzworldwide@gmail.com, warren@kumari.net
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <162948585631.8999.14396922765505792457@ietfa.amsl.com>
Date: Fri, 20 Aug 2021 11:57:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/bJ9Z3TOt1YlE2LrzxQbJAAX19_g>

The IESG has received a request from the Domain Name System Operations WG
(dnsop) to consider the following document: - 'DNS Transport over TCP -
Operational Requirements'
  <draft-ietf-dnsop-dns-tcp-requirements-12.txt> as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2021-09-03. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document updates RFC 1123.  This document strongly encourages
   the operational practice of permitting DNS messages to be carried
   over TCP on the Internet as a best current practice.  Such
   encouragement is aligned with the implementation requirements in RFC
   7766.  The use of TCP includes both DNS over unencrypted TCP, as well
   as over an encrypted TLS session.  The document also considers the
   consequences with this form of DNS communication and the potential
   operational issues that can arise when this best current practice is
   not upheld.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-tcp-requirements/



No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc8482: Providing Minimal-Sized Responses to DNS Queries That Have QTYPE=ANY (Proposed Standard - Internet Engineering Task Force (IETF))
    rfc8490: DNS Stateful Operations (Proposed Standard - Internet Engineering Task Force (IETF))
    rfc7873: Domain Name System (DNS) Cookies (Proposed Standard - Internet Engineering Task Force (IETF))
    rfc7828: The edns-tcp-keepalive EDNS0 Option (Proposed Standard - Internet Engineering Task Force (IETF))
    rfc7766: DNS Transport over TCP - Implementation Requirements (Proposed Standard - Internet Engineering Task Force (IETF))
    rfc7477: Child-to-Parent Synchronization in DNS (Proposed Standard - Internet Engineering Task Force (IETF))
    rfc6762: Multicast DNS (Proposed Standard - Internet Engineering Task Force (IETF))
    rfc5936: DNS Zone Transfer Protocol (AXFR) (Proposed Standard - Internet Engineering Task Force (IETF))
    rfc2181: Clarifications to the DNS Specification (Proposed Standard - Internet Engineering Task Force (IETF))
    rfc1996: A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY) (Proposed Standard - Internet Engineering Task Force (IETF))
    rfc1995: Incremental Zone Transfer in DNS (Proposed Standard - Internet Engineering Task Force (IETF))

Last Call: <draft-ietf-dnsop-dns-tcp-requirements… The IESG