The revised draft
https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-structured-dns-error
addresses
comments from Mark.

-Tiru

On Thu, 26 Feb 2026 at 12:11, <[email protected]> wrote:

> Internet-Draft draft-ietf-dnsop-structured-dns-error-17.txt is now
> available.
> It is a work item of the Domain Name System Operations (DNSOP) WG of the
> IETF.
>
>    Title:   Structured Error Data for Filtered DNS
>    Authors: Dan Wing
>             Tirumaleswar Reddy
>             Neil Cook
>             Mohamed Boucadair
>    Name:    draft-ietf-dnsop-structured-dns-error-17.txt
>    Pages:   26
>    Dates:   2026-02-25
>
> Abstract:
>
>    DNS filtering is widely deployed for various reasons, including
>    network security.  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.
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-structured-dns-error/
>
> There is also an HTML version available at:
>
> https://www.ietf.org/archive/id/draft-ietf-dnsop-structured-dns-error-17.html
>
> A diff from the previous version is available at:
>
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-dnsop-structured-dns-error-17
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> DNSOP mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to