On Tue, Dec 20, 2016 at 10:17 AM tjw ietf <tjw.i...@gmail.com> wrote:
> Why not just wade into this discussion... > > 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). > It is obvious that some feel this draft is a large mistake, but like > edns-client-subnet, more operators are deploying this than one is aware of. > > This starts a Call for Adoption for draft-vixie-dns-rpz > > The draft is available here: > https://datatracker.ietf.org/doc/draft-vixie-dns-rpz/ > > Please review this draft to see if you think it is suitable for adoption > by DNSOP, and comments to the list, clearly stating your view. > I believe that RPZ (and the DNS lies which it creates) is evil -- unfortunately we live in a world where this is a necessary evil. I wish we lived in a world where RPZ was not necessary, but, well, we don't, and so: I support adoption of this draft. I believe that it solves an important use case and that it needs to be publicly documented (it is already widely used / deployed and supported). I suspect that the changes to the document should primarily be to increase clarity / readability / fix nits, and that we should avoid the temptation to make substantive changes. I'm willing to contribute text, review, fold, spindle and mutilate, whatever will be useful to get this out the door. W > > Please also indicate if you are willing to contribute text, review, etc. > > With the holiday period upon us, we'll make this a three week call for > adoption. This call for adoption ends on 10 January 2017 > > Thanks, > tim wicinski > DNSOP co-chair > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop >
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
