Hi Ralf,
On 15 Nov 2026, at 03:49, Ralf Weber <[email protected]> wrote:
> The main threat to privacy are not resolvers be they public, at the ISP
> or in my home network (e.g as PI-hole). IMHO the main threat to privacy
> is the ad industry that wants to profit on your personal data and this
> would give them new very hard to defend against way to do this.
>
> The document sort of acknowledges that in the security and privacy
> considerations, however it talks about clients wich are browsers which
> most users have not control over in contrast to what is done with DNS
>
> So no, we should not do this.
Imagine a web server sends mappings between names and addresses to a client in
a form that a client is able to trust, as part of data exchanged over an HTTPS
bundle that already exists between them.
The web server already knows what DNS queries could be triggered by the objects
the sever sends the client. For example, they are implied by names embedded in
HTML sent from the server to the client. If the client looks up those names
using a DNS resolver, that provides opportunites for those queries to be
observed by new actors (DNS server operators).
The client of the web server can decide to block or ignore particular objects
or parts of objects received by the web server and not use (or look up) the
names that relate to things that were blocked. Whether or not DNS queries are
made by such a client does not change the information available to the web
server operator.
To me, doing something like what is described in this draft results in fewer
requests by a client being sent to the Internet and a reduced number of actors
that have the opportunity to observe them. Can you say more about why you think
there is a risk that adversaries ("the ad industry" in your reply, I assume)
gain new or increased opportunities to collect data from clients?
I think there are important pitfalls that need to be examined closely if we
imagine doing something like this, but the one you seem to be describing
doesn't obviously seem like one of them.
Joe
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]