I guess presuming that the back end will use TCP for DNS you could do
this, but I would imagine that's not always the case?
As an on-the-wire format goes there are worse ones, so if DNS over TCP
is used, which supports this, then I guess some mention in this proposal
could be useful to get people thinking about this. Even if something
else is used on the back end (e.g. http server is a DNS server with
cache, so may answer queries from cache or its own authoritative
database) it can still use this format.
Regards
Adrien
------ Original Message ------
From: "John Levine" <jo...@taugh.com>
To: "dnsop@ietf.org" <dnsop@ietf.org>
Cc: "adr...@qbik.com" <adr...@qbik.com>
Sent: 12/07/2016 3:06:24 p.m.
Subject: Re: [DNSOP] Call for Adoption: draft-song-dns-wireformat-http
So I suggest some thought should be given to reducing round-trips by
allowing for multiple DNS request payloads in a single HTTP request
message, and multiple DNS response payloads in an HTTP response
message.
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.
R's
John
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
