Dear DNSOP,

John and I have made a number of changes since the start of Working Group Last 
Call, thanks to your good feedback.  Here's a summary of the noteworthy changes 
since -06:

- The abstract emphasizes this document speak to operational requirements, in 
alignment with previously documented implementation requirements.

- Noted that this document updates RFC 1123

- Background section has been renamed to History of DNS over TCP

- Updated and clarified text on connection termination

- An earlier version mistakenly assumed that OpenBSD had the TCP "accept 
filter" feature

- EDNS(0) everywhere, instead of just EDNS

- Have added a few new or missing references to BIND, ECDSA, flag day 2020, and 
the KSK rollover list archives.

- Numerous updates to RFC references, including newly published RFCs and cases 
where some RFCs have new revisions published.  Also a number of RFC references 
were moved to the Normative section.

- Numerous other grammatical and typographical fixes

DW




> On Jun 8, 2021, at 4:10 PM, internet-dra...@ietf.org 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-10.txt
>       Pages           : 29
>       Date            : 2021-06-08
> 
> Abstract:
>   This document updates [RFC1123].  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 IETF datatracker status page for this draft is:
> https://secure-web.cisco.com/1Bt7uhovzfR-wXjPaS77JXhiNYAC3cbTLqKixLUer9be_snyAstM0vO7rbd-6tg1Af61WLfqMhmR6MVawQMyXSLUEvl0DDSRcPcGuyxR0DfQH5H1-kZ6dhoIrR03PqTyQi3sAPPE6MBNB866JcgyCfnKv7584QTS5Jn_PmyWhj4kZv-uLSWOYXn8yeY1J9dux9Tn-zR_72iBbLfxuN0DTm4R5rogWbVnF-09IUGVZim3fvZfuBJ6jxXNDkiM2XTUFlydxiUMOb96Sm7jng3ehyg/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-dnsop-dns-tcp-requirements%2F
> 
> There is also an htmlized version available at:
> https://secure-web.cisco.com/1kg3laQW73wmvxjmh3LHKPs8xTRL21Z8-8IsCg_LPFAwxpClKj5biuDi-KlWiOC4Fif8tl0V8GDQ42lYNX11vP-I18i5V8ywRYcweAMWL8D_8YyN6_WGgY2dWQvixDVv6AgA5A5mx_zx_LRNkTgrwokfiZjRkkDUFt7cvW6OizkTZE_MrZQbzUhAqaSzG_RH2qSx_Gjb2QYdcva1jZUArM1hJJQBk6zHznsMlqj1IqVShVtLC_o0wj79hWFYGDwzcuWBQgFHB_go1c8iIO0wFKA/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-dnsop-dns-tcp-requirements-10
> 
> A diff from the previous version is available at:
> https://secure-web.cisco.com/1n2z0gdPQvBFXazUbuwAkdVKLpzonHFKEqoPxbKuRCbnnqpluK3jeD0GmEy7EJinDCyKq6igwKrrmBzN77pynAgoRZRlaBSZh_DBffQQvgBPQp7oIjYftnLaBi98As0subHJYiUb2CyjeLCMHU3Pv8lQu3GlEKuFpvBZ9T5ZpIYwMyEVI6OdqZgGf7SIJWTOVBSH3tkSG53_yyD8bEsEIU7RHovBWnugdfFnQg5DQdqGBvoWiju0eLc14terdNJ-olPur3PGX8Pxe5uUS5H3nNQ/https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl2%3Ddraft-ietf-dnsop-dns-tcp-requirements-10
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://secure-web.cisco.com/1atzUJwMeKlqFcZqpVfe8Y-YVhu0kYAZKSSZnLcQDJARLtFm--_PO-Fkny_8v_OaS_gx_xyLPn6t0B4C4zy7aZTik0WB0it44p4Gt3-ONgGe3E4KPY__3excCeCkkuZDE3ri7i246Mv9OjdthuvztVOvZih-Up5uIfkpaZUE5d6bYXpvTt8nUFPVbEG4L5470k8zF7qeYNs658KGsV0mMcokaG9lkQBtr-7wsY3tVPuYqpXj3TdTvTnl7CeFurE0GWLC83zGaYkYY7rQM5-tVYQ/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fdnsop
> 

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

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to