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

"John R Levine" <johnl@taugh.com> Thu, 10 August 2017 18:30 UTC

Return-Path: <johnl@taugh.com>
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 A6A96132406 for <dispatch@ietfa.amsl.com>; Thu, 10 Aug 2017 11:30:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=iecc.com header.b=klujwMSK; dkim=neutral reason="invalid (public key: not available)" header.d=taugh.com header.b=Bt8E/+fX
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 ZQs7z5JlfLi0 for <dispatch@ietfa.amsl.com>; Thu, 10 Aug 2017 11:30:01 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7B4B1323B1 for <dispatch@ietf.org>; Thu, 10 Aug 2017 11:30:00 -0700 (PDT)
Received: (qmail 61630 invoked from network); 10 Aug 2017 18:29:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=f0bc.598ca627.k1707; bh=LhedcKbpmnYNSee15nVcNTmfF6kBtY7+G1be+LdFtTY=; b=klujwMSK/3XO+Ea/L+ZckPlKgtgXi5iuPIrcA5tmMKqx6i4U/JG1LdZR7L+YXden485Dc3yamUp/hlfpZkoSu/JXSO0SkKAIGPOTPDJFJyHo13id55u4vWpHJIf+kdvWbz/J1xLck9t1LM5U+Ju7u7nzlBaj4XblIQypN6niJQbzzuB4/ZTxouP265VL4hhiZbcwKDZmzLZFpvxF0r8ylVsCAo/4b3FQtkmadv/mgSWQ88bh/JTofAwzKvbM7gI5
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=f0bc.598ca627.k1707; bh=LhedcKbpmnYNSee15nVcNTmfF6kBtY7+G1be+LdFtTY=; b=Bt8E/+fXHkItqJs0pb/4YkjyjhBnFRAeCfvhbB05R/lkizv3+CBZLVkctNwQBjfqf6I8AQlPF6t7+ElRE+QS+lByrl6fVoIPM1SYYPlhV3iX6h6rjxQJlNe4lLSx3SPExnFrl0VhA+bwbEqDy767j7bf5St/GFOniLvwfSDScOe2qrT5z1pONJtbUWs1LAlMOZ1rmNwYNx/gBEsfBUkwvO3SVOQ6ARNXGXx99rG3onAMWWR3idA339m1oBQbbqgN
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 10 Aug 2017 18:29:59 -0000
Date: Thu, 10 Aug 2017 14:29:59 -0400
Message-ID: <alpine.OSX.2.21.1708101427390.37126@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Dispatch WG <dispatch@ietf.org>
In-Reply-To: <305d8c08-ce2d-8e4e-5293-c5c3abb5256b@cs.tcd.ie>
References: <20170810160035.9804.qmail@ary.lan> <305d8c08-ce2d-8e4e-5293-c5c3abb5256b@cs.tcd.ie>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/IZZe9oo2AOj46kgaaRyVaM-x_3k>
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 18:30:03 -0000

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.

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

CORS?

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