Moin!
On 5 Aug 2019, at 16:26, Paul Hoffman wrote:
As I said earlier in the thread, it is not a "need".
Some clients who want the information will want to use HTTPS because
that's what they already do (such as applications with DoH clients);
there is no need to force them to also have DNS transport stacks just
to get the information.
Some clients who want the information will want to use DNS because
that's what they already do (such as stub resolvers); there is no need
to force them to also have HTTPS transport stacks just to get the
information.
This will not work as pointed out before. We either have to make
publication (server side) of both protocols mandatory (which I don’t
think is good idea as I don’t want to run a HTTPs server at my DNS
server) or we have to make the clients asking for both protocols
mandatory. Having both sides decide on what they do will not create
interoperable solutions.
So long
-Ralf
——-
Ralf Weber
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
