Hi, Finally had a chance to read all of it. While I understand that it can be used to create enclaves, I think it can also be used in useful ways to increase the flexibility of the DNS system, e.g. for example possibly to avoid some of the problems we see from occasional name collision.
I would very much like to see it well documented. And if it is politically too difficult to standardize, informational is good enough. avri On 20-Dec-16 10:16, tjw ietf 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. > > 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 -- a...@ella.com is going out of use in the near future. Please switch to a...@acm.org --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
