Info about the availability of a DNS service

[KenjiBaheux]

Similarly to the idea of having a standardized (possibly machine readable?) data policy description of a DNS service, it would be useful to know if a DNS service is meant for everyone or just for certain users, e.g. an ISP's subscribers when they are on the ISP's network.

Hypothetically, this could be useful to know when a user connect their laptop outside of their house in which case their usual DNS/DoH service may no longer work.

[gitnnelg]

I've been pondering the notion of means by which choosing a DNS service would be like negotiating a TLS connections crypto. The idea being that one aspect is what you prefer, what you'll accept, and what you'll reject - and - the other aspect is what you offer, what you can do, what you can't do.

If that could be expressed in a trusted manner (signed, checks for integrity, checks for revocation) then it could form the basis for selection of service.

This would help with the @home, @work, @coffeeshop scenarios by allowing devices to be administratively configured on what DNS service aspects they want in different scenarios.

[vcunat]

What the "trusted manner" might mean? I'm fairly sure that most policy assertions aren't provable... well, perhaps just "partially" in some more complicated ways, e.g. a trusted company auditing the policies and certifying them by some kind of signature.