IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@icann.org> Mon, 19 March 2018 10:12 UTC

Return-Path: <paul.hoffman@icann.org>
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 2CDC4126DC2 for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 03:12:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 csmqB1L50KkC for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 03:12:42 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26095126CE8 for <doh@ietf.org>; Mon, 19 Mar 2018 03:12:42 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 19 Mar 2018 03:12:40 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Mon, 19 Mar 2018 03:12:40 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Ted Hardie <ted.ietf@gmail.com>
CC: DoH WG <doh@ietf.org>
Thread-Topic: [Ext] [Doh] A question on the mix of DNS and HTTP semantics
Thread-Index: AQHTv2rP/VUpr+taDUO0M0VJnys/ag==
Date: Mon, 19 Mar 2018 10:12:39 +0000
Message-ID: <88AB1743-7270-4D72-8C70-0AB6B74416BD@icann.org>
References: <CA+9kkMB7awRfW9jUmY9Q-1p+w3VLtpG5DxhF3s7Q58nEMZeX3w@mail.gmail.com> <20180318164307.GB6724@laperouse.bortzmeyer.org> <CAOdDvNr1GstB+g3pYi4w0bXuQ=Nz8HqgTRfWUX9TGu9YAYiz0w@mail.gmail.com> <CA+9kkMA733q3BPRbnN++0vwKrmOOCN8SBgknYwFaeEf2cvYikw@mail.gmail.com>
In-Reply-To: <CA+9kkMA733q3BPRbnN++0vwKrmOOCN8SBgknYwFaeEf2cvYikw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.47.234]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D6ED6769F916C243AFB06036A89B3BAE@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/ZUO46dqtXYDe3_kLU5iCFk1w_ic>
Subject: Re: [Doh] [Ext] 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: Mon, 19 Mar 2018 10:12:43 -0000

On Mar 19, 2018, at 9:49 AM, Ted Hardie <ted.ietf@gmail.com> wrote:
> The message body may not be able to answer this question completely, but it can clarify at the DNS level that this was REFUSED.  The semantics of that are much closer to 451's meaning than producing no DNS-level response at all (which maps to "query did not complete" if I understand it correctly).

Hopping up one level, I think you are describing a DOH server that inspects queries or responses and chooses to change the HTTP response to use a non-2xx code. That seems fine, but it also seems like you are saying that the DNS response inside that HTTP response should be understood by the client, and in a code-specific way. Is that a fair summary?

--Paul Hoffman

v2.23.0 | Report a Bug | By Email