<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-dnsop-structured-dns-error" target="https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-structured-dns-error-23">
   <front>
      <title>Structured Error Data for Filtered DNS</title>
      <author initials="D." surname="Wing" fullname="Dan Wing">
         <organization>Citrix Systems, Inc.</organization>
      </author>
      <author initials="T." surname="Reddy.K" fullname="Tirumaleswar Reddy.K">
         <organization>Nokia</organization>
      </author>
      <author initials="N." surname="Cook" fullname="Neil Cook">
         <organization>Open-Xchange</organization>
      </author>
      <author initials="M." surname="Boucadair" fullname="Mohamed Boucadair">
         <organization>Orange</organization>
      </author>
      <date month="June" day="24" year="2026" />
      <abstract>
	 <t>   DNS filtering is widely deployed for various reasons, including
   network security and policy enforcement.  However, filtered DNS
   responses lack structured information for end users to understand the
   reason for the filtering.  Existing mechanisms to provide explanatory
   details to end users cause harm especially if the blocked DNS
   response is for HTTPS resources.

   This document updates RFC 8914 by signaling client support for
   structuring the EXTRA-TEXT field of the Extended DNS Error to provide
   details on the DNS filtering.  Such details can be parsed by the
   client and displayed, logged, or used for other purposes.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-dnsop-structured-dns-error-23" />
   
</reference>
