Hello, it is a good read.
I would only add reference to https://datatracker.ietf.org/doc/draft-ietf-intarea-frag-fragile/ + DNS Flag Day 2020, which is going to effectivelly kill UDP fragmentation in DNS and thus require TCP for perfect operation. Maybe we could add something along these lines around end of section-2.4: Problems caused by IP fragmentation are described at length in document https://tools.ietf.org/html/draft-ietf-intarea-frag-fragile . One of possible approaches to workaround this problem is lowering EDNS buffer size to values which do not cause IP fragmentation. In fact, such coordinated change is planned for year 2020 [http://dnsflagday.net/2020/]. Petr Špaček @ CZ.NIC On 25. 06. 19 17:10, John Kristoff wrote: > Friends, > > Duane and I pushed out a recent update to this draft. There are at > least a couple of small TODO items we have to address (search text > for TODO) before it can be published, but I think we've exhausted > largely what we set out to do for this document and would like to see > this wrapped up. > > If you could give it perusal and provide and alert us to anything > needing attention that would be lovely. Thank you, > > <https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-tcp-requirements/> > > This document encourages the practice of permitting DNS messages to > be carried over TCP on the Internet. It also considers the > consequences with this form of DNS communication and the potential > operational issues that can arise when this best common practice is > not upheld. > > John > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
