%% You should probably cite draft-ietf-dnsop-extended-error instead of this I-D. @techreport{wkumari-dnsop-extended-error-02, number = {draft-wkumari-dnsop-extended-error-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-wkumari-dnsop-extended-error/02/}, author = {Warren "Ace" Kumari and Evan Hunt and Roy Arends and Wes Hardaker and David C Lawrence}, title = {{Extended DNS Errors}}, pagetotal = 9, year = 2017, month = jul, day = 17, abstract = {This document defines an extensible method to return additional information about the cause of DNS errors. The primary use case is to extend SERVFAIL to provide additional information about the cause of DNS and DNSSEC failures. {[} Open question: The document currently defines a registry for errors. It has also been suggested that the option also carry human readable (text) messages, to allow the server admin to provide additional debugging information (e.g: "example.com pointed their NS at us. No idea why...", "We don't provide recursive DNS to 192.0.2.0. Please stop asking...", "Have you tried Acme Anvil and DNS? We do DNS right..." (!). Please let us know if you think text is needed, or if a 16bit FCFS registry is expressive enough. {]} {[} Open question: This document discusses extended *errors*, but it has been suggested that this could be used to also annotate *non- error* messages. The authors do not think that this is a good idea, but could be persuaded otherwise. {]}}, }