Hello, I support adoption of this draft. Adding more structured information will help clients provide more useful experiences when they encounter blocked/filtered error codes.
Best, Tommy > On Jan 22, 2023, at 12:36 PM, Tim Wicinski <tjw.i...@gmail.com> wrote: > > > All > > The chairs have received feedback for DNSOP to adopt this document, and I've > wrestled with this document. We have received feedback when presented > to adopt this work. We've also had some conversations with folks who > offer DNS services to enterprises they have had some customer interest. > I will say personally that I am sure I can find some individuals at my > current employer who would get very interested in this also. > So the best thing to do is - see what the Working Group says. > > If you work for someone who is interested in this, please let us know. > If you work for someone who has customers interested in this, please let us > know. > If you plan on implementing this (or not!), please let us know. > > If you feel less comfortable speaking publicly, please reach out to the > chairs. > > > This starts a Call for Adoption for draft-wing-dnsop-structured-dns-error-page > > The draft is available here: > https://datatracker.ietf.org/doc/draft-wing-dnsop-structured-dns-error-page/ > Please review this draft to see if you think it is suitable for adoption > by DNSOP, and send any 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: February 5th, 2023 > > Thanks, > tim wicinski > For DNSOP co-chairs > _______________________________________________ > 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
