[DNSOP] Possible issues with DNS over HTTP wire format draft

Shane Kerr <shane@time-travellers.org> Mon, 08 August 2016 13:42 UTC

Return-Path: <shane@time-travellers.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 675E612D83B for <dnsop@ietfa.amsl.com>; Mon, 8 Aug 2016 06:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 2P_DVz2aOCl8 for <dnsop@ietfa.amsl.com>; Mon, 8 Aug 2016 06:42:00 -0700 (PDT)
Received: from time-travellers.nl.eu.org (c.time-travellers.nl.eu.org [IPv6:2a02:2770::21a:4aff:fea3:eeaa]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCA7512D81C for <dnsop@ietf.org>; Mon, 8 Aug 2016 06:41:59 -0700 (PDT)
Received: from [2001:470:78c8:2:224:9bff:fe13:3a9c] (helo=pallas.home.time-travellers.org) by time-travellers.nl.eu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <shane@time-travellers.org>) id 1bWkoV-0006SB-0j; Mon, 08 Aug 2016 13:41:55 +0000
Date: Mon, 08 Aug 2016 15:41:52 +0200
From: Shane Kerr <shane@time-travellers.org>
To: dnsop@ietf.org
Message-ID: <20160808154152.5d9c30f1@pallas.home.time-travellers.org>
X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; boundary="Sig_/KAztn=Y/zWI83j1iAeFaH0p"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/H_58BuuHEWACAP-ezaN206aiJYM>
Cc: Martin Thomson <martin.thomson@gmail.com>
Subject: [DNSOP] Possible issues with DNS over HTTP wire format draft
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2016 13:42:05 -0000

Hello,

There are a few suggestions about the DNS over HTTP draft made off-list,
which I will try to characterize here:

* We should expand the motivations to explain why DNS over HTTP makes
  sense at all. 

* We should restrict the protocol to TLS.

I am happy to expand the motivation section, although I am beginning to
wonder if it will ever be enough. :)

As for a requirement for TLS... the document currently says that
implementers SHOULD use TLS. My own feeling is that this should be
enough; apparently the recommendation to require TLS was made in the
HTTP/2 working group and rejected, so I am not sure that we need to
re-visit the entire discussion around the DNS over HTTP protocol.

https://http2.github.io/faq/#does-http2-require-encryption

Note that I do not have a strong preference here. This is a working
group document, so if there is consensus for requiring TLS then that's
how it is.


A final oversight that occurred to me is that there should be a privacy
section. This is because since the DNS over HTTP serves as a DNS
resolver that all of the privacy considerations of a normal DNS
resolver apply, and should be mentioned (probably referencing RFC 7626).

Cheers,

--
Shane