IETF Logo Mail Archive

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

Ben Schwartz <bemasc@google.com> Thu, 10 August 2017 19:53 UTC

Return-Path: <bemasc@google.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 79A7F132359 for <dispatch@ietfa.amsl.com>; Thu, 10 Aug 2017 12:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 X6pDb9cplBax for <dispatch@ietfa.amsl.com>; Thu, 10 Aug 2017 12:53:13 -0700 (PDT)
Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF64A132420 for <dispatch@ietf.org>; Thu, 10 Aug 2017 12:53:12 -0700 (PDT)
Received: by mail-vk0-x22e.google.com with SMTP id j189so6722827vka.0 for <dispatch@ietf.org>; Thu, 10 Aug 2017 12:53:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=F/fUTZfpAS6v7B5tyGQJs144IVoGlF8T85o5beTmZOA=; b=q/S9iHuhbPROeUfrITp24ySzaOML0BX+o3Fv800bzXRiOkhaxC3TjAbylIFBv9KU8c 4BsosYtG5tdKyqDowIPE8BYIWM8NDw3T3Xd/yfz8ePrTsyVb1UWCh2KIdp4O8kiNSjya 4r9tTxAdnxBpRu2+JCjalRj9+BBpLX5qihIbVjQcW5FMqmwWzfpeV0sTGByahOx8HZox EOvdQfivjviHH9Yh7Il6fYjnJoa2kIZ2YtIVA9S8+yJOuI/BN/cIbH1qM3vLzDu5/ubN ZBF3ryOzwqjUbnLkfZ+5Psy/ZdhuB+v59B/4XcdzM+gLJtMLPqBHafrFBvEc6ujSzLlx sjaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=F/fUTZfpAS6v7B5tyGQJs144IVoGlF8T85o5beTmZOA=; b=m5vConNIWodSPSE4CWdDDjOuKMtcR/vXV/SaxlXmA9Wk7izeBjNyvYuKDqL5/4j5fW GnrR+BHymyXaticpQCA4QE9DLgLg9kPV5hxHLaOCsrZEA/ZTrKOG3irHFRIqmjjVQqH6 gKR5x7jSlTHH62DiwJvgpIkUy1wpjCg5bzsRa9BpS7qys1jnc8CB4iIUef0OCVwm64D4 xVN46ljOGMyvDG6gN7Q6CKiNV8a7aZv9BS/bX6YxoZr43R/kMkM3BYLO9SnQmMXJHSuS Gk3MiVYfT1343lsz8QEu7HekgTw1jCigB8bZcqgLsuUwHumRV06GNXRuAdkItQO7eD8/ f62g==
X-Gm-Message-State: AHYfb5j4jGqBDqnSr3OWjB/Gx9T0BeChH33Xp/5K1+urYD7BRtQPsyJ+ 6tkEWcpncziNHuZu0MjiqCm4K89bRKDRXZc=
X-Received: by 10.31.193.141 with SMTP id r135mr8410511vkf.113.1502394791400; Thu, 10 Aug 2017 12:53:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.50.204 with HTTP; Thu, 10 Aug 2017 12:53:09 -0700 (PDT)
In-Reply-To: <3d53edbf-2d56-5972-5ce7-bc82f6d82960@cs.tcd.ie>
References: <20170810160035.9804.qmail@ary.lan> <305d8c08-ce2d-8e4e-5293-c5c3abb5256b@cs.tcd.ie> <alpine.OSX.2.21.1708101427390.37126@ary.qy> <3d53edbf-2d56-5972-5ce7-bc82f6d82960@cs.tcd.ie>
From: Ben Schwartz <bemasc@google.com>
Date: Thu, 10 Aug 2017 15:53:09 -0400
Message-ID: <CAHbrMsDXAyz99teaGzDQAnpbvnAry+k-5x0EGRV8EAJ0B5qZ+g@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: John R Levine <johnl@taugh.com>, Dispatch WG <dispatch@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="001a114dba4ee4d2b505566b8bf2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/BuiJOP4KuWHAbIeDHWZeOu5ZxEk>
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:53:15 -0000

On Thu, Aug 10, 2017 at 3:40 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
>
> 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.
>

I agree that paragraph is a bit out of place in this draft, but I think the
text is just trying to agree with you.  It's implicitly describing a
hypothetical scenario (browsers flinging DNS queries to any web server they
bump into) in order to say DON'T DO THAT.

I think we can clarify the wording there, and also possibly write a charter
that explicitly excludes any change to how DNS clients choose recursive
resolvers.


> >
> >> 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
> >
>
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>
>

v2.23.0 | Report a Bug | By Email