Reviewer: Vijay Gurbani Review result: Ready with Issues I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at <https://wiki.ietf.org/en/group/gen/GenArtFAQ>. Document: draft-ietf-dnsop-rfc8499bis-09 Reviewer: Vijay K. Gurbani Review Date: 2023-09-15 IETF LC End Date: 2023-09-05 IESG Telechat date: 2023-09-21 Summary: Ready with minor issues. (It was fun to read this I-D, lots of historical context. Thanks for putting it together!) Major issues: 0 Minor issues: 4 Nits/editorial comments: 2 Minor: - Global - I am surprised that the term "Round robin DNS" is not defined in this document. Is it worth defining? It is used quite a bit. - S2, in the definition of "Global DNS", second paragraph: In the last sentence of the paragraph, you use "octet" and "byte" interchangably. Perhaps stick to octets as we are talking about a collection of eight bits on the wire. - S5, in the definition of EDNS, the text says, "...to indicate the version number." Is there a EDNS(1) (or EDNS1)? I don't believe so, but it has been a while since I was caught up on latest work in DNS. AFAIK, it has always been called EDNS0, from back in rfc2671, RFC6891 continued with EDNS0 instead of EDNS1. Is it worth to provide historical perspective and say that till now, the version number has not changed since rfc2671? - S6, RDoT and ADoT: I do not believe that rfc7858 definies these terms. Is it worth referencing where these terms originated from? Nits - S2, right above "Private DNS:", please expand PTI on first use. - S3, in the definition of QNAME, s/this creates kind of confusion/this creates confusion/ ("kind of" is okay for colloquial use, but not in standards documents.) -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
