Hi, I support publication of this document, regardless of the minor comments below.
Best regards, Matthijs Minor comments: 1. In section 1. Introduction: "The recursive resolver will first query the root nameservers." This assumes that there is no information related to <www.example.com/AAAA> in the resolver's cache. I suggest to make a small change to clarify: The recursive resolver will first look if it has the answer in the cache. If not, the recursive resolver will query the root name servers. 2. In section 2.2. Data in the DNS request: "www.verybad.example where verybad.example is the domain of an illegal or very offensive organization may create more problems for the user." I think this is a very bad example: We should not mention illegal here. We should emphasize on the legal reasons to protect privacy: The reason why pervasive monitoring is being done is to prevent people doing something illegal. However, it comes at the cost of our privacy, the freedom to conceal aspects of ourselves from others. Doing something offensive or shameful are good reasons to do so. 3. In section 2.5.2. In the authoritative name servers: "Also, it seems [aeris-dns] that there is a strong concentration of authoritative name servers among "popular" domains (such as the Alexa Top N list)." The [aeris-dns] reference seems misplaced. Also, it is in French. I do love the French language, but I don't speak nor read it, so I was wondering if there is an English version of the reference. 4. A lot of references seem to be volatile web pages, which is less than ideal. On 23-02-15 23:36, Warren Kumari wrote: > Dear DPRIVE WG, > > The authors of draft-ietf-dprive-problem-statement have indicated that > they believe that the document is ready, and have asked for Working > Group Last Call. > > The draft is available here: > https://datatracker.ietf.org/doc/draft-ietf-dprive-problem-statement/ > > This document was discussed at the DPRIVE meeting at IETF91 - some > notes here: > http://tools.ietf.org/wg/dprive/minutes?item=minutes-91-dprive.html > > The document has also been worked on in GitHub, here: > https://github.com/bortzmeyer/my-IETF-work > It has also received a fair bit of on-list discussion. > > Please review this draft to see if you think it is ready for > publication and send comments to the list, clearly stating your view. > Even if you previously expressed support for the document (e.g during > adoption), please respond to the WGLC showing that you still support > it. > > This WGLC ends Mon 09-Mar-2015. > > > In addition, to satisfy RFC 6702 ("Promoting Compliance with > Intellectual Property Rights (IPR)"): > Are you personally aware of any IPR that applies to > draft-ietf-dprive-problem-statement? If so, has this IPR been > disclosed in compliance with IETF IPR rules? (See RFCs 3979, 4879, > 3669, and 5378 for more details.) > > Thanks, > Warren Kumari > (as DPRIVE WG co-chair) > > _______________________________________________ dns-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/dns-privacy
