DNS Transport over TCP - Operational Requirements
draft-ietf-dnsop-dns-tcp-requirements-15

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Suzanne Woolf <suzworldwide@gmail.com>, The IESG <iesg@ietf.org>, dnsop-chairs@ietf.org, dnsop@ietf.org, draft-ietf-dnsop-dns-tcp-requirements@ietf.org, rfc-editor@rfc-editor.org, suzworldwide@gmail.com, warren@kumari.net
Subject: Protocol Action: 'DNS Transport over TCP - Operational Requirements' to Best Current Practice (draft-ietf-dnsop-dns-tcp-requirements-15.txt)

The IESG has approved the following document:
- 'DNS Transport over TCP - Operational Requirements'
  (draft-ietf-dnsop-dns-tcp-requirements-15.txt) as Best Current Practice

This document is the product of the Domain Name System Operations Working
Group.

The IESG contact persons are Warren Kumari and Robert Wilton.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-tcp-requirements/

Ballot Text

Technical Summary

This document clarifies and strengthens an existing protocol feature specified in RFC 1123 from a SHOULD to a MUST. The bulk of it is a justification of the MUST for implementers, and corresponding advice to operators that they use the feature.  For many years it's been typical for DNS implementers to provide code for servicing DNS requests over TCP, but it has also been common for operators to turn it off; this document attempts to establish a best common practice for operators to only use DNS software that implements TCP support and to not disable the capability.


Working Group Summary

This document has been around in various forms for some time, and has been extensively reviewed in the WG by both protocol experts and DNS operators.  THe authors are experienced DNS protocol designers and operators as well, and responded to every issue raised in the WG discussion over time.


Document Quality

   This document clarifies and strengthens an existing protocol feature specified in RFC 1123 from a SHOULD to a MUST. The bulk of it is a justification of the MUST for implementers, and corresponding advice to operators that they use the feature.  For many years it's been typical for DNS implementers to provide code for servicing DNS requests over TCP, but it has also been common for operators to turn it off; this document attempts to establish a best common practice for operators to only use DNS software that implements TCP support and to not disable the capability.


Personnel
Suzanne Woolf is the Document Shepherd
Warren Kumari is RAD!!!!

RFC Editor Note