IETF Logo Mail Archive

[Doh] Support requirements for Get and Post

Ólafur Guðmundsson <olafur@cloudflare.com> Sat, 17 March 2018 12:27 UTC

Return-Path: <olafur@cloudflare.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 B10EF1277BB for <doh@ietfa.amsl.com>; Sat, 17 Mar 2018 05:27:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.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 lxr05w3gwXhZ for <doh@ietfa.amsl.com>; Sat, 17 Mar 2018 05:27:12 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 3AC4812778E for <doh@ietf.org>; Sat, 17 Mar 2018 05:27:12 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id a20so6220122wmd.1 for <doh@ietf.org>; Sat, 17 Mar 2018 05:27:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=4l/cO33kNUTZdgDLghDYx3jxc290lkgfgf/nzdRO0zE=; b=YURLUi/wuANmougYyMYVYoW6JkYFIvBqd3lLYnp1fvSQa90tZVPBGwx5jOIHAP1mGF Jg2XTWzGFgPVZiG7HbpgN6icUgKMYXqfSaSuMeX2Mmj6/XU9XcIgxVQogKSRuQwPcvQq +ThsNzo9l4M7MaoBvgbRkE9pXMtDk5/5gc2A8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=4l/cO33kNUTZdgDLghDYx3jxc290lkgfgf/nzdRO0zE=; b=Dv4htotOYvqFaoW/osG5bG83O7JWnapc8AeEmrLuS3k2N5q0fW7cMC7I95TqNsTZw0 ChHXZUKNencxjP+5N5AbztJeaikiuS8pT64OJtOTJCRljbh7laGkIFoLrn0ihFNADrFy BRlTsqMQa3GbE5mj4cRrZMVWijQyCnLcLdAmK/IGh4kgYOSfLJH13MN+AWvAw2KNCDwG yJW61cvv/ZVyPjExo1RpM61AGIoSW0qoNPXtgqHp/9UwOv7N0u0UwDfhXn5VQcvxCzwT KCYK4wMCcs0EhaCwSke2KlxWxdzkj81ynNQLPkf8OwaWdJL27pVOgMxr0CDzCe5cx3fK Rhlw==
X-Gm-Message-State: AElRT7HRe9ypTuk5fEwC8932QX5BO69ajoBu1wa5h4z/hs6ylYUjhDbo GzeZVQ8ze2zqmM8F22DHlEpKiEfl6Kr94kvyGuXKhJYq
X-Google-Smtp-Source: AG47ELtBq6ojL8ugUAlGdB/lhMs43OCzEsgbgesMFSkdQBsBokzKLRTdRYXFXD/xTeAxeYinttYRJhENspfA4LjbygA=
X-Received: by 10.28.5.145 with SMTP id 139mr3974137wmf.31.1521289630333; Sat, 17 Mar 2018 05:27:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.169.41 with HTTP; Sat, 17 Mar 2018 05:27:09 -0700 (PDT)
From: Ólafur Guðmundsson <olafur@cloudflare.com>
Date: Sat, 17 Mar 2018 12:27:09 +0000
Message-ID: <CAN6NTqzkUeF79y=heQ7PK7T3mQVDDk5WRtqB-npi6PuQ2s5bNQ@mail.gmail.com>
To: doh@ietf.org
Content-Type: multipart/alternative; boundary="001a114442f8046fe705679ad877"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/-2AtS1o32YkoZvzo6UXU0qDx3RY>
Subject: [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 12:27:14 -0000

Based on experience at the IETF101 Hackathon this issue came up.

dns-over-https-03 draft is silent on the topic if Get and Post are both
required or implementations can only support one of them.

I would like to see a section like this added to the document:

Implementation requirements

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

Reasoning: In many web servers POST is not logged but GET is. Thus from a
privacy point of view clients that do not want to have their queries logged
by servers stand a better chance by using POST.

Olafur

v2.23.0 | Report a Bug | By Email