Re: [DNSOP] Should we try to work on DNS over HTTP in dnsop?

Given a conversation about DNS over DTLS, DNS over TCP, I think a body of
work exploring the simple mapping over HTTP/HTTPS makes perfect sense and
is more about the DNS than its about the underlying transport.

So I'm in support, adopt.

-George

On Thu, Dec 17, 2015 at 11:07 AM, Shane Kerr <shane@time-travellers.org>
wrote:

> Hello,
>
> I have updated the DNS over HTTP review document that I sent some days
> ago. Thanks to Jinmei for reading it.
>
> As I mentioned before, if there is interest then my co-authors and I
> are happy to try to get the working group to adopt the document. If
> there is not interest, then we are happy to go forward with an
> individual submission.
>
> If I don't hear any positive support over the next week or two then
> that is a pretty clear sign that the working group has little
> interest. :)
>
> Cheers,
>
> --
> Shane
>
> ---------- Forwarded message ----------
> From: "by way of Shane Kerr <shane@biigroup.cn>" <internet-drafts@ietf.org
> >
> To: Shane Kerr <shane@biigroup.cn>, Runxia Wan <rxwan@biigroup.cn>,
> Linjian Song <songlinjian@gmail.com>
> Cc:
> Date: Wed, 16 Dec 2015 16:58:41 -0800
> Subject: New Version Notification for
> draft-shane-review-dns-over-http-01.txt
>
> A new version of I-D, draft-shane-review-dns-over-http-01.txt
> has been successfully submitted by Shane Kerr and posted to the
> IETF repository.
>
> Name:           draft-shane-review-dns-over-http
> Revision:       01
> Title:          A review of implementation DNS over port 80/443
> Document date:  2015-12-16
> Group:          Individual Submission
> Pages:          7
> URL:
> https://www.ietf.org/internet-drafts/draft-shane-review-dns-over-http-01.txt
> Status:
> https://datatracker.ietf.org/doc/draft-shane-review-dns-over-http/
> Htmlized:
> https://tools.ietf.org/html/draft-shane-review-dns-over-http-01
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-shane-review-dns-over-http-01
>
> Abstract:
>    The default DNS transport uses UDP on port 53.  There are many
>    motivations why users or operators may prefer to avoid sending DNS
>    traffic in this way.  A common solution is to use port 80 or 443;
>    with plain TCP, TLS-encrypted TCP, or full HTTP(S).  This memo
>    reviews the possible approaches and delivers some useful information
>    for developers.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
>
>
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>