Be ye not afraid -- I have reviewed this document as part of the operations directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the operation area directors. Document editors and WG chairs should treat these comments just like any other last call comments. Version reviewed: draft-ietf-dnsop-qname-minimisation-07 Summary: Ready with nits. OpsAD attention not needed. Please note: I strongly approve of this document, and have used it in many examples and presentations to explain the DNS privacy work that the IETF is undertaking. This may make me slightly biased :-). Because I like this document I had a hard time not over-editorializing. I've removed a bunch of bikeshedding comments, but feel free to take or ignore the readability comments below. Comments: O: This document describes one of the techniques that could be used to improve DNS privacy P: This document describes a technique to improve DNS privacy C: This is being published, so it seems like it moves from "we could do this" to "we are doing this" :-) Section 1: O: the fewer privacy problems you’ll get. P: the fewer privacy problems you’ll have. or P: the fewer privacy problems you have. C: Editorial. O: Under current practice, when a resolver receives P: Currently, when a resolver receives C: Readability. W -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf