>Please review this draft to see if you think it is suitable for adoption >by DNSOP, and comments to the list, clearly stating your view.
Yes, we should adopt it. It needs some work, but what draft doesn't. >Please also indicate if you are willing to contribute text, review, etc. Yes. My main suggestion is to lose the Proxy-DNS-Transport header and always have the request and response in TCP format. If the server doing the http-to-DNS proxy wants to microoptimize and try the query as UDP and see if it works, that's fine, but I'm guessing that the proxy will usually be close to the cache it's using so the penalty for TCP will be low. I'd also want to change some of the motivation text. To me, by far the most likely scenario here is javascript applications that want to do DNS queries, e.g. for SRV, but can't because javascript doesn't let you do that. Now the server that provided the javascript blob can also be the DNS proxy. The javascript can't query random other DNS proxies due to cross-site scripting rules. R's, John _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
