Re: [Doh] WG Review: DNS Over HTTPS (doh)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 26 September 2017 00:06 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 ABD37134614; Mon, 25 Sep 2017 17:06:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 uy1aXKQp8hut; Mon, 25 Sep 2017 17:06:07 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A845F13232C; Mon, 25 Sep 2017 17:06:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 7FF71BE2E; Tue, 26 Sep 2017 01:06:04 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VVTCwCfJNlAQ; Tue, 26 Sep 2017 01:06:03 +0100 (IST)
Received: from [10.244.2.100] (unknown [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 34D81BE24; Tue, 26 Sep 2017 01:06:03 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1506384363; bh=8hVS5fkC9SuuEfXYKQD8uaN48E8YYXLqMqwMUHW5/zg=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=FJ49W9jxruZjK4W3UwDsdBmJVC9jylU/BKszCsFRpUSjTA8J6wEITiAvY1zC14/dc tzfbMTIOpPrtcaiUdp7NAdIWIfk2C7ibhXYUziFyOgK8HgvYdkQ0pIshEZ+QmYlbx6 3i7M4b1tmg/s+DQlz9JWXl+b1B7ByqNgoaU1X8EY=
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Adam Roach <adam@nostrum.com>, Ted Hardie <ted.ietf@gmail.com>, doh@ietf.org, IETF <ietf@ietf.org>
References: <150549029332.2975.12341647131707994474.idtracker@ietfa.amsl.com> <CA+9kkMBJAP23GmGf_ix-DMeOMB=Rbas+qsBQhrVwZuA5-Cv7Mg@mail.gmail.com> <03b11478-6b75-8e52-e6d9-612885804aad@nostrum.com> <CA+9kkMA1z8XF7QNXdY_bGbHdUD8UOBS57VbbJn7xmt7rb8SOGw@mail.gmail.com> <2861b0eb-2486-9ba2-0b48-48293d758f03@cs.tcd.ie> <06c81edd-9f11-616f-e549-06fb180564a4@nostrum.com> <09eeb83b-ca78-bcbc-386e-c87eb82064b7@cs.tcd.ie> <CABkgnnVhFEYQpoLNLr9z6SceJ=X=jyF3XgvBwZs4AyrE9X3A+A@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <1982a9a7-85ee-21d2-e0cf-a8efbfee8e15@cs.tcd.ie>
Date: Tue, 26 Sep 2017 01:06:02 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnVhFEYQpoLNLr9z6SceJ=X=jyF3XgvBwZs4AyrE9X3A+A@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="OWDRXEUuBu9gLq6wQGQoqtDmDexBtr27A"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/uj_J2eQm2RFcQgFUT1nPhXTZ-zI>
Subject: Re: [Doh] WG Review: DNS Over HTTPS (doh)
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: Tue, 26 Sep 2017 00:06:10 -0000


On 26/09/17 01:04, Martin Thomson wrote:
> The Working Group will analyze the security and privacy issues that
> could arise from accessing DNS over HTTPS. In particular, the Working
> Group will consider the interaction of DNS and HTTP caching.

Yep, that's better than my earlier suggestion.

S.