Re: [dnsoverhttp] Survey of DNS over HTTP

Hi Shane,

Thanks for the doc.  One approach to add is using dns URIs as the target of
HTTP methods, returning the dns data using the relevant mime type.  In that
approach, you send the message over HTTP(S) with something like

GET  dns:[//authority/]domain[?CLASS=class;TYPE=type]

(See RFC 4501 for the full set of permitted syntax for DNS URIs)

and return either application/dns or text/dns records for the result (See
RFC 4027 for the specification of the MIME types).

This treats the server to whom you are speaking as it if were an HTTP
intermediary acting like a proxy, under a loose reading of RFC 7230's
description:

   A "proxy" is a message-forwarding agent that is selected by the
   client, usually via local configuration rules, to receive requests
   for some type(s) of absolute URI and attempt to satisfy those
   requests via translation through the HTTP interface.

In this case the type of absolute URI is a DNS URI.

regards,

Ted

On Wed, Sep 14, 2016 at 6:04 AM, Shane Kerr <shane@time-travellers.org>
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
> dnsoverhttp@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsoverhttp
>
>