DNS colleagues, As I mentioned a while ago, we have been working on a document to describe the various ways of (ab)using HTTP to transmit DNS traffic. We have finished a -00 draft, and I would appreciate it if you had a look and see if it makes sense.
If the working group thinks that it makes sense for this forum, then I am happy to ask for adoption here. I am also fine to pursue this as an independent submission of there is no interest! :) Cheers, -- Shane
--- Begin Message ---A new version of I-D, draft-shane-review-dns-over-http-00.txt has been successfully submitted by Shane Kerr and posted to the IETF repository. Name: draft-shane-review-dns-over-http Revision: 00 Title: A review of implementation DNS over port 80/443 Document date: 2015-12-07 Group: Individual Submission Pages: 7 URL: https://www.ietf.org/internet-drafts/draft-shane-review-dns-over-http-00.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-00 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
--- End Message ---
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
