This version of draft-ietf-dnsop-dns-tcp-requirements includes a number of 
changes made in response to GENART, SECDIR, ARTART, and TSVART reviews.  The 
notable changes are:

- added RFC 1536 as a document that this one updates

- new section 2.6. Reuse, Pipelining, and Out-of-Order Processing

- paragraph about tweaking parameters to deal with TIME_WAIT state is now much 
more conservative.  i.e. for experts only.

- new section 4.5. Defaults and Recommended Limits talks about recommended 
values for connection limits, timeouts, etc.

DW


> On Oct 13, 2021, at 4:21 PM, [email protected] wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the Domain Name System Operations WG of the IETF.
> 
>        Title           : DNS Transport over TCP - Operational Requirements
>        Authors         : John Kristoff
>                          Duane Wessels
>       Filename        : draft-ietf-dnsop-dns-tcp-requirements-13.txt
>       Pages           : 33
>       Date            : 2021-10-13
> 
> Abstract:
>   This document updates RFC 1123 and RFC 1536.  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.
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to