Re: [Doh] Support requirements for Get and Post

Ben Schwartz <bemasc@google.com> Sat, 17 March 2018 17:22 UTC

Return-Path: <bemasc@google.com>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39AAD126C83 for <doh@ietfa.amsl.com>; Sat, 17 Mar 2018 10:22:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level:
X-Spam-Status: No, score=-2.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EueoqgcWbeGg for <doh@ietfa.amsl.com>; Sat, 17 Mar 2018 10:22:30 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75E2A12025C for <doh@ietf.org>; Sat, 17 Mar 2018 10:22:30 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id m83so16099677ioi.8 for <doh@ietf.org>; Sat, 17 Mar 2018 10:22:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=m80jnhY+FTbGYuapSSJFzVIGGTnF+qfF4wUcN4iJfj8=; b=HzfpiFZr19Vxl9Gdu6hvXHXhI6TLUJeww9fs9IOgBA8KDSwGzs9xS6g7SxpApE/2eR CvT1xP0YJbgo0Eg24eSosvp+u7VuNW00+l17b/YO6r5NKkJ4mN8p0tWTR+gfEM5iAB8f wKqmC36goj+TuT8Ob/iDpCFHi5h0O45W+LwlGtz42m4xXY/0Sr+yewrOPIdBb69ur/oK fAPr8dy8pRp0XaBaXMyKe2pfgb6HdfUIyRL80Mjh3I2kvdhJbl/eQ3WHOG6H4bAiHxhp Xoe5IWvhjmkn6XBEBPmDg9+oxfzr4f6KawbNGK/9ipGrc8RWQKMDjA1tFwFxmA2keKPJ HOSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=m80jnhY+FTbGYuapSSJFzVIGGTnF+qfF4wUcN4iJfj8=; b=jKgOo1PDTVSvLZnibViie0XuWe8kDpRpuIYFuzjOFHDpP91hhlnVPA06tgebG54CSQ cVnMQVnPFvtFrAkzNLcLhPncW+4CpExdpH9fpDVXEHFTGryL3CeabKql0kcPbPwgKzfT G9Dz6/RpknC6ylBOaLVB8ik8LwsgluzUo344z6YsH5fcGFXBHheAwFRsp6nlL0EnyZVU tx7KZPVwOzOfQPR5jSeigTUOxsMMAjBmmEe/36WqsKPpAlh2WH2HK0/K5xkhzPjmUjVF d7/WEzVGRCCafdf+bpNHpuphQBK3cf2pFObd4lAOgzcfyWjWFQbRIUKuSfSL/ceMokw+ th3w==
X-Gm-Message-State: AElRT7HT+lmwJYVKB16HXU4CW069R9QLa/ufpRZUixXaUBOjZib//HRL oRxHARyDYUVEVQjmW/totz06yOPHMnDtHaCGSSW2ZA==
X-Google-Smtp-Source: AG47ELs9Cunp/fPVLl0BYIA9jcVrq5u4wD8drcuALO5jvqoG6gccqHbo+wTXOejzjBuQyaXwCA8xSWZ/MCGXZ1bJAkQ=
X-Received: by 10.107.29.205 with SMTP id d196mr6445806iod.18.1521307349091; Sat, 17 Mar 2018 10:22:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.168.210 with HTTP; Sat, 17 Mar 2018 10:22:28 -0700 (PDT)
In-Reply-To: <CAOdDvNqGvPRH3SzP_tkHVZHr-geacqDBa+QfoqXGVxFWW2qr2A@mail.gmail.com>
References: <CAN6NTqzkUeF79y=heQ7PK7T3mQVDDk5WRtqB-npi6PuQ2s5bNQ@mail.gmail.com> <alpine.DEB.2.20.1803171337530.1331@tvnag.unkk.fr> <CAN6NTqykeU1gT0TaDKahBPeF-a8gwYG7gsAEK_aSE0fNP-AsfQ@mail.gmail.com> <CAOdDvNq7e5YGtUap6tHu34zX5q1PvmQjAh+fc0m=xcRDUrmKhA@mail.gmail.com> <CAOdDvNqGvPRH3SzP_tkHVZHr-geacqDBa+QfoqXGVxFWW2qr2A@mail.gmail.com>
From: Ben Schwartz <bemasc@google.com>
Date: Sat, 17 Mar 2018 13:22:28 -0400
Message-ID: <CAHbrMsAkU+KKwCFpyLD40aPZLEVtRj=aEZsaC+=Y2yYwKCiEyA@mail.gmail.com>
To: Patrick McManus <pmcmanus@mozilla.com>
Cc: =?UTF-8?B?w5NsYWZ1ciBHdcOwbXVuZHNzb24=?= <olafur@cloudflare.com>, doh@ietf.org, Daniel Stenberg <daniel@haxx.se>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="001a1140a7442f022e05679ef833"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/7t7gPbgd6RC-RHeOgwgsX03HdkY>
Subject: Re: [Doh] Support requirements for Get and Post
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Mar 2018 17:22:33 -0000

On Sat, Mar 17, 2018 at 9:47 AM, Patrick McManus <pmcmanus@mozilla.com>;
wrote:

> 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.
>

SHOULD clients handle a "method not allowed" by retrying with the other
method?


>
> -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
>>>
>>>
>>
>
> _______________________________________________
> Doh mailing list
> Doh@ietf.org
> https://www.ietf.org/mailman/listinfo/doh
>
>