I think we should take a closer look at draft-nottingham-public-resolver-errors before proceeding to publish this document. That draft fixes this draft's internationalization problem, but accepting both would result in duplicate mechanisms for conveying error text.
Fixing internationalization also reduces the need for detailed structured data, such as the "suberror" field. Without internationalization, we need fields and codepoints to represent various concepts that can be presented to the user by a localized client. With internationalization, we can ask the server operator to localize its own explanation, and avoid trying to write a universal machine-readable language for the extremely messy and sensitive business of policy enforcement. draft-nottingham-public-resolver-errors also solves several technical problems with this draft: 1. Overall efficiency. Repeating the entire explanation in EXTRA-TEXT with every blocking response is wasteful of bandwidth, especially if most clients ignore it. 2. MTU. The text we are discussing here might well need to include legal boilerplate that would exceed the MTU, limiting any potential use of this draft with connectionless transports. --Ben Schwartz ________________________________ From: Benno Overeinder <be...@nlnetlabs.nl> Sent: Saturday, October 26, 2024 4:10 PM To: DNSOP Working Group <dnsop@ietf.org> Cc: DNSOP Chairs <dnsop-cha...@ietf.org> Subject: [DNSOP] Working Group Last Call draft-ietf-dnsop-structured-dns-error Dear all, The draft-ietf-dnsop-structured-dns-error has seen several revisions and there has been considerable discussion on the mailing list and in the WG. At IETF 116, Gianpaolo Scalone (Vodafone) and Ralf Weber (Akamai) presented a proof of concept of this specification. The authors and the WG chairs believe the draft is ready for a Working Group Last Call. This initiates the Working Group Last Call (WGLC) for draft-ietf-dnsop-structured-dns-error, "Structured Error Data for Filtered DNS." The draft can be reviewed here: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-dnsop-structured-dns-error/__;!!Bt8RZUm9aw!8c_SfguaBa4m5E5hYYSWvIot1EKvRE_tHf9NZritJsp_RUuU9hJdgCE6U_tbihwV3JXY617iTXhDXg$ Intended Status: Proposed Standard Document Shepherd: Benno Please take the time to review this draft and share any relevant comments. For the WGLC to be effective, we need both positive support and constructive feedback; a simple lack of objection isn’t enough. If you believe this draft is ready for publication as an RFC, please state your support. Conversely, if you feel the document isn’t ready for publication, please provide your concerns and reasoning. This starts a two-week Working Group Last Call process, concluding on November 9, 2024. Thank you, Suzanne Tim Benno _______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
_______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
