Re: [DNSOP] Should we try to work on DNS over HTTP in dnsop?

["Paul Hoffman" <[e-mail]>]

On 21 Dec 2015, at 5:13, Tony Finch wrote:

> Paul Vixie <[e-mail]> wrote:
>>
>> any HTTP initiator who wants out of order response processing will 
>> have
>> to negotiate for it (see mogul's 2001 RID draft) and will then have 
>> new
>> responsibilities for matching up the out of order HTTP responses with
>> then-outstanding HTTP requests.
>
> The current way to deal with out-of-order responses and head-of-line
> blocking in HTTP is HTTP/2.
>
> If you do DNS over HTTP then there has to be an exact correspondence
> between HTTP requests and responses and DNS requests and responses -
> anything else would be madness. This implies that DNS over HTTP/1 only
> supports in-order pipelined queries and responses in each connection; 
> to
> avoid head-of-line blocking you need either multiple connections or
> HTTP/2.

+1. If the authors of the document want to keep using HTTP 1.1 and thus 
lose the ability to do out-of-order responses, that's fine, but they 
have to be explicit about it.

As to the question in the Subject of this thread: I'm in favor of doing 
this in the DNSOP WG if the result will use modern IETF standards like 
HTTP/2 and TLS.

--Paul Hoffman