On Mon, Nov 04, 2024 at 01:48:57PM +0000, Gianpaolo Angelo Scalone, Vodafone <[email protected]> wrote a message of 203 lines which said:
> Given there are several reasons for a domain to be blocked > (mandatory reasons in case of court orders, CSAM filtering, customer > requested reasons in case a customer opt in to a protective DNS > service), today the customer is facing a disorienting user > experience, as either if the response is NXDOMAIN or a forged > response he is not aware of the real blocking reason and cannot I support the draft but I think your argument is not a correct one. RFC 8914 already allows the user to know if it was censored and, if so, if it was by request of the user, of the resolver operator, or a third party. What draft-ietf-dnsop-structured-dns-error add is the ability to have more details. _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
