All The Call for Adoption on draft-vixie-dns-rpz ended some time ago, and the results were a solid in favor of adoption. However, the legitmacy of the argument in opposition to adopting seems fairly significant about certain parts of the draft.
In discussing this with our AD, the opinion is that if this same opposition manifests in the IETF last call there would have reservations about advancing it. So if we consider this rough consensus for the purposes of adoption it means we believe we will be better off with an improved, working- group-owned document then this one. We’re going to go ahead and adopt it for DNSOP, with the intention of resolving the concerns people expressed by keeping the status as informational (not standards track) and making sure the cautions and limitations the WG discussed on the use of RPZ are clear in the document. thanks tim suzanne On Tue, Dec 20, 2016 at 10:16 AM, tjw ietf <[email protected]> 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 [email protected] https://www.ietf.org/mailman/listinfo/dnsop
