Skip to main content

Structured Data for Filtered DNS
draft-wing-dnsop-structured-dns-error-page-05

Document Type Replaced Internet-Draft (dnsop WG)
Expired & archived
Authors Dan Wing , Tirumaleswar Reddy.K , Neil Cook , Mohamed Boucadair
Last updated 2023-02-05 (Latest revision 2022-09-21)
Replaces draft-reddy-dnsop-error-page
Replaced by draft-ietf-dnsop-structured-dns-error
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-dnsop-structured-dns-error
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

DNS filtering is widely deployed for network security, but filtered DNS responses lack information for the end user to understand the reason for the filtering. Existing mechanisms to provide detail to end users cause harm especially if the blocked DNS response is to an HTTPS website. This document updates the EXTRA-TEXT field of Extended DNS Error to provide details on the DNS filtering. This information can be parsed by the client and displayed, logged, or used for other purposes. This document updates RFC 8914.

Authors

Dan Wing
Tirumaleswar Reddy.K
Neil Cook
Mohamed Boucadair

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)