Re: [DNSOP] I-D Action: draft-ietf-dnsop-structured-dns-error-06.txt

I still don't understand why (other than marketing/advertising) this is
needed — the EDE "4.18. Extended DNS Error Code 17 - Filtered" ("The server
is unable to respond to the request because the domain is on a blocklist as
requested by the client. Functionally, this amounts to "you requested that
we filter domains like this one.") seems to cover it.

If browsers are willing to do anything with the EDE codes (like "ERROR:
Your DNS filtering provider says you shouldn't go here") what additional
**important** information needs to be communicated? And if browsers are not
willing to do anything with just EDE codes, it sure doesn't seem like they
would want to do that **and** follow an unauthenticated URL…

Anything more simply adds complexity and security risks, and entails
privacy concerns for the user too…

W

On Thu, Oct 19, 2023 at 4:05 AM, Vodafone Gianpaolo Angelo Scalone <
Gianpaolo-Angelo.Scalone=40vodafone.com@dmarc.ietf.org> wrote:

> Hi,
>
> I think that we have now 2 good potential compromises:
>
>    1. A browser interstitial page explaining that the following page is
>    generated by the service that blocked the actual page, with a button
>    indicating “proceed to the blocking page” and another “dismiss”
>    2. A graphical representation of the blocking page, rendered as image
>    with no clickable links, with a button indicating “proceed to the blocking
>    page” and another “dismiss”
>
>
>
> This would be understandable by customers and provide a good user
> experience and security.
>
> In addition we could start thinking about a reputation mechanism.
>
>
>
> Kind regards
>
>
>
> Gianpaolo
>
> C2 General
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>