I support adoption and have made some comments to the list already. I am not sure if we need to eventually publish the document as an RFC however. In particular I don't think we should try to get that doc perfect before going on to the real work of building protocols. It should be a running summary of the design rationale for the current proposal(s) we are working on, not a rationale for something we plan to build.
In my view, it is exactly the type of document the RFC series was originally intended to publish. But getting such docs through IESG last call can be rather wearing. On Fri, Oct 17, 2014 at 12:41 PM, Warren Kumari <[email protected]> wrote: > Dear DPRIVE WG, > > This starts a Call for Adoption for draft-bortzmeyer-dnsop-dns-privacy. > > [ Please note: I am assuming that Stephane and DNSOP are both OK with > us adopting this. It is referenced in our charter, and so might be > adopted by reference, but figured might as well appease the process > gods by doing this officially... Short CfA because it seems > obvious...] > > The draft is available here: > https://datatracker.ietf.org/doc/draft-bortzmeyer-dnsop-dns-privacy/ > > Please review this draft to see if you think it is suitable for > adoption by DPRIVE, > and comments to the list, clearly stating your view. > > Please also indicate if you are willing to contribute text, review, etc. > > This call for adoption ends Fri 24-Oct-2014. > > In addition, to satisfy RFC 6702 ("Promoting Compliance with > Intellectual Property Rights (IPR)"): > If you are personally aware of any IPR that applies to > draft-bortzmeyer-dnsop-dns-privacy, has this IPR been disclosed in > compliance with IETF IPR rules? (See RFCs 3979, 4879, 3669, and 5378 > for more details.) > > > > > -- > I don't think the execution is relevant when it was obviously a bad > idea in the first place. > This is like putting rabid weasels in your pants, and later expressing > regret at having chosen those particular rabid weasels and that pair > of pants. > ---maf > > _______________________________________________ > dns-privacy mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dns-privacy >
_______________________________________________ dns-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/dns-privacy
