Document: draft-ietf-dnsop-3901bis Title: DNS IPv6 Transport Operational Guidelines Reviewer: Martin Duke Review result: Ready with Nits
This document has been reviewed as part of the transport area review team's ongoing effort to review key IETF documents. These comments were written primarily for the transport area directors, but are copied to the document's authors and WG to allow them to address any issues raised and also to the IETF discussion list for information. When done at the time of IETF Last Call, the authors should consider this review as part of the last-call comments they receive. Please always CC [email protected] if you reply to or forward this review. The main transport-related content here relates to MTU and fragmentation. There's nothing fundamentally wrong here, but things are bit oddly phrased. 1) Sec 3.2 says that a DNS server MAY choose to explicitly use MTU path discovery. The example suggests setting the MTU to the minimum MTU. But this is the only way, correct? With anything larger, one must use discovery, no? It's not an example, it's the only case. 2) The end of Sec 3.2 provides DoT and DoQ as examples of alternative transports, and implies that they have other means of fragmentation avoidance. In the case of QUIC, this is just PLPMTUD!! Just as with TCP, this is not something the DNS layer needs to worry about if the transport is competently implemented. But the level of service there is exactly the same as TCP modulo some security properties -- there is no additional magic in these protocols. _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
