IETF Logo Mail Archive

Re: [Doh] A question on the mix of DNS and HTTP semantics

Stephane Bortzmeyer <bortzmeyer@nic.fr> Sun, 18 March 2018 16:56 UTC

Return-Path: <bortzmeyer@nic.fr>
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 87429128C0A for <doh@ietfa.amsl.com>; Sun, 18 Mar 2018 09:56:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 aWagvTq57mNe for <doh@ietfa.amsl.com>; Sun, 18 Mar 2018 09:56:17 -0700 (PDT)
Received: from ayla.bortzmeyer.org (ayla.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fe27:3d3f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDBBA1289B0 for <doh@ietf.org>; Sun, 18 Mar 2018 09:56:16 -0700 (PDT)
Received: by ayla.bortzmeyer.org (Postfix, from userid 10) id 4B960A05CF; Sun, 18 Mar 2018 17:56:15 +0100 (CET)
Received: by godin (Postfix, from userid 1000) id 0457CEC0B87; Sun, 18 Mar 2018 17:53:57 +0100 (CET)
Date: Sun, 18 Mar 2018 16:53:57 +0000
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Tony Finch <dot@dotat.at>
Cc: Ted Hardie <ted.ietf@gmail.com>, doh@ietf.org
Message-ID: <20180318165356.GA7198@laperouse.bortzmeyer.org>
References: <CA+9kkMB7awRfW9jUmY9Q-1p+w3VLtpG5DxhF3s7Q58nEMZeX3w@mail.gmail.com> <alpine.DEB.2.11.1803181007050.16965@grey.csi.cam.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.11.1803181007050.16965@grey.csi.cam.ac.uk>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 16.04 (xenial)
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/lUiuPzjF9xXtPOu8RAYH1NhrH0M>
Subject: Re: [Doh] A question on the mix of DNS and HTTP semantics
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: Sun, 18 Mar 2018 16:56:18 -0000

On Sun, Mar 18, 2018 at 10:11:41AM +0000,
 Tony Finch <dot@dotat.at> wrote 
 a message of 62 lines which said:

> If the request is not HEAD/GET/POST, I return 405 Method Not Allowed
> with a browser-friendly body.
> 
> For POST requests with an unknown Content-Type, or GET requests with
> an unknown or missing `ct=` parameter, my server returns 415
> Unsupported Media Type with a browser-friendly body.
> 
> If the `dns=` parameter is missing from a GET request, the best
> response seems to be a browser-friendly 400 Bad Request.

> If the request's Accept: header doesn't allow
> `application/dns-udpwireformat` then the response should be a
> browser-friendly 406 Not Acceptable.

I agree with all this (and my hackathon-developed server does the
same) but, to follow Patrick McManus' idea of not restating everything
which is in HTTP, may be this could go in a non-normative appendix
such as "Implementation suggestions for non-HTTP experts"? With
lowercase "should" (specially for the last one: today, all the DoH
servers completely ignore Accept:)

v2.23.0 | Report a Bug | By Email