On Jul 31, 2018, at 2:41 PM, Ted Lemon <mel...@fugue.com> wrote:
> The client may perform as many DNS operations as it wishes using the
> -newly created DSO Session. Operations SHOULD be pipelined (i.e., the
> -client doesn't need wait for a response before sending the next message).
> +newly created DSO Session. When the
> +client has multiple messages to send, it SHOULD NOT wait for each response
> before sending the next message.
> +This prevents TCP's delayed acknowledgement algorithm from forcing the
> +client into a slow lock-step.
> The server MUST act on messages in the order they are transmitted, but
> -responses to those messages SHOULD be sent out of order when appropriate.
> +when responses to those messages become available out of order, the server
> +SHOULD NOT delay sending available responses in order to respond in order.
As a result of the discussion on Benjamin's DISCUSS, I noticed that we don't
reference RFC7788 here, and this text mirrors section 3.3 of RFC778, so I added
a line after this that explicitly references that section.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
