Tim Wicinski <[email protected]> wrote: > > This starts a Working Group Last Call for draft-ietf-dnsop-5966bis
I have re-read the draft and it looks good to me. A couple of suggestions for section 7: For the avoidance of future doubt, this requirement is clarified. Authoritative servers and recursive resolvers are RECOMMENDED to support the sending of responses in parallel and/or out-of-order, regardless of the transport protocol in use. I suggest deleting "in parallel and/or" since sending parallel responses on a TCP query doesn't make sense, and even UDP responses have to be serialized at some level. Perhaps change the clause to "preparing responses in parallel and sending them out-of-order". Since pipelined responses can arrive out-of-order, clients MUST match responses to outstanding queries using the ID field and port number. I think this should be: Since pipelined responses can arrive out-of-order, clients MUST match responses to outstanding queries using the DNS query ID, the contents of the question section (QNAME, QCLASS, QTYPE), and the transport tuple (protocol, source and destination addresses, source and destination ports). Tony. -- f.anthony.n.finch <[email protected]> http://dotat.at/ Viking, North Utsire: Easterly 4 or 5, increasing 6 at times. Slight or moderate, but rough in southwest Viking. Showers later. Good, occasionally poor later. _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
