Re: [dnsoverhttp] Survey of DNS over HTTP

[Stephen Farrell <[e-mail]>]

Hi Shane,

I have two related questions for which I didn't get answers
from your fine document.

1) Are folks using IP addresses or DNS names in the URLs they
are de-referencing when using HTTP(S)?

2) Are there any functional reasons to ever specifically want
DNS/HTTP, as opposed to DNS/HTTP/TLS? By functional I mean to
exclude the obvious simplicity, performance and WebPKI-trust
reasons why HTTP is "easier" than HTTP/TLS.

BTW, the reason these are related is that if folks are using
IP addresses for the requests, then our current inability to
get WebPKI certs for IP addresses may be a functional motivation
for preserving the ability to do DNS/HTTP in clear.

From my POV it'd be a bit sad if we need to define yet another
open-kimono/insecure way to do DNS, so I'd be happier were it
safe to assume that the client can use a DNS name in the URL
and can somehow figure out how to resolve that name to an IP
address. But I don't know if that's a reasonable assumption.

Cheers,
S.


On 14/09/16 14:04, Shane Kerr wrote:
> Hello,
> 
> I thought that people interested in this topic might find a draft
> written by my colleagues and myself useful. It is a survey of various
> DNS over HTTP techniques:
> 
> https://datatracker.ietf.org/doc/draft-shane-review-dns-over-http/
> 
> It needs to be updated, to reference Paul Hoffman's recent update to
> his DNS JSON draft if nothing else:
> 
> https://tools.ietf.org/html/draft-hoffman-dns-in-json/
> 
> Cheers,
> 
> --
> Shane
> 
> 
> 
> _______________________________________________
> dnsoverhttp mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dnsoverhttp
>