for a web to DNS proxy to decide to send a reply back, it would need to
consider it complete?
Or are you proposing that the http server would start streaming back the
payload as it received the (possibly out of order) replies?
Maybe instead should use WebSockets
------ Original Message ------
From: "John R Levine" <jo...@taugh.com>
To: "Marek Vavruša" <mvavr...@cloudflare.com>
Cc: "dnsop" <dnsop@ietf.org>
Sent: 12/07/2016 3:32:51 p.m.
Subject: Re: [DNSOP] Call for Adoption: draft-song-dns-wireformat-http
Don't you get this automatically if it's treated as a TCP DNS
connection? You stuff a bunch of requests down the pipe, and you get
back a bunch of responses.
See RFC 7766.
You get queueing for free, but not pipelining and out-of-order
responses, that has to be defined.
RFC 7766 says you should get pipelining and out-of-order responses on
TCP DNS. Take a look.
Even if the underlying DNS server that the proxy is using can't do it,
any newly written proxy should provide TCP DNS the way 7766 says it
should.
Regards,
John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
