Re: [dns-privacy] Working Group Last Call for draft-ietf-dprive-rfc7626-bis

["Hollenbeck, Scott" <[e-mail]>]

> -----Original Message-----
> From: dns-privacy <[e-mail]> On Behalf Of Vladimír
> Cunát
> Sent: Monday, August 19, 2019 8:58 AM
> To: [e-mail]
> Subject: [EXTERNAL] Re: [dns-privacy] Working Group Last Call for draft-ietf-
> dprive-rfc7626-bis
>
> Hello,
>
> I now read through the whole document, and I see one thing that might be a
> little bit confusing - the beginning of page three reads like QNAME
> minimization is not possible or at least never done, and contrary to
> rfc7626 itself it isn't even mentioned in the whole document.  I would
> suggest to at least reduce the strength of the wording ("always"), and/or
> mention rfc7816.  I don't have much data at hand, but I believe that some
> reduction of QNAMEs isn't as exotic as it used to be.

Agreed, and I'll suggest a sentence (enclosed by **) for the end of the third paragraph of the Introduction:

"It is important, when analyzing the privacy issues, to remember that the question asked to all these name servers is always the original question, not a derived question.  The question sent to the root name servers is "What are the AAAA records for www.example.com?", not "What are the name servers of .com?".  By repeating the full question, instead of just the relevant part of the question to the next in line, the DNS provides more information than necessary to the name server. **In this simplified description, recursive resolvers do not implement QNAME minimization as described in RFC 7816 [RFC7816], which will only send the relevant part of the question to the upstream name server.**"

It may be more desirable to reference 7816bis, but that would add an Internet-Draft reference dependency that folks might not want to add.

Scott