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

[Paul Vixie <[e-mail]>]

On Sunday, December 20, 2015 10:03:58 PM Mark Delany wrote:
> > > And since shane-review states:
> > >     "This memo reviews the possible approaches..."
> > > 
> > > I take it to mean that shane-review could encompass implementations
> > > like dpriv that imply or propose out-of-order. If that is the case ...
> > 
> > no.
> 
> Then I'd like to suggest a "yes" for this document.
> 
> Pipeline stalling due to forced in-order queries/responses is quite a
> performance limitation and some implementations could readily provide
> out-of-order.

this document proposes that http be used to proxy dns. dns already allows out of order 
response processing, and tcp/53 initators already have to cope with out of order responses 
when they occur.

what, precisely, do you think that a document that only describes HTTP initiators which are 
also DNS (tcp/53 and udp/53) responders, has to say about the possibility of future out-of-
order HTTP processing?

to me, that's future work. meaning, 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.

i can't imagine what to say about it in today's world which allows pipelining in HTTP. please 
suggest text?

-- 
P Vixie