IETF Logo Mail Archive

Re: [dispatch] Working Group Proposal: DNS Over HTTPS

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 10 August 2017 19:40 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E982132433 for <dispatch@ietfa.amsl.com>; Thu, 10 Aug 2017 12:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 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, URIBL_BLOCKED=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 V5bblUYnBfL6 for <dispatch@ietfa.amsl.com>; Thu, 10 Aug 2017 12:40:53 -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 F06B5132429 for <dispatch@ietf.org>; Thu, 10 Aug 2017 12:40:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 5F817BE2F; Thu, 10 Aug 2017 20:40:49 +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 ou9QuChoIuG9; Thu, 10 Aug 2017 20:40:46 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 8BB9CBE2E; Thu, 10 Aug 2017 20:40:46 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1502394046; bh=CBgOv2pvyIZlnCghalQN9NnN3XsPt8xShMQ26cdC5D0=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Rwzoqz5qHd8OWnAIZ3lCrh785lB7ZK+WpBKSHUbL+unQ+ZS4OIS6Ze/MBD5pa4uY+ SkfwTt1TFLn876r4fRY9xIVLkN+RoZJY6561hQ57x1NoDL4VlL1wLAJ5qA4NtdZpSZ Ipsj5C4sQ4Rh9mv0s5fn8NVeB9G6ZQdGYvNgPT7Q=
To: John R Levine <johnl@taugh.com>
Cc: Dispatch WG <dispatch@ietf.org>
References: <20170810160035.9804.qmail@ary.lan> <305d8c08-ce2d-8e4e-5293-c5c3abb5256b@cs.tcd.ie> <alpine.OSX.2.21.1708101427390.37126@ary.qy>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <3d53edbf-2d56-5972-5ce7-bc82f6d82960@cs.tcd.ie>
Date: Thu, 10 Aug 2017 20:40:45 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.21.1708101427390.37126@ary.qy>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="GdqTxSDnjN5i6dtV6E2vRCQUQrTqPJAv6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/mi7Iq6UmyrDV3yeTf0cf27FJG8s>
Subject: Re: [dispatch] Working Group Proposal: DNS Over HTTPS
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Aug 2017 19:40:55 -0000


On 10/08/17 19:29, John R Levine wrote:
> On Thu, 10 Aug 2017, Stephen Farrell wrote:
>> If however, a random web site were to be able to get a http
>> client like a browser to believe lies about dns then that'd
>> be much worse than today, if those lies affect more than the
>> web pages that the fibbing web site can control anyway.
> 
> I don't see what the problem is.  This is just a way to encapsulate DNS
> queries in http, typically from a javascript routine running in a
> browser. Unless browsers work very differently from the way I think they
> do, this is not a way to patch a browser's DNS lookup code.

I don't know what you mean by that last tbh.

The problem I'm trying to describe is touched on in the
last para of the draft's security considerations.

> 
>> As an aside, I'm puzzled a bit by how CORS comes into this.
> 
> CORS?

Yes. The mention of that in the draft we're discussing is
a bit of a puzzle to me. Hopefully you didn't read some
other draft:-)

S.

> 
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
>

v2.23.0 | Report a Bug | By Email