On Tue, Dec 20, 2016 at 10:16:58AM -0500, tjw ietf <tjw.i...@gmail.com> wrote a message of 79 lines which said:
> The draft is being present as "Informational", and the point here is to > document current working behavior in the DNS (for the past several years). ... > This starts a Call for Adoption for draft-vixie-dns-rpz Because there is a huge risk of misuse of this technique (for censorship), and because the current draft has no warning about these risks, I disagree with adoption by the WG. I know that adoption does not mean that the document is perfect, and that warnings about the risks could always be added during the WG work on the document but it is too important to rely on possible future changes. I don't want this document to be adopted before there are clear explanations of the risks and consequences. The work we do at the IETF has consequences (if not, we should shut down the working group and go fishing or gardening.) We need to consider these consequences, not to wash our hands saying "we just describe a technique, we are not responsible for its use". [Speaking of this responsability, the draft draft-irtf-hrpc-research is in Research Group Last Call in the HRPC research group. Reviewe welcome.] Regarding the "people are doing it anyway, better to publish a RFC than to have proprietary variants" argument, I think we should also consider the strategical risks for the DNS: lying resolvers train people to distrust the DNS, to move to alternative systems which have their own dangers and are not always well-designed. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
