Re: [Doh] Support requirements for Get and Post

Overall I think the draft does an OK job of describing the merits of
get/post (post is more efficient but is not http cache friendly, get is
needed for cases like push and is more http cache friendly). If folks think
its imperative to have that summary in one place in the document I'm happy
to make that change.

I would think most clients relying on http caches for performance would use
get, but if they have a DNS cache they are populating they would use post.
A server can choose not to implement one of these (and "method not allowed"
is the right response for that imo), but its limiting what clients can
achieve with it.

-P

On Sat, Mar 17, 2018 at 1:43 PM, Patrick McManus <pmcmanus@mozilla.com>
wrote:

> push #1: anticipate other needs of the client (as mentioned)
>
> push #2: its a different way to express additional records if that's a
> desirable thing (e.g. ttl granularity)
>
>
>
> On Sat, Mar 17, 2018 at 1:16 PM, Ólafur Guðmundsson <olafur@cloudflare.com
> > wrote:
>
>> What is the usage case to Server push of DNS answers ?
>>
>> Olafur
>>
>>
>> On Sat, Mar 17, 2018 at 12:40 PM, Daniel Stenberg <daniel@haxx.se> wrote:
>>
>>> On Sat, 17 Mar 2018, Ólafur Guðmundsson wrote:
>>>
>>> Post MUST be supported Get MAY be supported, when GET is not supported
>>>> the error code retuned should be 405 (HTTP RFC 7321, section 6.5.5).
>>>>
>>>
>>> You didn't say this, and it is a side-note about methods, but I still
>>> wanted to just mention that when imlementing support for HTTP/2 server push
>>> for DOH, you want the server to send that as a GET so that the query string
>>> tells the client about the request it also sends the response to...
>>>
>>> --
>>>
>>>  / daniel.haxx.se
>>
>>
>>
>> _______________________________________________
>> Doh mailing list
>> Doh@ietf.org
>> https://www.ietf.org/mailman/listinfo/doh
>>
>>
>